This requirement exists to periodically evaluate the framework against organizational needs, criteria, and best practices and to ensure security architecture decisions are consistent, risk-informed, and traceable.
Establish a documented process for periodically evaluate the framework against organizational needs, criteria, and best practices. 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 |
|---|---|---|---|---|
| IRDAI | IRDAI Information & Cyber Security Guidelines IRDAI information and cyber-security requirements... Clause: §2.5-3.2.5 – Technical review of applications; §1.5-IV – Review Frequency |
India
Guideline
|
vLatest | View → |
| RBI-CSF | RBI Cyber Security Framework / Master Directions RBI cyber-security requirements and directions set... Clause: 4) Network Management and Security – 4.1 Up-to-date organisation-level network architecture diagram; 5) Secure Configuration – 5.1 Baseline security requirements/configurations across device categories and lifecycle, with periodic review |
India
Regulation
|
vLatest | View → |
| SEBI-CSCRF | SEBI Cyber Security & Cyber Resilience Framework SEBI’s Cybersecurity and Cyber Resilience Framewor... Clause: 3.4 PR.IP: Information Protection Processes and Procedures; 1.1 GV.OC: Organizational Context |
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 → |
| ISO27002 | ISO/IEC 27002 ISO/IEC 27002 is a guidance standard containing a... Clause: 8.27 – Secure system architecture and engineering principles |
ISO
Standard
|
v2022 | 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: CC1.3 – Control Environment – COSO Principle 3: Management establishes, with board oversight, structures, reporting lines, and appropriate authorities and responsibilities in the pursuit of objectives. CC5.2 – Control Activities – COSO Principle 11: The entity also selects and develops general control activities over technology to support the achievement of objectives. 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. |
AICPA
Audit Framework
|
vLatest | View → |