View source for Practice SI.L2-3.14.3 Details

'''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.

== SI.L2-3.14.3 – SECURITY ALERTS & ADVISORIES ==
===SECURITY REQUIREMENT ===
Monitor system security alerts and advisories and take action in response.
=== ASSESSMENT OBJECTIVES ===
Determine if:
: [a] response actions to system security alerts and advisories are identified;
: [b] system security alerts and advisories are monitored; and
: [c] actions in response to system security alerts and advisories are taken.
=== POTENTIAL ASSESSMENT METHODS AND OBJECTS ===
'''Examine'''

[SELECT FROM: System and information integrity policy; procedures addressing security alerts, advisories, and directives; system security plan; records of security alerts and advisories; other relevant documents or records].

'''Interview'''

[SELECT FROM: Personnel with security alert and advisory responsibilities;personnel implementing, operating, maintaining, and using the system;personnel, organizational elements, and external organizations to whom alerts, advisories, and directives are to be disseminated;system or network administrators;personnel with information security responsibilities].

'''Test'''

[SELECT FROM: Organizational processes for defining, receiving, generating, disseminating, and complying with security alerts, advisories, and directives; mechanisms supporting or implementing definition, receipt, generation, and dissemination of security alerts, advisories, and directives; mechanisms supporting or implementing security directives].
=== DISCUSSION ===
There are many publicly available sources of system security alerts and advisories. The United States Computer Emergency Readiness Team (US-CERT) generates security alerts and advisories to maintain situational awareness across the federal government and in nonfederal organizations. Software vendors, subscription services, and relevant industry information sharing and analysis centers (ISACs) may also provide security alerts and advisories. Examples of response actions include notifying relevant external organizations, For example, external mission/business partners, supply chain partners, external service providers, and peer or supporting organizations.

NIST SP 800-161 provides guidance on supply chain risk management.
=== FURTHER DISCUSSION ===
Solicit and receive security alerts, advisories, and directives from reputable external organizations.Identify sources relevant to the industry and technology used by your company. Methods to receive alerts and advisories may include:
* signing up for email distributions;
* subscribing to RSS feeds; and
* attending meetings.

Review alerts and advisories for applicability as they are received. The frequency of the reviews should be based on the frequency of the alerts and advisories to ensure you have the most up-to-date information.

External alerts and advisories may prompt you to generate internal security alerts, advisories, or directives, and share these with all personnel with a need-to-know. The individuals should assess the risk related to a given alert and act to respond as appropriate.Sometimes it may require a configuration update. Other times, the information may also require adjusting system architecture in order to thwart a threat described in an advisory.

'''Example'''

You monitor security advisories each week.You review the alert emails and online subscription service alerts to determine which ones apply [b]. You create a list of the applicable alerts and research what steps you need to take to address them. Next, you generate a plan that you review with your change management group so that the work can be scheduled [c].

'''Potential Assessment Considerations'''
* Are the responses to system security alerts and advisories identified in relation to the assessed severity of potential flaws (e.g., communicating with responsible personnel, initiating vulnerability scans, initiating system flaw remediation activities) [a]?
* Are system security alerts and advisories addressed (e.g., assessing potential severity or likelihood, communicating with responsible personnel, initiating vulnerability scans, initiating system flaw remediation activities) [a,c]?
=== KEY REFERENCES ===
* NIST SP 800-171 Rev 2 3.14.3