This requirement exists to ensure required reviews occur and identified findings are remediated and to ensure security architecture decisions are consistent, risk-informed, and traceable.
Establish a documented process for ensure required reviews occur and identified findings are remediated. Define accountable roles, required inputs and outputs, approval or validation points, criteria, review frequency, exception handling, monitoring, and evidence requirements. Integrate the activity with architecture governance, risk management, security requirements, engineering, and change processes as applicable. Retain records sufficient to demonstrate that the control operates.
| FRAMEWORK CODE | FRAMEWORK NAME & DETAILS | FAMILY / CATEGORY | VERSION | ACTION |
|---|---|---|---|---|
| ISO27001 | ISO/IEC 27001 ISO/IEC 27001 specifies auditable requirements for... Clause: 9.1 – Monitoring, measurement, analysis and evaluation |
ISO
Standard
|
v2022 | View → |
| IRDAI | IRDAI Information & Cyber Security Guidelines IRDAI information and cyber-security requirements... Clause: §2.16-3.6 – Information Security assessment |
India
Guideline
|
vLatest | View → |
| RBI-CSF | RBI Cyber Security Framework / Master Directions RBI cyber-security requirements and directions set... Clause: 5) Secure Configuration – 5.1 Baseline security requirements/configurations across device categories and lifecycle, with periodic review; 6) Application Security Life Cycle (ASLC) – 6.1 Information security across all application lifecycle stages |
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 |
India
Regulation
|
vLatest | View → |
| DORA | Digital Operational Resilience Act The EU Digital Operational Resilience Act establis... Clause: Article 6(8)(d) – ICT reference architecture and changes needed for business objectives Article 7 – ICT systems, protocols and tools |
EU
Regulation
|
vCurrent | View → |
| NIS2 | NIS2 Directive The NIS2 Directive establishes EU-wide cybersecuri... Clause: Article 21(2)(f) – Policies and procedures to assess the effectiveness of cybersecurity risk-management measures |
EU
Directive
|
vCurrent | View → |
| PCI-DSS | PCI DSS PCI DSS is an industry security standard maintaine... Clause: 2.2.1 – Configuration standards are developed,; 6.5.2 – Upon completion of a significant change, all |
PCI
Standard
|
v4 | View → |
| NIST-CSF | NIST Cybersecurity Framework (CSF) The NIST Cybersecurity Framework provides high-lev... Clause: PR.IR – Technology Infrastructure Resilience | PR.IR-01 – Networks and environments are protected from unauthorized logical access and usage |
NIST
Framework
|
v2 | View → |
| NIST80053 | NIST SP 800-53 NIST SP 800-53 Rev. 5 presents control families, i... Clause: 3.17 – SYSTEM AND SERVICES ACQUISITION, 3.4 – ASSESSMENT, AUTHORIZATION, AND MONITORING; SA-17 – DEVELOPER SECURITY AND PRIVACY ARCHITECTURE AND DESIGN, CA-2 – CONTROL ASSESSMENTS |
NIST
Control Catalog
|
vRev. 5 | 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.1 – Control Activities – COSO Principle 10: The entity selects and develops control activities that contribute to the mitigation of risks to the achievement of objectives to acceptable levels. 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 → |