Active

Analytics Continuous Improvement

The organization shall establish a continuous improvement process for exposure analytics, driving ongoing enhancement of analytics effectiveness and value. The process shall include mechanisms for identifying improvement opportunities, implementing changes, and measuring results, drawing inputs from analytics reviews, stakeholder feedback, and best practice benchmarking.

Requirement ID
VUL-008-R010
Parent Control
Domain Code

Requirement Details & Guidance

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

Some vulnerabilities cannot be remediated immediately, but unmanaged exceptions create persistent exposure.

Implementation Guidance

Require documented business justification, risk assessment, owner, expiry date, compensating controls, and periodic review for deferred remediation.

Practical Application & Audit Readiness

VUL-008-R010 · Field Guidance

Business Examples

    Common Audit Findings

      Common Mistakes

        Best Practices & Ownership

        VUL-008 · Recommended Approach

        Recommended Practices

          Typical Owner

          Cross-Mapped Regulatory Frameworks

          Harmonized Control Mappings
          FRAMEWORK CODE FRAMEWORK NAME & DETAILS FAMILY / CATEGORY VERSION ACTION
          ISO27001 ISO/IEC 27001 ISO/IEC 27001 specifies auditable requirements for... Clause: 10.1 – Continual improvement
          ISO
          Standard
          v2022 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; 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: 4.1 DE.CM: Security Continuous Monitoring; 2.2 ID.RA: Risk Assessment
          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 Article 8(3) – ICT risk assessment following major changes
          EU
          Regulation
          vCurrent 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.5 – Monitor, Evaluate and Assess (MEA) > MEA02 – Managed System of Internal Control > MEA02.01 – Monitor internal controls.
          COBIT
          Governance Framework
          v2019 View →
          NIST-CSF NIST Cybersecurity Framework (CSF) The NIST Cybersecurity Framework provides high-lev... Clause: ID.IM – Improvement | ID.IM-03 – Improvements are identified from execution of operational processes, procedures, and activities ID.IM – Improvement | ID.IM-01 – Improvements are identified from evaluations
          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, RA-3 – RISK ASSESSMENT
          NIST
          Control Catalog
          vRev. 5 View →
          NPCI-ISR NPCI Information Security Requirements NPCI information-security requirements define cont... Clause: Operational Review; VAPT Testing and Re-assessment
          India
          Standard
          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. 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.
          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

          Parent Control Context

          Control Baseline
          Control Name:
          Exposure Analytics (VUL-008)
          Summary:
          Establishes exposure analytics including data collection, trend analysis, attack surface analysis, exposure scoring, executive dashboards, reporting, and predictive analysis for vulnerability intelligence.
          Business Description:
          Establish and maintain capabilities to analyze vulnerability data, attack exposure, remediation trends, and organizational risk posture.