Skip to main content

VPM-06.3: Privileged Access

VPM 9 — Critical Protect

Mechanisms exist to implement privileged access authorization for selected vulnerability scanning activities.

Control Question: Does the organization implement privileged access authorization for selected vulnerability scanning activities?

General (15)
Framework Mapping Values
CSA CCM 4 IAM-09
GovRAMP Core RA-05(05)
GovRAMP Moderate RA-05(05)
GovRAMP High RA-05(05)
NIST 800-53 R4 RA-5(5)
NIST 800-53 R4 (moderate) RA-5(5)
NIST 800-53 R4 (high) RA-5(5)
NIST 800-53 R5 (source) RA-5(5)
NIST 800-53B R5 (moderate) (source) RA-5(5)
NIST 800-53B R5 (high) (source) RA-5(5)
NIST 800-82 R3 MODERATE OT Overlay RA-5(5)
NIST 800-82 R3 HIGH OT Overlay RA-5(5)
NIST 800-171 R2 (source) 3.11.2
Shared Assessments SIG 2025 T.2
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) VPM-06.3
US (11)
EMEA (1)
Framework Mapping Values
EMEA Israel CDMO 1.0 22.9

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to implement privileged access authorization for selected vulnerability scanning activities.

Level 1 — Performed Informally

Vulnerability & Patch Management (VPM) efforts are ad hoc and inconsistent. CMM Level 1 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • Attack Surface Management (ASM) is decentralized.
  • IT personnel apply software patches through an informal process.
  • Occasional vulnerability scanning is conducted on High Value Assets (HVAs).
Level 2 — Planned & Tracked

Vulnerability & Patch Management (VPM) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Identify cybersecurity and data protection controls to address applicable statutory, regulatory and contractual requirements for ASM. o Apply software patches and other vulnerability remediation efforts.

  • Attack Surface Management (ASM) is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
  • IT/cybersecurity personnel:
  • Administrative processes and technologies focus on protecting High Value Assets (HVAs), including environments where sensitive/regulated data is stored, transmitted and processed.
Level 3 — Well Defined

Vulnerability & Patch Management (VPM) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Defines the scope of ASM activities. o Provides governance oversight for the implementation of applicable statutory, regulatory and contractual cybersecurity and data protection controls to protect the confidentiality, integrity, availability and safety of the organization's applications, systems, services and data with regards to ASM. o Provides oversight of ASM activities to centrally manage the flaw remediation process as part of the organization's overall Patch& Vulnerability & Patch Management Program (VPMP). o Manages the identification, tracking and remediation of vulnerabilities. o Utilizes a Security Incident Event monitor (SIEM), or similar automated tool, to monitor for unauthorized activities, accounts, connections, devices and software according to organization-specific Indicators of Compromise (IoC), including feeds from applications, hosts, network devices and vulnerability scanners.

  • An IT Asset Management (ITAM) function, or similar function, categorizes devices according to the data the asset stores, transmits and/ or processes and applies the appropriate technology controls to protect the asset and data.
  • A Governance, Risk & Compliance (GRC) function, or similar function:
  • A Security Operations Center (SOC), or similar function:
  • Asset custodians install the latest stable version of security-related updates on all systems within the organization-defined time requirements.
Level 4 — Quantitatively Controlled

See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to implement privileged access authorization for selected vulnerability scanning activities.

Level 5 — Continuously Improving

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to implement privileged access authorization for selected vulnerability scanning activities.

Assessment Objectives

  1. VPM-06.3_A01 system components to which privileged access is authorized for selected vulnerability scanning activities are defined.
  2. VPM-06.3_A02 vulnerability scanning activities selected for privileged access authorization to system components are defined.
  3. VPM-06.3_A03 privileged access authorization is implemented to system components for vulnerability scanning activities.

Technology Recommendations

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.