Back to Control Explorer



Control Acronym



System And Information Integrity

CMMC Level


800-171 Control #


CMMC Description

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

CMMC Clarification

All software and firmware have potential flaws. Many vendors work to reduce those flaws by releasing vulnerability information and updates to their software and firmware. Organizations should have a process to review relevant vendor newsletters with updates about common problems or weaknesses. After reviewing the information the organization should execute a process called patch management that allows for systems to be updated without adversely affecting the organization. Organizations should also purchase support from their vendors to ensure timely access to updates. Example You have many responsibilities at your company, including IT. You know that malware, ransomware, and viruses can be a big problem for companies. You make sure to enable all security updates for your software, including the operating system and applications, and purchase the maintenance packages for new hardware and operating systems.

800-171 Description

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

800-171 Discussion

Organizations identify systems that are affected by announced software and firmware flaws including potential vulnerabilities resulting from those flaws and report this information to designated personnel with information security responsibilities. Security-relevant updates include patches, service packs, hot fixes, and anti-virus signatures. Organizations address flaws discovered during security assessments, continuous monitoring, incident response activities, and system error handling. Organizations can take advantage of available resources such as the Common Weakness Enumeration (CWE) database or Common Vulnerabilities and Exposures (CVE) database in remediating flaws discovered in organizational systems. Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of factors including the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). Some types of flaw remediation may require more testing than other types of remediation. [SP 800-40] provides guidance on patch management technologies.

Other Source Discussion


CIS Control References

NIST 800-53 Control Ref.

NIST SP 800-53 Rev 4 SI-2

CMMC Derived

NIST CSF Control References

NIST 800-171 References

NIST SP 800-171 Rev 1 3.14.1

Applicable FAR Clause

FAR Clause 52.204-21 b.1.xii

NIST CSF Control Reference

NIST CSF v1.1 RS.CO-2, RS.MI-3

CERT RMM Reference


Modification of NIST 800-171B Reference

NIST 800-171B Reference

UK NCSCCyber Reference

UK NCSC Cyber Essentials

AS ACSC Reference

AU ACSC Essential Eight


Assessment Sub-Criteria 1

SI.1.210.[a] the time within which to identify system flaws is specified;

Assessment Sub-Criteria 2

SI.1.210.[b] system flaws are identified within the specified time frame;

Assessment Sub-Criteria 3

SI.1.210.[c] the time within which to report system flaws is specified;

Assessment Sub-Criteria 4

SI.1.210.[d] system flaws are reported within the specified time frame;

Assessment Sub-Criteria 5

SI.1.210.[e] the time within which to correct system flaws is specified; and

Assessment Sub-Criteria 6

SI.1.210.[f] system flaws are corrected within the specified time frame.

Assessment Sub-Criteria 7

Assessment Sub-Criteria 8

Assessment Sub-Criteria 9

Assessment Sub-Criteria 10

Assessment Sub-Criteria 11

Assessment Sub-Criteria 12

Assessment Sub-Criteria 13

Assessment Sub-Criteria 14

Assessment Sub-Criteria 15