Assessment Objectives
In addition to relevant policies, standards and procedures, the assessor shall examine, interview, and/or test to determine if appropriately scoped evidence exists to support the claim that:
- VPM-12_A01 the frequency at which the system is scanned for vulnerabilities is defined.
Defined parameters: at least monthly
Assessment rigor: 1
Origin: 53A_R5_RA-05_ODP[01] 53A_R5_RA-05_ODP[02] 171A_3.11.2[a] 171A_R3_A.03.11.02.ODP[02] - VPM-12_A02 response times to remediate legitimate vulnerabilities in accordance with an organizational assessment of risk are defined.
Defined parameters: high-risk vulnerabilities mitigated within thirty (30) days from date of discovery; moderate-risk vulnerabilities mitigated within ninety (90) days from date of discovery; low risk vulnerabilities mitigated within one hundred and eighty (180) days from date of discovery
Assessment rigor: 1
Origin: 53A_R5_RA-05_ODP[03] - VPM-12_A03 personnel or roles with whom information obtained from the vulnerability scanning process and control assessments are to be shared.
Assessment rigor: 1
Origin: 53A_R5_RA-05_ODP[04] - VPM-12_A04 vulnerability scan reports and results from vulnerability monitoring are analyzed.
Assessment rigor: 1
Origin: 53A_R5_RA-05c. - VPM-12_A05 systems and hosted applications are scanned for vulnerabilities frequently and/or randomly in accordance with organization-defined process and when new vulnerabilities potentially affecting the system are identified and reported.
Defined parameters: monthly operating system/infrastructure; monthly web applications (including APIs) and databases
Assessment rigor: 1
Origin: 53A_R5_RA-05a.[01] 53A_R5_RA-05a.[02] - VPM-12_A06 vulnerability monitoring tools and techniques are employed to facilitate interoperability among tools.
Assessment rigor: 2
Origin: 53A_R5_RA-05b. - VPM-12_A07 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.
Assessment rigor: 2
Origin: 53A_R5_RA-05b.01 - VPM-12_A08 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.
Assessment rigor: 2
Origin: 53A_R5_RA-05b.02 - VPM-12_A09 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.
Assessment rigor: 2
Origin: 53A_R5_RA-05b.03 - VPM-12_A10 the system is scanned for vulnerabilities per an organization-defined frequency.
Defined parameters: at least monthly
Assessment rigor: 2
Origin: 171A_3.11.2[b] - VPM-12_A11 vulnerability scans are performed on applications with the defined frequency.
Defined parameters: at least monthly
Assessment rigor: 2
Origin: 171A_3.11.2[c] - VPM-12_A12 the system is monitored for vulnerabilities when new vulnerabilities that affect the system are identified.
Assessment rigor: 2
Origin: 171A_3.11.2[d] 171A_R3_A.03.11.02.a[03] - VPM-12_A13 the system is scanned for vulnerabilities when new vulnerabilities that affect the system are identified.
Assessment rigor: 2
Origin: 171A_3.11.2[e] 171A_R3_A.03.11.02.a[04] - VPM-12_A14 legitimate vulnerabilities are remediated response times in accordance with an organizational assessment of risk.
Defined parameters: high-risk vulnerabilities mitigated within thirty (30) days from date of discovery; moderate-risk vulnerabilities mitigated within ninety (90) days from date of discovery; low risk vulnerabilities mitigated within one hundred and eighty (180) days from date of discovery
Assessment rigor: 3
Origin: 53A_R5_RA-05d. - VPM-12_A15 information obtained from the vulnerability monitoring process and control assessments is shared with personnel or roles to help eliminate similar vulnerabilities in other systems.
Assessment rigor: 3
Origin: 53A_R5_RA-05e. - VPM-12_A16 vulnerability monitoring tools that include the capability to readily update the vulnerabilities to be scanned are employed.
Assessment rigor: 3
Origin: 53A_R5_RA-05f. - VPM-12_A17 the frequency at which to update system vulnerabilities to be scanned is defined.
Defined parameters: at least monthly
Assessment rigor: 2
Origin: 171A_R3_A.03.11.02.ODP[04] - VPM-12_A18 the system is monitored for vulnerabilities per an organization-defined frequency.
Defined parameters: at least monthly
Assessment rigor: 3
Origin: SCF Created - VPM-12_A19 system vulnerabilities to be scanned are updated per an organization-defined frequency.
Defined parameters: at least monthly
Assessment rigor: 3
Origin: SCF Created - VPM-12_A20 system vulnerabilities to be scanned are updated when new vulnerabilities are identified and reported.
Assessment rigor: 3
Origin: SCF Created - VPM-12_A21 the frequency at which the system is monitored for vulnerabilities is defined.
Defined parameters: at least monthly
Assessment rigor: 2
Origin: 171A_R3_A.03.11.02.ODP[01] - VPM-12_A22 the system is monitored for vulnerabilities <A.03.11.02.ODP[01]: frequency>.
Defined parameters: at least monthly, or when there are significant incidents or significant changes to risks
Assessment rigor: NIST 800-171
Origin: 171A_R3_A.03.11.02.a[01] - VPM-12_A23 the system is scanned for vulnerabilities <A.03.11.02.ODP[02]: frequency>.
Defined parameters: at least monthly, or when there are significant incidents or significant changes to risks
Assessment rigor: NIST 800-171
Origin: 171A_R3_A.03.11.02.a[02] - VPM-12_A24 system vulnerabilities to be scanned are updated <A.03.11.02.ODP[04]: frequency>.
Defined parameters: no more than 24 hours prior to running the scans
Assessment rigor: NIST 800-171
Origin: 171A_R3_A.03.11.02.c[01]
Linkitetyt tehtävät
| Linkin tyyppi | Tehtävä |
|---|---|
| blocks | Vulnerability Scanning |
- Secure Controls Framework -
The Secure Controls Framework® (SCF)
"The SCF is the Common Controls Framework™ (CCF), the world's most comprehensive cybersecurity and data privacy metaframework - it is also free to use. The entire concept is building secure, compliant and resilient capabilities in the most efficient and cost-effective manner possible.
The SCF is more than just a unified control catalog, since its included content creates a playbook for Governance, Risk & Compliance (GRC) capabilities. Used globally by organizations of every size, the SCF is a robust and scalable solution for security, compliance and resilience controls. As a comprehensive security framework, the SCF maps 1,400+ controls across 200+ laws, regulations, and industry frameworks so you can implement once and comply everywhere.
Like it or not, cybersecurity is a protracted war on an asymmetric battlefield, where the threats are everywhere and as defenders we have to make the effort to work together to help improve cybersecurity and data privacy practices, since we all suffer when massive data breaches occur or when cyber attacks have physical impacts. Hackers share information on attack methods with other hackers, so why shouldn’t the good guys share information on how to best protect an organization? We decided to take action and make a difference, since we feel it is too important to wait for someone else to fix the problems that exist.
The SCF is made up of volunteers, mainly specialists within the cybersecurity profession, who focus on GRC and the cybersecurity side of data privacy. These are auditors, engineers, architects, incident responders, consultants and other specialists who live and breathe these topics on a daily basis. The end product is "expert-derived content" that makes up the SCF." https://securecontrolsframework.com/Terms & Conditions
The SCF End User License Agreement (EULA) governs the use of the Secure Controls Framework® (SCF) under the Creative Commons Attribution-No Derivatives 4.0 International Public License.