Active

Exception Closure

The organization shall close vulnerability exceptions when vulnerabilities are remediated, conditions have changed, or the exception period has expired. Closure shall include verification that vulnerabilities have been remediated, documentation of closure decisions, and removal from active status, with closure properly authorized and documented.

Requirement ID
VUL-007-R010
Parent Control
VUL-007
Domain Code
VUL

Requirement Details & Guidance

VUL-007-R010 · VUL-007
Why This Requirement Exists

Vulnerability risk changes with active exploitation, threat campaigns, internet exposure, and attack-path context.

Implementation Guidance

Integrate vulnerability data with threat intelligence, asset exposure, exploit information, and attack-surface context to identify urgent risks.

Practical Application & Audit Readiness

VUL-007-R010 · Field Guidance

Business Examples

    Common Audit Findings

      Common Mistakes

        Best Practices & Ownership

        VUL-007 · Recommended Approach

        Recommended Practices

          Typical Owner

          Cross-Mapped Regulatory Frameworks

          Harmonized Control Mappings
          FRAMEWORK CODE FRAMEWORK NAME & DETAILS FAMILY / CATEGORY VERSION ACTION
          IRDAI IRDAI Information & Cyber Security Guidelines IRDAI information and cyber-security requirements... Clause: §2.6-3.6 – Vulnerability Management
          India
          Guideline
          		 vLatest View →
          RBI-CSF RBI Cyber Security Framework / Master Directions RBI cyber-security requirements and directions set... Clause: 2) Preventing execution of unauthorised software – 2.4 Defined exception framework, approval and periodic review; 18) Vulnerability assessment and Penetration Test and Red Team Exercises – 18.2 Prompt remediation of vulnerabilities under risk-treatment framework
          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 →
          DORA Digital Operational Resilience Act The EU Digital Operational Resilience Act establis... Clause: Article 8(2) – Continuous identification of ICT risk sources, cyber threats and ICT vulnerabilities
          EU
          Regulation
          		 vCurrent 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 →
          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 →
          NIST-CSF NIST Cybersecurity Framework (CSF) The NIST Cybersecurity Framework provides high-lev... Clause: ID.RA – Risk Assessment | ID.RA-07 – Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
          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; RA-7 – RISK RESPONSE, CA-6 – AUTHORIZATION
          NIST
          Control Catalog
          		 vRev. 5 View →
          CIS-V8 CIS Controls CIS Controls are a prioritized set of cybersecurit... Clause: Control 07 – Continuous Vulnerability Management: 7.2 – Establish and Maintain a Remediation Process
          CIS
          Best Practice
          		 vv8 View →
          NPCI-ISR NPCI Information Security Requirements NPCI information-security requirements define cont... Clause: Operational Review; Testing – Re-assessment and Closure
          India
          Standard
          		 vLatest View →
          SOC2 SOC 2 Trust Services Criteria SOC 2 is an independent examination and reporting... Clause: 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. CC5.3 – Control Activities – COSO Principle 12: The entity deploys control activities through policies that establish what is expected and in procedures that put policies into action.
          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 Exception Management (VUL-007)
          Summary:
          Establishes vulnerability exception management including request, risk assessment, approval, compensating controls, monitoring, renewal, reporting, review, and closure for vulnerabilities.
          Business Description:
          Establish and maintain processes to evaluate, approve, document, monitor, and periodically review vulnerability remediation exceptions.
          View