Level 2 · System and Information Integrity

SI.L2-3.14.1

Flaw Remediation

Flaw remediation needs defined timing for identification, reporting, and correction.

Score: 5 POA&M: Not eligible
✓ Level 1 coverage included: SI.L1-b.1.xii ↓
GAVII Cybersecurity assessment reference

Official reference

The requirement

Identify, report, and correct system flaws in a timely manner.

DoD CMMC Assessment Guide, Level 2, version 2.13. SI.L2-3.14.1; requirement and objectives, printed page 246 ↗

Assessment objectives

What must be established

Determine if each applicable objective is satisfied. The labels below follow the cited DoD assessment guide.

  1. [a]

    the time within which to identify system flaws is specified;

  2. [b]

    system flaws are identified within the specified time frame;

  3. [c]

    the time within which to report system flaws is specified;

  4. [d]

    system flaws are reported within the specified time frame;

  5. [e]

    the time within which to correct system flaws is specified; and

  6. [f]

    system flaws are corrected within the specified time frame.

MET requires evidence that all applicable objectives are satisfied. Final, approved evidence is needed. A NOT APPLICABLE determination needs a scope-based basis and is equivalent to MET for scoring. Enduring exceptions and temporary deficiencies have specific conditions under 32 CFR 170.24; they are not a general permission to defer implementation.

Included Level 1 coverage · FCI

SI.L1-b.1.xii: Flaw Remediation

Flaws need defined timeframes for identification, reporting, and correction.

Level 2 includes Level 1 safeguarding coverage. This is the FAR-based Level 1 assessment context mapped into the 110-requirement library, not an additional Level 2 requirement.

Identify, report, and correct information and information system flaws in a timely manner.

DoD CMMC Assessment Guide, Level 1: SI.L1-b.1.xii; requirement and objectives, printed page 39 ↗

Level 1 assessment objectives and guidance

Determine if:

  1. [a]

    the time within which to identify system flaws is specified;

  2. [b]

    system flaws are identified within the specified time frame;

  3. [c]

    the time within which to report system flaws is specified;

  4. [d]

    system flaws are reported within the specified time frame;

  5. [e]

    the time within which to correct system flaws is specified; and

  6. [f]

    system flaws are corrected within the specified time frame.

Treat each step as an evidence question. A list of installed patches does not establish when the organization became aware of a flaw or notified the responsible person.

Examine

Review the defined timeframes, flaw records, notifications, corrective work, and verification.

Interview

How are flaws in different system types identified and assigned for correction?

Demonstrate or test

Trace a representative flaw through identification, reporting, and verified correction against the defined timeframes.

Level 1 evidence gaps

  • Only a patching deadline is defined.
  • Failed updates remain unresolved without an owner.

Level 1 has no weighted deduction. All applicable requirements must be fully implemented; the self-assessment is MET or NOT MET in its entirety.

Level 1 does not permit a POA&M. CAP P.11 addresses Level 2 certification planning, not a mandatory on-site rule for Level 1 self-assessments. Choose evidence and observations adequate to evaluate the actual physical environment and applicable objectives.

GAVII Cybersecurity assessment approach

Connect the objective to the evidence

Evaluate these three steps separately. A patch dashboard may show installation status without establishing when flaws were identified or reported to the responsible owner.

Assessment focus: objectives [a], [b], [c], [d], [e], [f]. Use the methods together; a single example does not establish every objective.

Examine

Review defined timeframes, discovery records, notifications, remediation records, and verification results.

Interview

How are the identification, reporting, and correction timeframes applied to different system types?

Demonstrate or test

Trace a representative flaw through all three timestamps and verify the resulting correction.

Evidence gaps to look for

  • Only a patch deadline is defined.
  • Unsupported systems or failed installations remain outside the tracked process.

GAVII Cybersecurity’s examples illustrate ways to examine, interview, and test. They are not a mandatory artifact list or a guarantee of an assessment result. Combine methods and address every applicable objective in the actual scope.

Assessment constraints

Scoring and POA&M eligibility

Score: 5

If this requirement is NOT MET, deduct 5 points from the Level 2 maximum of 110. The deduction applies to the requirement, not separately to each objective.

Scoring rule ↗

POA&M: Not eligible

This requirement has a deduction greater than 1 point and does not qualify for the limited encryption exception. It cannot be deferred on the POA&M used for Conditional Level 2 status.

POA&M rule ↗

Conditional Level 2 requires a score of at least 88 out of 110 and satisfaction of every eligibility condition. A 1-point requirement is not automatically eligible. The permitted POA&M must be closed through the appropriate closeout assessment within 180 days of the Conditional CMMC Status Date. An operational remediation plan does not confer Conditional Status.

Assessment planning

Location and observation

Not specifically listed in CAP P.11

This requirement is not specifically listed in CAP P.11. That does not establish that remote assessment is sufficient: the Lead CCA and C3PAO determine an adequate approach for the actual scope and evidence.

CAP §P.11, pages 10–11 ↗

Check the source

References and related requirements

Program timing and contract applicability can change independently of these requirements. Check current DoD program notices and your solicitation or contract before making a compliance decision. Open the official DoD resource hub.

Get your free consultation.