VUL-004 (VUL-004-R007) - VUL-004

Requirement Details & Guidance

VUL-004-R007 · VUL-004

Why This Requirement Exists

The organization shall monitor patch compliance to ensure systems are patched in accordance with policies and schedules. Monitoring shall include assessment of patch status, identification of unpatched systems, and tracking of compliance gaps.

Implementation Guidance

Severity alone does not represent business risk; exploitability, asset criticality, exposure, and business impact affect remediation priority.

Practical Application & Audit Readiness

VUL-004-R007 · Field Guidance

Business Examples

Common Audit Findings

Common Mistakes

Best Practices & Ownership

VUL-004 · 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.3 – Perform Automated Operating System Patch Management	CIS Best Practice	vv8	View →
DORA	Digital Operational Resilience Act The EU Digital Operational Resilience Act establis... Clause: Article 9(4)(e) – ICT change management: recording, testing, assessing, approving, implementing and verifying changes Article 9(4)(f) – Documented policies for patches and updates	EU Regulation	vCurrent	View →
GDPR	General Data Protection Regulation (GDPR) The General Data Protection Regulation is a bindin... Clause: Article 32(1)(d) – Testing, assessing and evaluating security measures; Article 32(1) – Security of processing	EU Regulation	vCurrent	View →
HIPAA	Health Insurance Portability and Accountability Act HIPAA is a U.S. federal law supported by implement... Clause: § 164.308(a)(4) Standard: Patch management	US Law	vCurrent	View →
IRDAI	IRDAI Information & Cyber Security Guidelines IRDAI information and cyber-security requirements... Clause: §2.6-3.2 – Patch 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 →
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: DE.CM – Continuous Monitoring \| DE.CM-09 – Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events	NIST Framework	v2	View →
NIST80053	NIST SP 800-53 NIST SP 800-53 Rev. 5 presents control families, i... Clause: 3.19 – SYSTEM AND INFORMATION INTEGRITY; SI-2 – FLAW REMEDIATION	NIST Control Catalog	vRev. 5	View →
NPCI-ISR	NPCI Information Security Requirements NPCI information-security requirements define cont... Clause: Security Measures / Controls; Application Security – Hardening and Patching	India Standard	vLatest	View →
PCI-DSS	PCI DSS PCI DSS is an industry security standard maintaine... Clause: 6.3.3 – All system components are protected from	PCI Standard	v4	View →
RBI-CSF	RBI Cyber Security Framework / Master Directions RBI cyber-security requirements and directions set... Clause: 7) Patch/Vulnerability & Change Management – 7.1 Risk-based patch inventory, identification and application to minimise exposure; 7) Patch/Vulnerability & Change Management – 7.2 Identify, track, manage and monitor patch status; 2) Preventing execution of unauthorised software – 2.3 Patch monitoring and expedited/emergency patching	India Regulation	vLatest	View →
SEBI-CSCRF	SEBI Cyber Security & Cyber Resilience Framework SEBI’s Cybersecurity and Cyber Resilience Framewor... Clause: 4.1 DE.CM: Security Continuous Monitoring; 2.2 ID.RA: Risk Assessment	India Regulation	vLatest	View →
SOC2	SOC 2 Trust Services Criteria SOC 2 is an independent examination and reporting... Clause: CC8.1 – Change Management – The entity authorizes, designs, develops or acquires, configures, documents, tests, approves, and implements changes to infrastructure, data, software, and procedures to meet its objectives. 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. CC7.2 – System Operations – The entity monitors system components and the operation of those components for anomalies that are indicative of malicious acts, natural disasters, and errors affecting the entity's ability to meet its objectives; anomalies are analyzed to determine whether they represent security events.	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 Intelligence (VUL-004)

Summary:

Establishes vulnerability intelligence including source management, collection, analysis, validation, dissemination, integration, and continuous improvement for vulnerability information.

Business Description:

Establish and maintain processes to incorporate threat intelligence, exploit intelligence, vendor advisories, and emerging vulnerability information into vulnerability management activities.

View