+RA-05 Vulnerability Monitoring and Scanning
---+RA-05(02) Update Vulnerabilities to Be Scanned
---+RA-05(03) Breadth and Depth of Coverage
---+RA-05(04) Discoverable Information
---+RA-05(05) Privileged Access
---+RA-05(06) Automated Trend Analyses
---+RA-05(08) Review Historic Audit Logs
---+RA-05(10) Correlate Scanning Information
---+RA-05(11) Public Disclosure Program
|
RA-05 Vulnerability Monitoring and Scanning
Control
- Monitor and scan for vulnerabilities in the system and hosted applications [Assignement: organization-defined frequency and/or randomly in accordance with organization-defined process] and when new vulnerabilities potentially affecting the system are identified and reported;
- Employ vulnerability monitoring tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for:
- Enumerating platforms, software flaws, and improper configurations;
- Formatting checklists and test procedures; and
- Measuring vulnerability impact;
- Analyze vulnerability scan reports and results from vulnerability monitoring;
- Remediate legitimate vulnerabilities [Assignement: response times] in accordance with an organizational assessment of risk;
- Share information obtained from the vulnerability monitoring process and control assessments with [Assignement: personnel or roles] to help eliminate similar vulnerabilities in other systems; and
- Employ vulnerability monitoring tools that include the capability to readily update the vulnerabilities to be scanned.
Discussion
Security categorization of information and systems guides the frequency and comprehensiveness of vulnerability monitoring (including scans). Organizations determine the required vulnerability monitoring for system components, ensuring that the potential sources of vulnerabilities—such as infrastructure components (e.g., switches, routers, guards, sensors), networked printers, scanners, and copiers—are not overlooked. The capability to readily update vulnerability monitoring tools as new vulnerabilities are discovered and announced and as new scanning methods are developed helps to ensure that new vulnerabilities are not missed by employed vulnerability monitoring tools. The vulnerability monitoring tool update process helps to ensure that potential vulnerabilities in the system are identified and addressed as quickly as possible. Vulnerability monitoring and analyses for custom software may require additional approaches, such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Organizations can use these analysis approaches in source code reviews and in a variety of tools, including web-based application scanners, static analysis tools, and binary analyzers.
Vulnerability monitoring includes scanning for patch levels; scanning for functions, ports, protocols, and services that should not be accessible to users or devices; and scanning for flow control mechanisms that are improperly configured or operating incorrectly. Vulnerability monitoring may also include continuous vulnerability monitoring tools that use instrumentation to continuously analyze components. Instrumentation-based tools may improve accuracy and may be run throughout an organization without scanning. Vulnerability monitoring tools that facilitate interoperability include tools that are Security Content Automated Protocol (SCAP)-validated. Thus, organizations consider using scanning tools that express vulnerabilities in the Common Vulnerabilities and Exposures (CVE) naming convention and that employ the Open Vulnerability Assessment Language (OVAL) to determine the presence of vulnerabilities. Sources for vulnerability information include the Common Weakness Enumeration (CWE) listing and the National Vulnerability Database (NVD). Control assessments, such as red team exercises, provide additional sources of potential vulnerabilities for which to scan. Organizations also consider using scanning tools that express vulnerability impact by the Common Vulnerability Scoring System (CVSS).
Vulnerability monitoring includes a channel and process for receiving reports of security vulnerabilities from the public at-large. Vulnerability disclosure programs can be as simple as publishing a monitored email address or web form that can receive reports, including notification authorizing good-faith research and disclosure of security vulnerabilities. Organizations generally expect that such research is happening with or without their authorization and can use public vulnerability disclosure channels to increase the likelihood that discovered vulnerabilities are reported directly to the organization for remediation.
Organizations may also employ the use of financial incentives (also known as "bug bounties" ) to further encourage external security researchers to report discovered vulnerabilities. Bug bounty programs can be tailored to the organization’s needs. Bounties can be operated indefinitely or over a defined period of time and can be offered to the general public or to a curated group. Organizations may run public and private bounties simultaneously and could choose to offer partially credentialed access to certain participants in order to evaluate security vulnerabilities from privileged vantage points.
Assessment Objective
- systems and hosted applications are monitored for vulnerabilities [Assignement: frequency and/or randomly in accordance with organization-defined process] and when new vulnerabilities potentially affecting the system are identified and reported;
- systems and hosted applications are scanned for vulnerabilities [Assignement: frequency and/or randomly in accordance with organization-defined process] and when new vulnerabilities potentially affecting the system are identified and reported;
- vulnerability monitoring tools and techniques are employed to facilitate interoperability among tools;
- vulnerability monitoring tools and techniques are employed to automate parts of the vulnerability management process by using standards for enumerating platforms, software flaws, and improper configurations;
- vulnerability monitoring tools and techniques are employed to facilitate interoperability among tools and to automate parts of the vulnerability management process by using standards for formatting checklists and test procedures;
- vulnerability monitoring tools and techniques are employed to facilitate interoperability among tools and to automate parts of the vulnerability management process by using standards for measuring vulnerability impact;
- vulnerability scan reports and results from vulnerability monitoring are analyzed;
- legitimate vulnerabilities are remediated [Assignement: response times] in accordance with an organizational assessment of risk;
- information obtained from the vulnerability monitoring process and control assessments is shared with [Assignement: personnel or roles] to help eliminate similar vulnerabilities in other systems;
- vulnerability monitoring tools that include the capability to readily update the vulnerabilities to be scanned are employed.
Assessment Method
Examine
Risk assessment policy
procedures addressing vulnerability scanning
risk assessment
assessment report
vulnerability scanning tools and associated configuration documentation
vulnerability scanning results
patch and vulnerability management records
system security plan
other relevant documents or records
Interview
Organizational personnel with risk assessment, control assessment, and vulnerability scanning responsibilities
organizational personnel with vulnerability scan analysis responsibilities
organizational personnel with vulnerability remediation responsibilities
organizational personnel with security responsibilities
system/network administrators
1. Oversigt
| Titel |
Standard |
|
RA-05(02) Update Vulnerabilities to Be Scanned
|
Control
Update the system vulnerabilities to be scanned [Selection(one-or-more): {{ insert: param, ra-05.02_odp.02 }} ; prior to a new scan; when new vulnerabilities are identified and reported].
Discussion
Due to the complexity of modern software, systems, and other factors, new vulnerabilities are discovered on a regular basis. It is important that newly discovered vulnerabilities are added to the list of vulnerabilities to be scanned to ensure that the organization can take steps to mitigate those vulnerabilities in a timely manner.
Assessment Objective
the system vulnerabilities to be scanned are updated [Selection(one-or-more): {{ insert: param, ra-05.02_odp.02 }} ; prior to a new scan; when new vulnerabilities are identified and reported].
Assessment Method
Examine
Procedures addressing vulnerability scanning
assessment report
vulnerability scanning tools and associated configuration documentation
vulnerability scanning results
patch and vulnerability management records
system security plan
other relevant documents or records
Interview
Organizational personnel with vulnerability scanning responsibilities
organizational personnel with vulnerability scan analysis responsibilities
organizational personnel with security responsibilities
system/network administrators
|
|
RA-05(03) Breadth and Depth of Coverage
|
Control
Define the breadth and depth of vulnerability scanning coverage.
Discussion
The breadth of vulnerability scanning coverage can be expressed as a percentage of components within the system, by the particular types of systems, by the criticality of systems, or by the number of vulnerabilities to be checked. Conversely, the depth of vulnerability scanning coverage can be expressed as the level of the system design that the organization intends to monitor (e.g., component, module, subsystem, element). Organizations can determine the sufficiency of vulnerability scanning coverage with regard to its risk tolerance and other factors. Scanning tools and how the tools are configured may affect the depth and coverage. Multiple scanning tools may be needed to achieve the desired depth and coverage. [SP 800-53A](#a21aef46-7330-48a0-b2e1-c5bb8b2dd11d) provides additional information on the breadth and depth of coverage.
Assessment Objective
the breadth and depth of vulnerability scanning coverage are defined.
Assessment Method
Examine
Procedures addressing vulnerability scanning
assessment report
vulnerability scanning tools and associated configuration documentation
vulnerability scanning results
patch and vulnerability management records
system security plan
other relevant documents or records
Interview
Organizational personnel with vulnerability scanning responsibilities
organizational personnel with vulnerability scan analysis responsibilities
organizational personnel with security responsibilities
|
|
RA-05(04) Discoverable Information
|
Control
Determine information about the system that is discoverable and take [Assignement: corrective actions].
Discussion
Discoverable information includes information that adversaries could obtain without compromising or breaching the system, such as by collecting information that the system is exposing or by conducting extensive web searches. Corrective actions include notifying appropriate organizational personnel, removing designated information, or changing the system to make the designated information less relevant or attractive to adversaries. This enhancement excludes intentionally discoverable information that may be part of a decoy capability (e.g., honeypots, honeynets, or deception nets) deployed by the organization.
Assessment Objective
- information about the system is discoverable;
- [Assignement: corrective actions] are taken when information about the system is confirmed as discoverable.
Assessment Method
Examine
Procedures addressing vulnerability scanning
assessment report
penetration test results
vulnerability scanning results
risk assessment report
records of corrective actions taken
incident response records
audit records
system security plan
other relevant documents or records
Interview
Organizational personnel with vulnerability scanning and/or penetration testing responsibilities
organizational personnel with vulnerability scan analysis responsibilities
organizational personnel responsible for risk response
organizational personnel responsible for incident management and response
organizational personnel with security responsibilities
|
|
RA-05(05) Privileged Access
|
Control
Implement privileged access authorization to [Assignement: system components] for [Assignement: vulnerability scanning activities].
Discussion
In certain situations, the nature of the vulnerability scanning may be more intrusive, or the system component that is the subject of the scanning may contain classified or controlled unclassified information, such as personally identifiable information. Privileged access authorization to selected system components facilitates more thorough vulnerability scanning and protects the sensitive nature of such scanning.
Assessment Objective
privileged access authorization is implemented to [Assignement: system components] for [Assignement: vulnerability scanning activities].
Assessment Method
Examine
Risk assessment policy
procedures addressing vulnerability scanning
system design documentation
system configuration settings and associated documentation
list of system components for vulnerability scanning
personnel access authorization list
authorization credentials
access authorization records
system security plan
other relevant documents or records
Interview
Organizational personnel with vulnerability scanning responsibilities
system/network administrators
organizational personnel responsible for access control to the system
organizational personnel responsible for configuration management of the system
system developers
organizational personnel with security responsibilities
|
|
RA-05(06) Automated Trend Analyses
|
Control
Compare the results of multiple vulnerability scans using [Assignement: automated mechanisms].
Discussion
Using automated mechanisms to analyze multiple vulnerability scans over time can help determine trends in system vulnerabilities and identify patterns of attack.
Assessment Objective
the results of multiple vulnerability scans are compared using [Assignement: automated mechanisms].
Assessment Method
Examine
Risk assessment policy
procedures addressing vulnerability scanning
system design documentation
vulnerability scanning tools and techniques documentation
vulnerability scanning results
system security plan
other relevant documents or records
Interview
Organizational personnel with vulnerability scanning responsibilities
organizational personnel with vulnerability scan analysis responsibilities
organizational personnel with security responsibilities
|
|
RA-05(08) Review Historic Audit Logs
|
Control
Review historic audit logs to determine if a vulnerability identified in a [Assignement: system] has been previously exploited within an [Assignement: time period].
Discussion
Reviewing historic audit logs to determine if a recently detected vulnerability in a system has been previously exploited by an adversary can provide important information for forensic analyses. Such analyses can help identify, for example, the extent of a previous intrusion, the trade craft employed during the attack, organizational information exfiltrated or modified, mission or business capabilities affected, and the duration of the attack.
Assessment Objective
historic audit logs are reviewed to determine if a vulnerability identified in a [Assignement: system] has been previously exploited within [Assignement: time period].
Assessment Method
Examine
Risk assessment policy
procedures addressing vulnerability scanning
audit logs
records of audit log reviews
vulnerability scanning results
patch and vulnerability management records
system security plan
other relevant documents or records
Interview
Organizational personnel with vulnerability scanning responsibilities
organizational personnel with vulnerability scan analysis responsibilities
organizational personnel with audit record review responsibilities
system/network administrators
organizational personnel with security responsibilities
|
|
RA-05(10) Correlate Scanning Information
|
Control
Correlate the output from vulnerability scanning tools to determine the presence of multi-vulnerability and multi-hop attack vectors.
Discussion
An attack vector is a path or means by which an adversary can gain access to a system in order to deliver malicious code or exfiltrate information. Organizations can use attack trees to show how hostile activities by adversaries interact and combine to produce adverse impacts or negative consequences to systems and organizations. Such information, together with correlated data from vulnerability scanning tools, can provide greater clarity regarding multi-vulnerability and multi-hop attack vectors. The correlation of vulnerability scanning information is especially important when organizations are transitioning from older technologies to newer technologies (e.g., transitioning from IPv4 to IPv6 network protocols). During such transitions, some system components may inadvertently be unmanaged and create opportunities for adversary exploitation.
Assessment Objective
the output from vulnerability scanning tools is correlated to determine the presence of multi-vulnerability and multi-hop attack vectors.
Assessment Method
Examine
Risk assessment policy
procedures addressing vulnerability scanning
risk assessment
vulnerability scanning tools and techniques documentation
vulnerability scanning results
vulnerability management records
audit records
event/vulnerability correlation logs
system security plan
other relevant documents or records
Interview
Organizational personnel with vulnerability scanning responsibilities
organizational personnel with vulnerability scan analysis responsibilities
organizational personnel with security responsibilities
|
|
RA-05(11) Public Disclosure Program
|
Control
Establish a public reporting channel for receiving reports of vulnerabilities in organizational systems and system components.
Discussion
The reporting channel is publicly discoverable and contains clear language authorizing good-faith research and the disclosure of vulnerabilities to the organization. The organization does not condition its authorization on an expectation of indefinite non-disclosure to the public by the reporting entity but may request a specific time period to properly remediate the vulnerability.
Assessment Objective
a public reporting channel is established for receiving reports of vulnerabilities in organizational systems and system components.
Assessment Method
Examine
Risk assessment policy
procedures addressing vulnerability scanning
risk assessment
vulnerability scanning tools and techniques documentation
vulnerability scanning results
vulnerability management records
audit records
public reporting channel
system security plan
other relevant documents or records
Interview
Organizational personnel with vulnerability scanning responsibilities
organizational personnel with vulnerability scan analysis responsibilities
organizational personnel with security responsibilities
|
1.1 Referencer
1.2 Identificerede krav
1.3 Relaterede reguleringer
2. Identificerede krav
3. Relaterede reguleringer
Reguleringer
| Kilde |
Regulering |
Linkede sager
|