NET-14: Zero Trust Architecture (ZTA)
Mechanisms exist to treat all users and devices as potential threats and prevent access to data and resources until the users can be properly authenticated and their access authorized.
Renumbered: Formerly NET-01.1 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, NET-14 was Remote Access. That control is now NET-26.
Control Question: Does the organization treat all users and devices as potential threats and prevent access to data and resources until the users can be properly authenticated and their access authorized?
General (9)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC6.1-POF5 |
| CIS CSC 8.1 | 13.5 |
| CIS CSC 8.1 IG2 | 13.5 |
| CIS CSC 8.1 IG3 | 13.5 |
| CR CMM 2026 | CR4.1.5 |
| CSA IoT SCF 2 | SNT-02 |
| IEC 62443-4-2 2019 | NDR 1.13 |
| MPA Content Security Program 5.3.1 | TS-6.0 TS-6.1 TS-6.2 |
| NIST 800-207 | NIST Tenet 3 NIST Tenet 5 NIST Tenet 6 |
US (2)
| Framework | Mapping Values |
|---|---|
| USA Federal DoD Zero Trust Reference Architecture 2.0 | 3.0 |
| USA Federal DoD Zero Trust Execution Roadmap v1.1 | 5.1.1 6.2.3 |
APAC (6)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-0665 |
| APAC India SEBI CSCRF 2024 | PR.AA.S4 |
| APAC Japan ISMAP | 9.1.1.16 |
| APAC Malaysia RMiT 2025 | 11.3(d) A10-B1(b) |
| APAC New Zealand NZISM 3.9 | 2.3.26.C.01 2.3.26.C.02 16.1.25.C.01 16.5.12.C.02 |
| APAC Singapore CCOP CII 2026 | 3.7.2(b) A.2.4(b) |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
Network Security (NET) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with NET domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Network security-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Administrative processes are used to configure boundary devices (e.g., firewalls and routers) to deny network traffic by default and allow network traffic by exception (e.g., deny all and permit by exception).
Level 2 — Planned & Tracked
SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).
Level 3 — Well Defined
Network Security (NET) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with NET domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with NET domain capabilities are well-documented and kept current by process owners. ▪ A network security management team, or similar function, is appropriately staffed and supported to implement and maintain NET domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of network security operations (e.g., network management solution and log aggregator). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with NET domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ Secure Baseline Configurations (SBC) enforce the principles of least privileges and least functionality for boundary protection technologies. ▪ An implemented and operational capability exists to treat all users and devices as potential threats and prevent access to data and resources until the users can be properly authenticated and their access authorized.
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- NET-14_A01 all users are treated as potential threats, and access to data and resources is prevented until the user is authenticated and their access is authorized.
- NET-14_A02 all devices are treated as potential threats, and access to data and resources is prevented until the device is authenticated and its access is authorized.
Evidence Requirements
- E-NET-05 Zero Trust Architecture (ZTA)
-
Documented evidence of controls that would enable the organization to claim conformity with Zero Trust (ZT) principles.
Network Security - E-QTS-09 Zero Trust Network Architecture (ZTNA)
-
Documented evidence of Zero Trust Network Architecture (ZTNA) (e.g., architecture diagrams, segmentation matrices, access policies, etc.).
Quantum Security
Technology Recommendations
Micro/Small
- Zero trust basics: MFA everywhere, device compliance checks, least privilege (e.g., Microsoft Entra Conditional Access)
Small
- Zero trust roadmap; identity-centric access with MFA and device compliance (e.g., Entra Conditional Access, Cloudflare Access)
Medium
- Zero Trust Architecture (ZTA) planning and roadmap
Large
- ZTA implementation
- Identity-centric access controls
- Microsegmentation
Enterprise
- Enterprise ZTA platform (e.g., Zscaler, Palo Alto Prisma Access)
- Identity-based access
- Microsegmentation
- Continuous validation