CMMC Overview - Revision history

Uncouth: re-wording, adding more future pages, etc.

2025-03-05T00:52:51Z

re-wording, adding more future pages, etc.

← Older revision		Revision as of 00:52, 5 March 2025
Line 3:		Line 3:
	In November 2021, in response to industry feedback, CMMC 2.0 was introduced to simplify the original model, making compliance more achievable while maintaining strong security standards. This updated framework reduces the original five certification levels down to three:		In November 2021, in response to industry feedback, CMMC 2.0 was introduced to simplify the original model, making compliance more achievable while maintaining strong security standards. This updated framework reduces the original five certification levels down to three:

	<u>Level 1:</u> Basic cyber hygiene practices, ~~primarily protecting~~ FCI. Organizations must implement 17 practices aligned with Federal Acquisition Regulation ([[FAR]]) 52.204-21.		<u>Level 1:</u> Basic cyber hygiene practices, for the protection of [[Federal Contract Information (FCI)]]. Organizations must implement 15 practices aligned with Federal Acquisition Regulation ([[FAR]]) [https://www.acquisition.gov/far/52.204-21 52.204-21].

	<u>Level 2:</u> Aligned with NIST SP 800-171 Rev 2, this level applies to ~~companies~~ that handle CUI. It includes 110 security controls required by [[NIST 800-171]]~~, emphasizing areas such as access control, incident response, and system security~~.		<u>Level 2:</u> Aligned with NIST SP 800-171 Rev 2, this level applies to [[Covered contractor information system\|covered contractor information systems]] that handle CUI. It includes 110 security controls and 320 assessment objectives required by [[NIST 800-171]].

	<u>Level 3:</u> ~~Designed~~ for companies with ~~the highest cybersecurity requirements~~, Level 3 ~~incorporates advanced practices beyond~~ NIST SP 800-171 and ~~will be aligned~~ with ~~a subset of controls~~ from [[NIST SP 800-172]], focusing on defending against advanced persistent threats ([[APT]]s).		<u>Level 3:</u> Intended for companies with more sensitive CUI, Level 3 includes all NIST SP 800-171 requirements and enhances those requirements with 24 additional practices from [[NIST SP 800-172]], focusing on defending against advanced persistent threats ([[APT]]s).

	=== [[Self-Assessment and Certification]]: ===		=== [[Self-Assessment and Certification]]: ===

	Under CMMC 2.0, organizations handling only FCI at Level 1 ~~can~~ conduct annual self-assessments. For Level 2, companies handling critical CUI must undergo third-party assessments or self-attest depending on the criticality of the contract. Level 3 requires ~~comprehensive third-party assessments~~ by the Defense Industrial Base Cybersecurity Assessment Center (DIBCAC).		Under CMMC 2.0, organizations handling only FCI at Level 1 will be required to conduct annual self-assessments. For Level 2, companies handling critical CUI must undergo third-party assessments or self-attest depending on the criticality of the contract. Level 3 requires a CMMC Level 2 C3PAO assessment followed by a Level 3 assessment performed by the Defense Industrial Base Cybersecurity Assessment Center (DIBCAC).

	=== Why CMMC is Important ===		=== Why CMMC is Important ===

Uncouth: Removed the 800-171 families, to be re-done at a later date

2025-02-25T20:04:42Z

Removed the 800-171 families, to be re-done at a later date

← Older revision		Revision as of 20:04, 25 February 2025
Line 8:		Line 8:

	<u>Level 3:</u> Designed for companies with the highest cybersecurity requirements, Level 3 incorporates advanced practices beyond NIST SP 800-171 and will be aligned with a subset of controls from [[NIST SP 800-172]], focusing on defending against advanced persistent threats ([[APT]]s).		<u>Level 3:</u> Designed for companies with the highest cybersecurity requirements, Level 3 incorporates advanced practices beyond NIST SP 800-171 and will be aligned with a subset of controls from [[NIST SP 800-172]], focusing on defending against advanced persistent threats ([[APT]]s).

	~~=== NIST 800-171 Rev 2: The Foundation of CMMC 2.0: ===~~

	At the heart of CMMC Level 2 is NIST Special Publication 800-171 Revision 2, which outlines security requirements for protecting CUI in non-federal systems. Organizations must meet the 14 families of security requirements, which include:

	~~'''[[Access Control]] (AC)'''~~
	~~Ensures that only authorized users have access to the information systems and CUI.~~
	~~Example: Role-based access control (RBAC).~~

	~~'''[[Awareness and Training]] (AT)'''~~
	~~Ensures that users are trained and aware of security risks and organizational policies.~~
	~~Example: Regular cybersecurity training sessions.~~

	~~'''[[Audit and Accountability]] (AU)'''~~
	~~Provides mechanisms to audit the system's activities and ensure users are accountable for their actions.~~
	~~Example: Logging of all user activities for tracking and investigation.~~

	~~'''[[Configuration Management]] (CM)'''~~
	~~Involves managing security configurations of systems to reduce vulnerabilities.~~
	~~Example: Ensuring systems have up-to-date security patches.~~

	~~'''[[Identification and Authentication]] (IA)'''~~
	~~Verifies user identities and provides mechanisms for authentication.~~
	~~Example: Multi-factor authentication (MFA).~~

	~~'''[[Incident Response]] (IR)'''~~
	~~Prepares for, detects, and responds to security incidents.~~
	~~Example: Incident reporting and remediation processes.~~

	~~'''[[Maintenance]] (MA)'''~~
	~~Provides procedures for system maintenance that protect the security of CUI during routine and emergency repairs.~~
	~~Example: Remote maintenance procedures with authentication controls.~~

	~~'''[[Media Protection]] (MP)'''~~
	~~Ensures that physical and digital media containing CUI are protected from unauthorized access or loss.~~
	~~Example: Encryption of removable storage devices.~~

	~~'''[[Personnel Security]] (PS)'''~~
	~~Ensures that personnel are properly vetted and that access to CUI is limited based on individual trustworthiness.~~
	~~Example: Background checks for employees handling CUI.~~

	~~'''[[Physical Protection]] (PE)'''~~
	~~Restricts physical access to information systems, equipment, and operating environments.~~
	~~Example: Secure data centers with controlled entry points.~~

	~~'''[[Risk Assessment]] (RA)'''~~
	~~Involves the identification and analysis of potential risks to information systems and CUI.~~
	~~Example: Regular vulnerability scans and risk assessments.~~

	~~'''[[Security Assessment]] (CA)'''~~
	~~Regularly assesses and tests security controls to ensure they are effective.~~
	~~Example: Third-party security audits.~~

	~~'''[[System and Communications Protection]] (SC)'''~~
	~~Ensures that communications between systems are secure and protected from unauthorized access.~~
	~~Example: Encryption of data in transit and at rest.~~

	~~'''[[System and Information Integrity]] (SI)'''~~
	~~Protects systems and data by identifying and mitigating flaws and vulnerabilities.~~
	~~Example: Continuous monitoring and timely application of security patches.~~

	~~Meeting NIST 800-171 Rev 2 is crucial for achieving CMMC Level 2 certification and is mandatory for contractors handling CUI.~~

	=== [[Self-Assessment and Certification]]: ===		=== [[Self-Assessment and Certification]]: ===

Marieramsay at 22:45, 26 September 2024

2024-09-26T22:45:59Z

Marieramsay at 22:31, 26 September 2024

2024-09-26T22:31:45Z

Marieramsay at 22:30, 26 September 2024

2024-09-26T22:30:15Z

Marieramsay at 22:29, 26 September 2024

2024-09-26T22:29:45Z

← Older revision		Revision as of 22:29, 26 September 2024
Line 9:		Line 9:
	Level 3: Designed for companies with the highest cybersecurity requirements, Level 3 incorporates advanced practices beyond NIST SP 800-171 and will be aligned with a subset of controls from NIST SP 800-172, focusing on defending against advanced persistent threats (APTs).		Level 3: Designed for companies with the highest cybersecurity requirements, Level 3 incorporates advanced practices beyond NIST SP 800-171 and will be aligned with a subset of controls from NIST SP 800-172, focusing on defending against advanced persistent threats (APTs).

	NIST 800-171 Rev 2: The Foundation of CMMC 2.0:		=== NIST 800-171 Rev 2: The Foundation of CMMC 2.0: ===

	At the heart of CMMC Level 2 is NIST Special Publication 800-171 Revision 2, which outlines security requirements for protecting CUI in non-federal systems. Organizations must meet the 14 families of security requirements, which include:		At the heart of CMMC Level 2 is NIST Special Publication 800-171 Revision 2, which outlines security requirements for protecting CUI in non-federal systems. Organizations must meet the 14 families of security requirements, which include:

Marieramsay: Created page with "The Cybersecurity Maturity Model Certification (CMMC) is a framework designed to enhance cybersecurity practices across the Defense Industrial Base (DIB). It applies to any organization within the supply chain (receiving specific DFARS flow-down) that works on contracts with the Department of Defense (DoD), ensuring these companies can safeguard Controlled Unclassified Information (CUI) and Federal Contract Information (FCI). In November 2021, in response to industry fe..."

2024-09-26T22:27:14Z

Created page with "The Cybersecurity Maturity Model Certification (CMMC) is a framework designed to enhance cybersecurity practices across the Defense Industrial Base (DIB). It applies to any organization within the supply chain (receiving specific DFARS flow-down) that works on contracts with the Department of Defense (DoD), ensuring these companies can safeguard Controlled Unclassified Information (CUI) and Federal Contract Information (FCI). In November 2021, in response to industry fe..."

New page

The Cybersecurity Maturity Model Certification (CMMC) is a framework designed to enhance cybersecurity practices across the Defense Industrial Base (DIB). It applies to any organization within the supply chain (receiving specific DFARS flow-down) that works on contracts with the Department of Defense (DoD), ensuring these companies can safeguard Controlled Unclassified Information (CUI) and Federal Contract Information (FCI).

In November 2021, in response to industry feedback, CMMC 2.0 was introduced to simplify the original model, making compliance more achievable while maintaining strong security standards. This updated framework reduces the original five certification levels down to three:

Level 1: Basic cyber hygiene practices, primarily protecting FCI. Organizations must implement 17 practices aligned with Federal Acquisition Regulation (FAR) 52.204-21.

Level 2: Aligned with NIST SP 800-171 Rev 2, this level applies to companies that handle CUI. It includes 110 security controls required by NIST 800-171, emphasizing areas such as access control, incident response, and system security.

Level 3: Designed for companies with the highest cybersecurity requirements, Level 3 incorporates advanced practices beyond NIST SP 800-171 and will be aligned with a subset of controls from NIST SP 800-172, focusing on defending against advanced persistent threats (APTs).

NIST 800-171 Rev 2: The Foundation of CMMC 2.0:

At the heart of CMMC Level 2 is NIST Special Publication 800-171 Revision 2, which outlines security requirements for protecting CUI in non-federal systems. Organizations must meet the 14 families of security requirements, which include:

Access Control (AC)
Ensures that only authorized users have access to the information systems and CUI.
Example: Role-based access control (RBAC).

Awareness and Training (AT)
Ensures that users are trained and aware of security risks and organizational policies.
Example: Regular cybersecurity training sessions.

Audit and Accountability (AU)
Provides mechanisms to audit the system's activities and ensure users are accountable for their actions.
Example: Logging of all user activities for tracking and investigation.

Configuration Management (CM)
Involves managing security configurations of systems to reduce vulnerabilities.
Example: Ensuring systems have up-to-date security patches.

Identification and Authentication (IA)
Verifies user identities and provides mechanisms for authentication.
Example: Multi-factor authentication (MFA).

Incident Response (IR)
Prepares for, detects, and responds to security incidents.
Example: Incident reporting and remediation processes.

Maintenance (MA)
Provides procedures for system maintenance that protect the security of CUI during routine and emergency repairs.
Example: Remote maintenance procedures with authentication controls.

Media Protection (MP)
Ensures that physical and digital media containing CUI are protected from unauthorized access or loss.
Example: Encryption of removable storage devices.

Personnel Security (PS)
Ensures that personnel are properly vetted and that access to CUI is limited based on individual trustworthiness.
Example: Background checks for employees handling CUI.

Physical Protection (PE)
Restricts physical access to information systems, equipment, and operating environments.
Example: Secure data centers with controlled entry points.

Risk Assessment (RA)
Involves the identification and analysis of potential risks to information systems and CUI.
Example: Regular vulnerability scans and risk assessments.

Security Assessment (CA)
Regularly assesses and tests security controls to ensure they are effective.
Example: Third-party security audits.

System and Communications Protection (SC)
Ensures that communications between systems are secure and protected from unauthorized access.
Example: Encryption of data in transit and at rest.

System and Information Integrity (SI)
Protects systems and data by identifying and mitigating flaws and vulnerabilities.
Example: Continuous monitoring and timely application of security patches.

Meeting NIST 800-171 Rev 2 is crucial for achieving CMMC Level 2 certification and is mandatory for contractors handling CUI.

Self-Assessment and Third-Party Certification:

Under CMMC 2.0, organizations handling only FCI at Level 1 can conduct annual self-assessments. For Level 2, companies handling critical CUI must undergo third-party assessments or self-attest depending on the criticality of the contract. Level 3 requires comprehensive third-party assessments by the Defense Industrial Base Cybersecurity Assessment Center (DIBCAC).

Why CMMC is Important

The DoD created CMMC to ensure that companies in the DIB have adequate protections in place to secure sensitive information and defend against cyber threats. Compliance with CMMC 2.0 helps protect national security, secure supply chains, and build trust between the DoD and its contractors.

For organizations in the defense supply chain, preparing for CMMC 2.0 requires:

Implementing controls based on NIST 800-171 Rev 2 (for Level 2),

Engaging in continuous monitoring and security improvements,

And obtaining certification through third-party or self-assessments, depending on the level of compliance required.

← Older revision		Revision as of 22:45, 26 September 2024
Line 1:		Line 1:
	The Cybersecurity Maturity Model Certification (CMMC) is a framework designed to enhance cybersecurity practices across the Defense Industrial Base (DIB). It applies to any organization within the supply chain (receiving specific DFARS flow-down) that works on contracts with the Department of Defense (DoD), ensuring these companies can safeguard Controlled Unclassified Information (CUI) and Federal Contract Information (FCI).		The Cybersecurity Maturity Model Certification (CMMC) is a framework designed to enhance cybersecurity practices across the Defense Industrial Base ([[DIB]]). It applies to any organization within the supply chain (receiving specific [[DFARS]] flow-down) that works on contracts with the Department of Defense ([[DoD]]), ensuring these companies can safeguard Controlled Unclassified Information ([[CUI]]) and Federal Contract Information ([[FCI]]).

	In November 2021, in response to industry feedback, CMMC 2.0 was introduced to simplify the original model, making compliance more achievable while maintaining strong security standards. This updated framework reduces the original five certification levels down to three:		In November 2021, in response to industry feedback, CMMC 2.0 was introduced to simplify the original model, making compliance more achievable while maintaining strong security standards. This updated framework reduces the original five certification levels down to three:

	<u>Level 1:</u> Basic cyber hygiene practices, primarily protecting FCI. Organizations must implement 17 practices aligned with Federal Acquisition Regulation (FAR) 52.204-21.		<u>Level 1:</u> Basic cyber hygiene practices, primarily protecting FCI. Organizations must implement 17 practices aligned with Federal Acquisition Regulation ([[FAR]]) 52.204-21.

	<u>Level 2:</u> Aligned with NIST SP 800-171 Rev 2, this level applies to companies that handle CUI. It includes 110 security controls required by NIST 800-171, emphasizing areas such as access control, incident response, and system security.		<u>Level 2:</u> Aligned with NIST SP 800-171 Rev 2, this level applies to companies that handle CUI. It includes 110 security controls required by [[NIST 800-171]], emphasizing areas such as access control, incident response, and system security.

	<u>Level 3:</u> Designed for companies with the highest cybersecurity requirements, Level 3 incorporates advanced practices beyond NIST SP 800-171 and will be aligned with a subset of controls from NIST SP 800-172, focusing on defending against advanced persistent threats (~~APTs~~).		<u>Level 3:</u> Designed for companies with the highest cybersecurity requirements, Level 3 incorporates advanced practices beyond NIST SP 800-171 and will be aligned with a subset of controls from [[NIST SP 800-172]], focusing on defending against advanced persistent threats ([[APT]]s).

	=== NIST 800-171 Rev 2: The Foundation of CMMC 2.0: ===		=== NIST 800-171 Rev 2: The Foundation of CMMC 2.0: ===
Line 13:		Line 13:
	At the heart of CMMC Level 2 is NIST Special Publication 800-171 Revision 2, which outlines security requirements for protecting CUI in non-federal systems. Organizations must meet the 14 families of security requirements, which include:		At the heart of CMMC Level 2 is NIST Special Publication 800-171 Revision 2, which outlines security requirements for protecting CUI in non-federal systems. Organizations must meet the 14 families of security requirements, which include:

	'''Access Control (AC)'''		'''[[Access Control]] (AC)'''
	Ensures that only authorized users have access to the information systems and CUI.		Ensures that only authorized users have access to the information systems and CUI.
	Example: Role-based access control (RBAC).		Example: Role-based access control (RBAC).

	'''Awareness and Training (AT)'''		'''[[Awareness and Training]] (AT)'''
	Ensures that users are trained and aware of security risks and organizational policies.		Ensures that users are trained and aware of security risks and organizational policies.
	Example: Regular cybersecurity training sessions.		Example: Regular cybersecurity training sessions.

	'''Audit and Accountability (AU)'''		'''[[Audit and Accountability]] (AU)'''
	Provides mechanisms to audit the system's activities and ensure users are accountable for their actions.		Provides mechanisms to audit the system's activities and ensure users are accountable for their actions.
	Example: Logging of all user activities for tracking and investigation.		Example: Logging of all user activities for tracking and investigation.

	'''Configuration Management (CM)'''		'''[[Configuration Management]] (CM)'''
	Involves managing security configurations of systems to reduce vulnerabilities.		Involves managing security configurations of systems to reduce vulnerabilities.
	Example: Ensuring systems have up-to-date security patches.		Example: Ensuring systems have up-to-date security patches.

	'''Identification and Authentication (IA)'''		'''[[Identification and Authentication]] (IA)'''
	Verifies user identities and provides mechanisms for authentication.		Verifies user identities and provides mechanisms for authentication.
	Example: Multi-factor authentication (MFA).		Example: Multi-factor authentication (MFA).

	'''Incident Response (IR)'''		'''[[Incident Response]] (IR)'''
	Prepares for, detects, and responds to security incidents.		Prepares for, detects, and responds to security incidents.
	Example: Incident reporting and remediation processes.		Example: Incident reporting and remediation processes.

	'''Maintenance (MA)'''		'''[[Maintenance]] (MA)'''
	Provides procedures for system maintenance that protect the security of CUI during routine and emergency repairs.		Provides procedures for system maintenance that protect the security of CUI during routine and emergency repairs.
	Example: Remote maintenance procedures with authentication controls.		Example: Remote maintenance procedures with authentication controls.

	'''Media Protection (MP)'''		'''[[Media Protection]] (MP)'''
	Ensures that physical and digital media containing CUI are protected from unauthorized access or loss.		Ensures that physical and digital media containing CUI are protected from unauthorized access or loss.
	Example: Encryption of removable storage devices.		Example: Encryption of removable storage devices.

	'''Personnel Security (PS)'''		'''[[Personnel Security]] (PS)'''
	Ensures that personnel are properly vetted and that access to CUI is limited based on individual trustworthiness.		Ensures that personnel are properly vetted and that access to CUI is limited based on individual trustworthiness.
	Example: Background checks for employees handling CUI.		Example: Background checks for employees handling CUI.

	'''Physical Protection (PE)'''		'''[[Physical Protection]] (PE)'''
	Restricts physical access to information systems, equipment, and operating environments.		Restricts physical access to information systems, equipment, and operating environments.
	Example: Secure data centers with controlled entry points.		Example: Secure data centers with controlled entry points.

	'''Risk Assessment (RA)'''		'''[[Risk Assessment]] (RA)'''
	Involves the identification and analysis of potential risks to information systems and CUI.		Involves the identification and analysis of potential risks to information systems and CUI.
	Example: Regular vulnerability scans and risk assessments.		Example: Regular vulnerability scans and risk assessments.

	'''Security Assessment (CA)'''		'''[[Security Assessment]] (CA)'''
	Regularly assesses and tests security controls to ensure they are effective.		Regularly assesses and tests security controls to ensure they are effective.
	Example: Third-party security audits.		Example: Third-party security audits.

	'''System and Communications Protection (SC)'''		'''[[System and Communications Protection]] (SC)'''
	Ensures that communications between systems are secure and protected from unauthorized access.		Ensures that communications between systems are secure and protected from unauthorized access.
	Example: Encryption of data in transit and at rest.		Example: Encryption of data in transit and at rest.

	'''System and Information Integrity (SI)'''		'''[[System and Information Integrity]] (SI)'''
	Protects systems and data by identifying and mitigating flaws and vulnerabilities.		Protects systems and data by identifying and mitigating flaws and vulnerabilities.
	Example: Continuous monitoring and timely application of security patches.		Example: Continuous monitoring and timely application of security patches.
Line 71:		Line 71:
	Meeting NIST 800-171 Rev 2 is crucial for achieving CMMC Level 2 certification and is mandatory for contractors handling CUI.		Meeting NIST 800-171 Rev 2 is crucial for achieving CMMC Level 2 certification and is mandatory for contractors handling CUI.

	=== Self-Assessment and ~~Third-Party~~ Certification: ===		=== [[Self-Assessment and Certification]]: ===

	Under CMMC 2.0, organizations handling only FCI at Level 1 can conduct annual self-assessments. For Level 2, companies handling critical CUI must undergo third-party assessments or self-attest depending on the criticality of the contract. Level 3 requires comprehensive third-party assessments by the Defense Industrial Base Cybersecurity Assessment Center (DIBCAC).		Under CMMC 2.0, organizations handling only FCI at Level 1 can conduct annual self-assessments. For Level 2, companies handling critical CUI must undergo third-party assessments or self-attest depending on the criticality of the contract. Level 3 requires comprehensive third-party assessments by the Defense Industrial Base Cybersecurity Assessment Center (DIBCAC).
Line 83:		Line 83:
	* Implementing controls based on NIST 800-171 Rev 2 (for Level 2),		* Implementing controls based on NIST 800-171 Rev 2 (for Level 2),

	* Engaging in continuous monitoring and security improvements,		* Engaging in [[continuous monitoring]] and [[security improvements]],

	* And obtaining certification through third-party or self-assessments, depending on the level of compliance required.		* And obtaining certification through third-party or self-assessments, depending on the level of compliance required.

← Older revision		Revision as of 22:31, 26 September 2024
Line 3:		Line 3:
	In November 2021, in response to industry feedback, CMMC 2.0 was introduced to simplify the original model, making compliance more achievable while maintaining strong security standards. This updated framework reduces the original five certification levels down to three:		In November 2021, in response to industry feedback, CMMC 2.0 was introduced to simplify the original model, making compliance more achievable while maintaining strong security standards. This updated framework reduces the original five certification levels down to three:

	Level 1: Basic cyber hygiene practices, primarily protecting FCI. Organizations must implement 17 practices aligned with Federal Acquisition Regulation (FAR) 52.204-21.		<u>Level 1:</u> Basic cyber hygiene practices, primarily protecting FCI. Organizations must implement 17 practices aligned with Federal Acquisition Regulation (FAR) 52.204-21.

	Level 2: Aligned with NIST SP 800-171 Rev 2, this level applies to companies that handle CUI. It includes 110 security controls required by NIST 800-171, emphasizing areas such as access control, incident response, and system security.		<u>Level 2:</u> Aligned with NIST SP 800-171 Rev 2, this level applies to companies that handle CUI. It includes 110 security controls required by NIST 800-171, emphasizing areas such as access control, incident response, and system security.

	Level 3: Designed for companies with the highest cybersecurity requirements, Level 3 incorporates advanced practices beyond NIST SP 800-171 and will be aligned with a subset of controls from NIST SP 800-172, focusing on defending against advanced persistent threats (APTs).		<u>Level 3:</u> Designed for companies with the highest cybersecurity requirements, Level 3 incorporates advanced practices beyond NIST SP 800-171 and will be aligned with a subset of controls from NIST SP 800-172, focusing on defending against advanced persistent threats (APTs).

	=== NIST 800-171 Rev 2: The Foundation of CMMC 2.0: ===		=== NIST 800-171 Rev 2: The Foundation of CMMC 2.0: ===
Line 21:		Line 21:
	Example: Regular cybersecurity training sessions.		Example: Regular cybersecurity training sessions.

	Audit and Accountability (AU)		'''Audit and Accountability (AU)'''
	Provides mechanisms to audit the system's activities and ensure users are accountable for their actions.		Provides mechanisms to audit the system's activities and ensure users are accountable for their actions.
	Example: Logging of all user activities for tracking and investigation.		Example: Logging of all user activities for tracking and investigation.

	Configuration Management (CM)		'''Configuration Management (CM)'''
	Involves managing security configurations of systems to reduce vulnerabilities.		Involves managing security configurations of systems to reduce vulnerabilities.
	Example: Ensuring systems have up-to-date security patches.		Example: Ensuring systems have up-to-date security patches.

	Identification and Authentication (IA)		'''Identification and Authentication (IA)'''
	Verifies user identities and provides mechanisms for authentication.		Verifies user identities and provides mechanisms for authentication.
	Example: Multi-factor authentication (MFA).		Example: Multi-factor authentication (MFA).

	Incident Response (IR)		'''Incident Response (IR)'''
	Prepares for, detects, and responds to security incidents.		Prepares for, detects, and responds to security incidents.
	Example: Incident reporting and remediation processes.		Example: Incident reporting and remediation processes.

	Maintenance (MA)		'''Maintenance (MA)'''
	Provides procedures for system maintenance that protect the security of CUI during routine and emergency repairs.		Provides procedures for system maintenance that protect the security of CUI during routine and emergency repairs.
	Example: Remote maintenance procedures with authentication controls.		Example: Remote maintenance procedures with authentication controls.

	Media Protection (MP)		'''Media Protection (MP)'''
	Ensures that physical and digital media containing CUI are protected from unauthorized access or loss.		Ensures that physical and digital media containing CUI are protected from unauthorized access or loss.
	Example: Encryption of removable storage devices.		Example: Encryption of removable storage devices.

	Personnel Security (PS)		'''Personnel Security (PS)'''
	Ensures that personnel are properly vetted and that access to CUI is limited based on individual trustworthiness.		Ensures that personnel are properly vetted and that access to CUI is limited based on individual trustworthiness.
	Example: Background checks for employees handling CUI.		Example: Background checks for employees handling CUI.

	Physical Protection (PE)		'''Physical Protection (PE)'''
	Restricts physical access to information systems, equipment, and operating environments.		Restricts physical access to information systems, equipment, and operating environments.
	Example: Secure data centers with controlled entry points.		Example: Secure data centers with controlled entry points.

	Risk Assessment (RA)		'''Risk Assessment (RA)'''
	Involves the identification and analysis of potential risks to information systems and CUI.		Involves the identification and analysis of potential risks to information systems and CUI.
	Example: Regular vulnerability scans and risk assessments.		Example: Regular vulnerability scans and risk assessments.

	Security Assessment (CA)		'''Security Assessment (CA)'''
	Regularly assesses and tests security controls to ensure they are effective.		Regularly assesses and tests security controls to ensure they are effective.
	Example: Third-party security audits.		Example: Third-party security audits.

	System and Communications Protection (SC)		'''System and Communications Protection (SC)'''
	Ensures that communications between systems are secure and protected from unauthorized access.		Ensures that communications between systems are secure and protected from unauthorized access.
	Example: Encryption of data in transit and at rest.		Example: Encryption of data in transit and at rest.

	System and Information Integrity (SI)		'''System and Information Integrity (SI)'''
	Protects systems and data by identifying and mitigating flaws and vulnerabilities.		Protects systems and data by identifying and mitigating flaws and vulnerabilities.
	Example: Continuous monitoring and timely application of security patches.		Example: Continuous monitoring and timely application of security patches.
Line 81:		Line 81:
	For organizations in the defense supply chain, preparing for CMMC 2.0 requires:		For organizations in the defense supply chain, preparing for CMMC 2.0 requires:

	Implementing controls based on NIST 800-171 Rev 2 (for Level 2),		* Implementing controls based on NIST 800-171 Rev 2 (for Level 2),

	Engaging in continuous monitoring and security improvements,		* Engaging in continuous monitoring and security improvements,

	And obtaining certification through third-party or self-assessments, depending on the level of compliance required.		* And obtaining certification through third-party or self-assessments, depending on the level of compliance required.

← Older revision		Revision as of 22:30, 26 September 2024
Line 13:		Line 13:
	At the heart of CMMC Level 2 is NIST Special Publication 800-171 Revision 2, which outlines security requirements for protecting CUI in non-federal systems. Organizations must meet the 14 families of security requirements, which include:		At the heart of CMMC Level 2 is NIST Special Publication 800-171 Revision 2, which outlines security requirements for protecting CUI in non-federal systems. Organizations must meet the 14 families of security requirements, which include:

	Access Control (AC)		'''Access Control (AC)'''
	Ensures that only authorized users have access to the information systems and CUI.		Ensures that only authorized users have access to the information systems and CUI.
	Example: Role-based access control (RBAC).		Example: Role-based access control (RBAC).

	Awareness and Training (AT)		'''Awareness and Training (AT)'''
	Ensures that users are trained and aware of security risks and organizational policies.		Ensures that users are trained and aware of security risks and organizational policies.
	Example: Regular cybersecurity training sessions.		Example: Regular cybersecurity training sessions.
Line 71:		Line 71:
	Meeting NIST 800-171 Rev 2 is crucial for achieving CMMC Level 2 certification and is mandatory for contractors handling CUI.		Meeting NIST 800-171 Rev 2 is crucial for achieving CMMC Level 2 certification and is mandatory for contractors handling CUI.

	Self-Assessment and Third-Party Certification:		=== Self-Assessment and Third-Party Certification: ===

	Under CMMC 2.0, organizations handling only FCI at Level 1 can conduct annual self-assessments. For Level 2, companies handling critical CUI must undergo third-party assessments or self-attest depending on the criticality of the contract. Level 3 requires comprehensive third-party assessments by the Defense Industrial Base Cybersecurity Assessment Center (DIBCAC).		Under CMMC 2.0, organizations handling only FCI at Level 1 can conduct annual self-assessments. For Level 2, companies handling critical CUI must undergo third-party assessments or self-attest depending on the criticality of the contract. Level 3 requires comprehensive third-party assessments by the Defense Industrial Base Cybersecurity Assessment Center (DIBCAC).

	Why CMMC is Important		=== Why CMMC is Important ===

	The DoD created CMMC to ensure that companies in the DIB have adequate protections in place to secure sensitive information and defend against cyber threats. Compliance with CMMC 2.0 helps protect national security, secure supply chains, and build trust between the DoD and its contractors.		The DoD created CMMC to ensure that companies in the DIB have adequate protections in place to secure sensitive information and defend against cyber threats. Compliance with CMMC 2.0 helps protect national security, secure supply chains, and build trust between the DoD and its contractors.