About

Imported from CyberStrikeus/CyberStrike (.cyberstrike/skill/NIST/SP800-53_rev5/SI_system-and-information-integrity/si-2-3-time-to-remediate-flaws-and/SKILL.md). Install upstream with npx skills add CyberStrikeus/CyberStrike --skill si-2-3-time-to-remediate-flaws-and. Copyright stays with the author.

SI-2(3) Time to Remediate Flaws and Benchmarks for Corrective Actions

Name: SI-2(3)_time-to-remediate-flaws-and-benchmarks-for-corrective-action
Author: CyberStrikeus

Enhancement of: SI-2

High-Level Description

Family: System and Information Integrity (SI) Framework: NIST SP 800-53 Rev 5

Organizations determine the time it takes on average to correct system flaws after such flaws have been identified and subsequently establish organizational benchmarks (i.e., time frames) for taking corrective actions. Benchmarks can be established by the type of flaw or the severity of the potential vulnerability if the flaw can be exploited.

What to Check

Verify SI-2(3) Time to Remediate Flaws and Benchmarks for Corrective Actions is documented in SSP
Validate all 2 control requirements are implemented
Confirm control is operating effectively
Review evidence of continuous monitoring for SI-2(3)
Verify enhancement builds upon base control SI-2

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for SI-2(3) implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

Tools

Tool	Purpose	Usage
cloud-audit-mcp	Check integrity monitoring	`cloud_audit_monitoring`
AWS CLI	Review GuardDuty/Inspector	`aws guardduty list-detectors`

Remediation Guide

Control Statement

Measure the time between flaw identification and flaw remediation; and Establish the following benchmarks for taking corrective actions: [organization-defined].

Implementation Guidance

Organizations determine the time it takes on average to correct system flaws after such flaws have been identified and subsequently establish organizational benchmarks (i.e., time frames) for taking corrective actions. Benchmarks can be established by the type of flaw or the severity of the potential vulnerability if the flaw can be exploited.

Risk Assessment

Finding	Severity	Impact
SI-2(3) Time to Remediate Flaws and Benchmarks for Corrective Actions not implemented	High	System and Information Integrity
SI-2(3) partially implemented	Medium	Incomplete System and Information Integrity

CWE Categories

CWE ID	Title
CWE-20	Improper Input Validation

References

Checklist

Control documented in SSP
Implementation evidence collected
Operating effectiveness validated
Continuous monitoring in place
Related controls (none) reviewed

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/cyberstrikeus-cyberstrike-si-2-3-time-to-remediate-flaws-and/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

cyberstrikeus-cyberstrike-si-2-3-time-to-remediate-flaws-and.ocm.jsonjson

{
  "ocm": "1",
  "id": "cyberstrikeus-cyberstrike-si-2-3-time-to-remediate-flaws-and",
  "kind": "skill",
  "name": "SI-2(3)_time-to-remediate-flaws-and-benchmarks-for-corrective-action",
  "description": "Measure the time between flaw identification and flaw remediation;",
  "publisher": "CyberStrikeus",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "nist",
      "sp800-53",
      "rev5",
      "si-2-3",
      "si",
      "enhancement",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Measure the time between flaw identification and flaw remediation;"
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/CyberStrikeus/CyberStrike",
      "path": ".cyberstrike/skill/NIST/SP800-53_rev5/SI_system-and-information-integrity/si-2-3-time-to-remediate-flaws-and/SKILL.md",
      "ref": "df28ccd3dc6d6c02391169121ee2dcdf4a6a132b",
      "url": "https://github.com/CyberStrikeus/CyberStrike/blob/df28ccd3dc6d6c02391169121ee2dcdf4a6a132b/.cyberstrike/skill/NIST/SP800-53_rev5/SI_system-and-information-integrity/si-2-3-time-to-remediate-flaws-and/SKILL.md",
      "key": "CyberStrikeus/CyberStrike/.cyberstrike/skill/NIST/SP800-53_rev5/SI_system-and-information-integrity/si-2-3-time-to-remediate-flaws-and/SKILL.md"
    }
  },
  "instructions": "# SI-2(3) Time to Remediate Flaws and Benchmarks for Corrective Actions\n\n> **Enhancement of:** SI-2\n\n## High-Level Description\n\n**Family:** System and Information Integrity (SI)\n**Framework:** NIST SP 800-53 Rev 5\n\nOrganizations determine the time it takes on average to correct system flaws after such flaws have been identified and subsequently establish organizational benchmarks (i.e., time frames) for taking corrective actions. Benchmarks can be established by the type of flaw or the severity of the potential vulnerability if the flaw can be exploited.\n\n## What to Check\n\n- [ ] Verify SI-2(3)",
  "cost": {
    "context_tokens": 945
  }
}

Fetch it by URL: GET /api/v1/registry/cyberstrikeus-cyberstrike-si-2-3-time-to-remediate-flaws-and/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.