Practice RA.L2-3.11.3 Details - Revision history

David: /* FURTHER DISCUSSION */

2025-04-13T21:54:01Z

FURTHER DISCUSSION

← Older revision		Revision as of 21:54, 13 April 2025
Line 34:		Line 34:

	'''Potential Assessment Considerations'''		'''Potential Assessment Considerations'''
	* Are the results of risk assessments used to prioritize vulnerabilities for remediation [b]? * For any given vulnerability is action taken for remediation, acceptance, avoidance, or transference of the vulnerability risk [b]?		* Are the results of risk assessments used to prioritize vulnerabilities for remediation [b]?
			* For any given vulnerability is action taken for remediation, acceptance, avoidance, or transference of the vulnerability risk [b]?
	* Are all high risk vulnerabilities prioritized [b]?		* Are all high risk vulnerabilities prioritized [b]?

	=== KEY REFERENCES ===		=== KEY REFERENCES ===
	* NIST SP 800-171 Rev 2 3.11.3		* NIST SP 800-171 Rev 2 3.11.3

David at 00:36, 16 March 2025

2025-03-16T00:36:39Z

← Older revision		Revision as of 00:36, 16 March 2025
Line 1:		Line 1:
	'''Source of Reference: The official [https://~~www~~.~~acq~~.~~osd.mil~~/cmmc/~~documentation.html~~ CMMC Level 2 Assessment Guide] from the ~~Office of the Under Secretary~~ of Defense ~~Acquisition & Sustainment~~.'''		'''Source of Reference: The official [https://dodcio.defense.gov/cmmc/Resources-Documentation/ CMMC Level 2 Assessment Guide] from the Department of Defense Chief Information Officer (DoD CIO).'''

	For inquiries and reporting errors on this wiki, please [mailto:support@cmmctoolkit.org contact us]. Thank you.		For inquiries and reporting errors on this wiki, please [mailto:support@cmmctoolkit.org contact us]. Thank you.
Line 13:		Line 13:
	'''Examine'''		'''Examine'''

	[SELECT FROM: Risk assessment policy; procedures addressing vulnerability scanning; risk assessment; system security plan; security assessment report; vulnerability scanning tools and associated configuration documentation;vulnerability scanning results;patch and vulnerability management records; other relevant documents or records].		[SELECT FROM: Risk assessment policy; procedures addressing vulnerability scanning; risk assessment; system security plan; security assessment report; vulnerability scanning tools and associated configuration documentation; vulnerability scanning results; patch and vulnerability management records; other relevant documents or records].

	'''Interview'''		'''Interview'''

	[SELECT FROM: Personnel with risk assessment, security assessment and vulnerability scanning responsibilities;personnel with vulnerability scan analysis responsibilities;personnel with vulnerability remediation responsibilities;personnel with information security responsibilities; system or network administrators].		[SELECT FROM: Personnel with risk assessment, security assessment and vulnerability scanning responsibilities; personnel with vulnerability scan analysis responsibilities; personnel with vulnerability remediation responsibilities; personnel with information security responsibilities; system or network administrators].

	'''Test'''		'''Test'''
Line 25:		Line 25:
	Vulnerabilities discovered, for example, via the scanning conducted in response to RA.L2- 3.11.2, are remediated with consideration of the related assessment of risk. The consideration of risk influences the prioritization of remediation efforts and the level of effort to be expended in the remediation for specific vulnerabilities.		Vulnerabilities discovered, for example, via the scanning conducted in response to RA.L2- 3.11.2, are remediated with consideration of the related assessment of risk. The consideration of risk influences the prioritization of remediation efforts and the level of effort to be expended in the remediation for specific vulnerabilities.
	=== FURTHER DISCUSSION ===		=== FURTHER DISCUSSION ===
	Not all vulnerabilities captured in a vulnerability scanner may pose the same level of risk to an organization. Prioritize mitigation efforts to close the most critical vulnerabilities first.Track all vulnerability remediation to ensure completion; also track vulnerabilities that you have determined not to remediate.		Not all vulnerabilities captured in a vulnerability scanner may pose the same level of risk to an organization. Prioritize mitigation efforts to close the most critical vulnerabilities first. Track all vulnerability remediation to ensure completion; also track vulnerabilities that you have determined not to remediate.

	This practice, RA.L2-3.11.3, benefits from CA.L2-3.12.2. RA.L2-3.11.3 allows remediation of vulnerabilities to take place based on the developed plans of actions for vulnerabilities from CA.L2-3.12.2.		This practice, RA.L2-3.11.3, benefits from CA.L2-3.12.2. RA.L2-3.11.3 allows remediation of vulnerabilities to take place based on the developed plans of actions for vulnerabilities from CA.L2-3.12.2.

Wikiadmin: Created page with "'''Source of Reference: The official [https://www.acq.osd.mil/cmmc/documentation.html CMMC Level 2 Assessment Guide] from the Office of the Under Secretary of Defense Acquisition & Sustainment.''' For inquiries and reporting errors on this wiki, please [mailto:support@cmmctoolkit.org contact us]. Thank you. == RA.L2-3.11.3 – VULNERABILITY REMEDIATION == === SECURITY REQUIREMENT === Remediate vulnerabilities in accordance with risk assessments. === ASSESSMENT OBJECTIV..."

2022-02-24T18:34:06Z

Created page with "'''Source of Reference: The official [https://www.acq.osd.mil/cmmc/documentation.html CMMC Level 2 Assessment Guide] from the Office of the Under Secretary of Defense Acquisition & Sustainment.''' For inquiries and reporting errors on this wiki, please [mailto:support@cmmctoolkit.org contact us]. Thank you. == RA.L2-3.11.3 – VULNERABILITY REMEDIATION == === SECURITY REQUIREMENT === Remediate vulnerabilities in accordance with risk assessments. === ASSESSMENT OBJECTIV..."

New page

'''Source of Reference: The official [https://www.acq.osd.mil/cmmc/documentation.html CMMC Level 2 Assessment Guide] from the Office of the Under Secretary of Defense Acquisition & Sustainment.'''

For inquiries and reporting errors on this wiki, please [mailto:support@cmmctoolkit.org contact us]. Thank you.

== RA.L2-3.11.3 – VULNERABILITY REMEDIATION ==
=== SECURITY REQUIREMENT ===
Remediate vulnerabilities in accordance with risk assessments.
=== ASSESSMENT OBJECTIVES ===
Determine if:
: [a] vulnerabilities are identified; and
: [b] vulnerabilities are remediated in accordance with risk assessments.
=== POTENTIAL ASSESSMENT METHODS AND OBJECTS ===
'''Examine'''

[SELECT FROM: Risk assessment policy; procedures addressing vulnerability scanning; risk assessment; system security plan; security assessment report; vulnerability scanning tools and associated configuration documentation;vulnerability scanning results;patch and vulnerability management records; other relevant documents or records].

'''Interview'''

[SELECT FROM: Personnel with risk assessment, security assessment and vulnerability scanning responsibilities;personnel with vulnerability scan analysis responsibilities;personnel with vulnerability remediation responsibilities;personnel with information security responsibilities; system or network administrators].

'''Test'''

[SELECT FROM: Organizational processes for vulnerability scanning, analysis, remediation, and information sharing; mechanisms supporting or implementing vulnerability scanning, analysis, remediation, and information sharing].
=== DISCUSSION ===
Vulnerabilities discovered, for example, via the scanning conducted in response to RA.L2- 3.11.2, are remediated with consideration of the related assessment of risk. The consideration of risk influences the prioritization of remediation efforts and the level of effort to be expended in the remediation for specific vulnerabilities.
=== FURTHER DISCUSSION ===
Not all vulnerabilities captured in a vulnerability scanner may pose the same level of risk to an organization. Prioritize mitigation efforts to close the most critical vulnerabilities first.Track all vulnerability remediation to ensure completion; also track vulnerabilities that you have determined not to remediate.

This practice, RA.L2-3.11.3, benefits from CA.L2-3.12.2. RA.L2-3.11.3 allows remediation of vulnerabilities to take place based on the developed plans of actions for vulnerabilities from CA.L2-3.12.2.

'''Example'''

You are a system administrator. Each quarter you receive a list of vulnerabilities generated by your company’s vulnerability scanner [a].You prioritize that list and note which vulnerabilities should be targeted as soon as possible as well as which vulnerabilities you can safely defer addressing at this time. You document the reasoning behind accepting the risk of the unremediated flaws and note to continue to monitor these vulnerabilities in case you need to revise the decision at a later date [b].

'''Potential Assessment Considerations'''
* Are the results of risk assessments used to prioritize vulnerabilities for remediation [b]? * For any given vulnerability is action taken for remediation, acceptance, avoidance, or transference of the vulnerability risk [b]?
* Are all high risk vulnerabilities prioritized [b]?
=== KEY REFERENCES ===
* NIST SP 800-171 Rev 2 3.11.3