Requirement Details & Guidance
VUL-005-R006 · VUL-005Why This Requirement Exists
The organization shall define and report on vulnerability metrics that provide meaningful insight into vulnerability management effectiveness and risk exposure. Metrics shall include vulnerability closure rates, time to remediate, patch compliance, and risk reduction.
Implementation Guidance
Timely remediation reduces the window in which known vulnerabilities can be exploited.
Practical Application & Audit Readiness
VUL-005-R006 · Field GuidanceBusiness Examples
Use risk-based SLAs, tested deployment procedures, post-remediation validation, and escalation for overdue issues.
Common Audit Findings
Assign findings to accountable owners, define remediation SLAs, deploy patches or fixes through controlled processes, and verify closure after remediation.
Common Mistakes
Missed SLAs; tickets without owners; remediation claimed without validation; repeated overdue findings.
Best Practices & Ownership
VUL-005 · Recommended ApproachRecommended Practices
Patching without testing, closing tickets after deployment without rescanning, or leaving ownership ambiguous.
Typical Owner
High-risk operating system vulnerabilities are patched through a controlled change process and verified by a follow-up scan.
Cross-Mapped Regulatory Frameworks
Harmonized Control Mappings| FRAMEWORK CODE | FRAMEWORK NAME & DETAILS | FAMILY / CATEGORY | VERSION | ACTION |
|---|---|---|---|---|
| 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 |
COBIT
Governance Framework
|
v2019 | View → |
| DORA | Digital Operational Resilience Act The EU Digital Operational Resilience Act establis... Clause: Article 10(1) – Mechanisms to promptly detect anomalous activities and ICT-related incidents Article 13(4) – Monitoring digital resilience strategy, incident patterns and ICT risk exposure |
EU
Regulation
|
vCurrent | View → |
| GDPR | General Data Protection Regulation (GDPR) The General Data Protection Regulation is a bindin... Clause: Article 32(1) – Security of processing; Article 32(1)(d) – Testing, assessing and evaluating security measures |
EU
Regulation
|
vCurrent | View → |
| HIPAA | Health Insurance Portability and Accountability Act HIPAA is a U.S. federal law supported by implement... Clause: § 164.312(h) Standard: Vulnerability management; § 164.316(a)(2) Actions, activities and assessments documentation |
US
Law
|
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 → |
| ISO27001 | ISO/IEC 27001 ISO/IEC 27001 specifies auditable requirements for... Clause: 9.1 – Monitoring, measurement, analysis and evaluation |
ISO
Standard
|
v2022 | 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, 3.4 – ASSESSMENT, AUTHORIZATION, AND MONITORING, 3.13 – PROGRAM MANAGEMENT; RA-5 – VULNERABILITY MONITORING AND SCANNING, CA-7 – CONTINUOUS MONITORING, PM-6 – MEASURES OF PERFORMANCE |
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 → |
| PCI-DSS | PCI DSS PCI DSS is an industry security standard maintaine... Clause: 6.3.1 – Security vulnerabilities are identified and; 11.3.1 – Internal vulnerability scans are performed as; 11.3.2 – External vulnerability scans are performed as |
PCI
Standard
|
v4 | 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.4 Management monitoring of VA/PT findings and follow-up actions; 21) Metrics – 21.1 Comprehensive prospective and retrospective metrics including KPIs/KRIs; 21) Metrics – 21.2 Metrics such as anti-malware coverage, patch latency, awareness training and vulnerability measures |
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; 1.4 GV.OV: Oversight |
India
Regulation
|
vLatest | View → |
| SOC2 | SOC 2 Trust Services Criteria SOC 2 is an independent examination and reporting... Clause: CC2.2 – Information and Communication – COSO Principle 14: The entity internally communicates information, including objectives and responsibilities for internal control, necessary to support the functioning of internal control. CC4.2 – Monitoring of Controls – COSO Principle 17: The entity evaluates and communicates internal control deficiencies in a timely manner to those parties responsible for taking corrective action, including senior management and the board of directors, as appropriate. 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. |
AICPA
Audit Framework
|
vLatest | View → |
Parent Domain Context
Governance Domain BaselineDomain Name:
Vulnerability & Patch Management (VUL)
Purpose:
To identify, prioritize, and remediate vulnerabilities and patch known security flaws.
Scope:
Enterprise
Parent Control Context
Control BaselineControl Name:
Patch Management (VUL-005)
Summary:
Establishes patch management including identification, assessment, prioritization, testing, deployment, compliance monitoring, reporting, and continuous improvement for security patches.
Business Description:
Establish and maintain processes to evaluate, test, approve, deploy, verify, and monitor security patches and software updates across organizational technology assets.