This requirement exists to periodically assess Zero Trust controls against established criteria and best practices and to ensure security architecture decisions are consistent, risk-informed, and traceable.
Establish a documented process for periodically assess Zero Trust controls against established 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.3-3.4 – User Authorization |
India
Guideline
|
vLatest | View → |
| RBI-CSF | RBI Cyber Security Framework / Master Directions RBI cyber-security requirements and directions set... Clause: 8) User Access Control / Management – 8.3 No admin rights on end-user devices; need-to-know and time-bound access; 8) User Access Control / Management – 8.4 Centralised authentication/authorization, strong passwords, MFA, least privilege and segregation of duties; 4) Network Management and Security – 4.10 Layered boundary defences, firewalls/proxies/DMZ/IPS/IDS and traffic filtering |
India
Regulation
|
vLatest | View → |
| SEBI-CSCRF | SEBI Cyber Security & Cyber Resilience Framework SEBI’s Cybersecurity and Cyber Resilience Framewor... Clause: 3.1 PR.AA: Identity Management, Authentication, and Access Control |
India
Regulation
|
vLatest | View → |
| DORA | Digital Operational Resilience Act The EU Digital Operational Resilience Act establis... Clause: Article 9(4)(c) – Logical/physical access limitation and access-rights administration Article 9(4)(d) – Strong authentication, cryptographic keys and encryption |
EU
Regulation
|
vCurrent | View → |
| ISO27002 | ISO/IEC 27002 ISO/IEC 27002 is a guidance standard containing a... Clause: 8.3 – Information access restriction; 8.22 – Segregation of networks |
ISO
Standard
|
v2022 | View → |
| NIS2 | NIS2 Directive The NIS2 Directive establishes EU-wide cybersecuri... Clause: Article 21(2)(i) – Human resources security, access control policies and asset management Article 21(2)(j) – MFA/continuous authentication, secured voice/video/text communications and secured emergency communications |
EU
Directive
|
vCurrent | View → |
| PCI-DSS | PCI DSS PCI DSS is an industry security standard maintaine... Clause: 7.2.1 – An access control model is defined and; 7.2.2 – Access is assigned to users, including; 1.4.1 – NSCs are implemented between trusted and |
PCI
Standard
|
v4 | View → |
| COBIT2019 | COBIT COBIT is an enterprise governance and management f... Clause: 4.2 – Align, Plan and Organize (APO) > APO03 – Managed Enterprise Architecture > APO03.02 – Define reference architecture. |
COBIT
Governance Framework
|
v2019 | 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: CC6.1 – Logical and Physical Access Controls – The entity implements logical access security software, infrastructure, and architectures over protected information assets to protect them from security events to meet the entity's objectives. CC6.3 – Logical and Physical Access Controls – The entity authorizes, modifies, or removes access to data, software, functions, and other protected information assets based on roles, responsibilities, or the system design and changes, giving consideration to the concepts of least privilege and segregation of duties, to meet the entity’s objectives. CC6.6 – Logical and Physical Access Controls – The entity implements logical access security measures to protect against threats from sources outside its system boundaries. 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 → |