+RA-05 [M] Vulnerability Monitoring and Scanning
---+RA-05(02) [M] Update Vulnerabilities to Be Scanned
---+RA-05(05) [M] Privileged Access
---+RA-05(11) [M] Public Disclosure Program

RA-05 [M] Vulnerability Monitoring and Scanning

Control

  1. 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;
  2. Employ vulnerability monitoring tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for:
    1. Enumerating platforms, software flaws, and improper configurations;
    2. Formatting checklists and test procedures; and
    3. Measuring vulnerability impact;
  3. Analyze vulnerability scan reports and results from vulnerability monitoring;
  4. Remediate legitimate vulnerabilities [Assignement: response times] in accordance with an organizational assessment of risk;
  5. 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
  6. 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

    1. 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;
    2. 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;
  2. vulnerability monitoring tools and techniques are employed to facilitate interoperability among tools;
    1. 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;
    2. 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;
    3. 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;
  3. vulnerability scan reports and results from vulnerability monitoring are analyzed;
  4. legitimate vulnerabilities are remediated [Assignement: response times] in accordance with an organizational assessment of risk;
  5. 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;
  6. 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. Pārskats

RA-05(02) [M] 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(05) [M] 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(11) [M] 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 Atsauces

1.2 Identificētās prasības

1.3 Saistītie tiesību akti

2. Identificētās prasības

Prasības

3. Saistītie tiesību akti

Tiesību akti

Saistītie uzdevumi

Saites
is blocked by RA-05 [M] Vulnerability Monitoring and Scanning – Assessment Procedure
is blocked by Vulnerability Scanning
is blocked by Update Vulnerability Scanning Tools