Assessment Review (VUL-002-R009) - VUL-002

Requirement Details & Guidance

VUL-002-R009 · VUL-002

Why This Requirement Exists

Regular identification is necessary because vulnerabilities emerge continuously and assets change over time.

Implementation Guidance

Use authenticated and unauthenticated scanning as appropriate, covering servers, endpoints, network devices, applications, cloud assets, and other in-scope technology.

Practical Application & Audit Readiness

VUL-002-R009 · Field Guidance

Business Examples

Common Audit Findings

Common Mistakes

Best Practices & Ownership

VUL-002 · Recommended Approach

Recommended Practices

Typical Owner

Cross-Mapped Regulatory Frameworks

Harmonized Control Mappings

FRAMEWORK CODE	FRAMEWORK NAME & DETAILS	FAMILY / CATEGORY	VERSION	ACTION
CIS-V8	CIS Controls CIS Controls are a prioritized set of cybersecurit... Clause: Control 07 – Continuous Vulnerability Management: 7.5 – Perform Automated Vulnerability Scans of Internal Enterprise Assets; 7.6 – Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets	CIS Best Practice	vv8	View →
COBIT2019	COBIT COBIT is an enterprise governance and management f... Clause: 4.4 – Deliver, Service and Support (DSS) > DSS05 – Managed Security Services > DSS05.07 – Manage vulnerabilities and monitor the infrastructure for 4.5 – Monitor, Evaluate and Assess (MEA) > MEA02 – Managed System of Internal Control > MEA02.03 – Perform control self-assessments.	COBIT Governance Framework	v2019	View →
DORA	Digital Operational Resilience Act The EU Digital Operational Resilience Act establis... Clause: Article 24(2) – Appropriate digital operational resilience tests Article 25 – Testing of ICT tools and systems	EU Regulation	vCurrent	View →
IRDAI	IRDAI Information & Cyber Security Guidelines IRDAI information and cyber-security requirements... Clause: §2.6-3.6 – Vulnerability Management	India Guideline	vLatest	View →
ISO22301	ISO/IEC 22301 ISO 22301 specifies requirements for a Business Co... Clause: 6.1.1 – Determining risks and opportunities; 8.2.3 – Risk assessment	ISO Standard	v2019	View →
ISO27002	ISO/IEC 27002 ISO/IEC 27002 is a guidance standard containing a... Clause: 8.8 – Management of technical vulnerabilities	ISO Standard	v2022	View →
NIS2	NIS2 Directive The NIS2 Directive establishes EU-wide cybersecuri... Clause: Article 21(2)(e) – Security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure	EU Directive	vCurrent	View →
NIST-CSF	NIST Cybersecurity Framework (CSF) The NIST Cybersecurity Framework provides high-lev... Clause: ID.RA – Risk Assessment \| ID.RA-01 – Vulnerabilities in assets are identified, validated, and recorded	NIST Framework	v2	View →
NIST80053	NIST SP 800-53 NIST SP 800-53 Rev. 5 presents control families, i... Clause: 3.16 – RISK ASSESSMENT; RA-5 – VULNERABILITY MONITORING AND SCANNING	NIST Control Catalog	vRev. 5	View →
NPCI-ISR	NPCI Information Security Requirements NPCI information-security requirements define cont... Clause: Operational Review; Testing – VAPT	India Standard	vLatest	View →
RBI-CSF	RBI Cyber Security Framework / Master Directions RBI cyber-security requirements and directions set... Clause: 18) Vulnerability assessment and Penetration Test and Red Team Exercises – 18.1 Periodic VA/PT of critical systems, especially internet-facing	India Regulation	vLatest	View →
SEBI-CSCRF	SEBI Cyber Security & Cyber Resilience Framework SEBI’s Cybersecurity and Cyber Resilience Framewor... Clause: 2.2 ID.RA: Risk Assessment; 3.4 PR.IP: Information Protection Processes and Procedures	India Regulation	vLatest	View →
SOC2	SOC 2 Trust Services Criteria SOC 2 is an independent examination and reporting... Clause: CC7.1 – System Operations – To meet its objectives, the entity uses detection and monitoring procedures to identify (1) changes to configurations that result in the introduction of new vulnerabilities, and (2) susceptibilities to newly discovered vulnerabilities. CC3.2 – Risk Assessment – COSO Principle 7: The entity identifies risks to the achievement of its objectives across the entity and analyzes risks as a basis for determining how the risks should be managed. CC4.1 – Monitoring of Controls – COSO Principle 16: The entity selects, develops, and performs ongoing and/or separate evaluations to ascertain whether the components of internal control are present and functioning.	AICPA Audit Framework	vLatest	View →

Parent Domain Context

Governance Domain Baseline

Domain Name:

Vulnerability & Patch Management (VUL)

Purpose:

To identify, prioritize, and remediate vulnerabilities and patch known security flaws.

Scope:

Enterprise

View

Parent Control Context

Control Baseline

Control Name:

Vulnerability Assessment & Scanning (VUL-002)

Summary:

Establishes vulnerability assessment including scan planning, execution, vulnerability identification, risk prioritization, validation, monitoring, reporting, and continuous improvement.

Business Description:

Establish and maintain processes to identify vulnerabilities through authenticated and unauthenticated assessments across infrastructure, applications, cloud resources, endpoints, containers, APIs, and other technology assets.

View