NET-12: Safeguarding Data Over Open Networks
Cryptographic mechanisms exist to implement strong cryptography and security protocols to safeguard sensitive/regulated data during transmission over open, public networks.
Control Question: Are cryptographic mechanisms utilized to implement strong cryptography and security protocols to safeguard sensitive/regulated data during transmission over open, public networks?
General (28)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC6.6 CC6.6-POF2 |
| GovRAMP Core | AC-02 SI-03 SI-04 SI-07 |
| GovRAMP Low | AC-02 AC-03 SI-03 SI-04 SI-05 |
| GovRAMP Low+ | AC-02 AC-03 AC-05 SI-03 SI-04 SI-05 SI-07 SI-10 |
| GovRAMP Moderate | AC-02 AC-03 AC-05 SI-03 SI-04 SI-05 SI-07 SI-10 |
| GovRAMP High | AC-02 AC-03 AC-05 SI-03 SI-04 SI-05 SI-07 SI-10 |
| NIST 800-53 R5 (source) | AC-2 AC-3 AC-5 SI-3 SI-4 SI-5 SI-7 SI-10 |
| NIST 800-53B R5 (low) (source) | AC-2 AC-3 SI-3 SI-4 SI-5 |
| NIST 800-53B R5 (moderate) (source) | AC-2 AC-3 AC-5 SI-3 SI-4 SI-5 SI-7 SI-10 |
| NIST 800-53B R5 (high) (source) | AC-2 AC-3 AC-5 SI-3 SI-4 SI-5 SI-7 SI-10 |
| NIST 800-82 R3 LOW OT Overlay | AC-2 AC-3 SI-3 SI-4 SI-5 |
| NIST 800-82 R3 MODERATE OT Overlay | AC-2 AC-3 AC-5 SI-3 SI-4 SI-5 SI-7 SI-10 |
| NIST 800-82 R3 HIGH OT Overlay | AC-2 AC-3 AC-5 SI-3 SI-4 SI-5 SI-7 SI-10 |
| NIST 800-161 R1 | AC-2 AC-3 AC-5 SI-3 SI-4 SI-5 SI-7 |
| NIST 800-161 R1 C-SCRM Baseline | AC-2 AC-3 AC-5 SI-3 SI-4 SI-5 SI-7 |
| NIST 800-161 R1 Flow Down | AC-2 AC-3 AC-5 SI-3 SI-4 SI-5 SI-7 |
| NIST 800-161 R1 Level 1 | SI-4 SI-5 SI-7 |
| NIST 800-161 R1 Level 2 | AC-2 AC-3 AC-5 SI-3 SI-4 SI-5 SI-7 |
| NIST 800-161 R1 Level 3 | AC-2 AC-3 AC-5 SI-3 SI-4 SI-5 SI-7 |
| PCI DSS 4.0.1 (source) | 4.1 4.2.1 11.2 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 4.2.1 |
| PCI DSS 4.0.1 SAQ C (source) | 4.2.1 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 4.2.1 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 4.2.1 |
| SCF CORE Mergers, Acquisitions & Divestitures (MA&D) | NET-12 |
| SCF CORE ESP Level 1 Foundational | NET-12 |
| SCF CORE ESP Level 2 Critical Infrastructure | NET-12 |
| SCF CORE ESP Level 3 Advanced Threats | NET-12 |
US (4)
| Framework | Mapping Values |
|---|---|
| US CJIS Security Policy 5.9.3 (source) | AC-2 AC-3 AC-5 SI-3 SI-4 SI-5 SI-7 SI-10 |
| US IRS 1075 | AC-2 AC-3 AC-5 SI-3 SI-4 SI-5 SI-7 SI-10 |
| US SSA EIESR 8.0 | 5.8 |
| US - TX DIR Control Standards 2.0 | AC-2 AC-3 AC-5 SI-3 SI-4 SI-5 |
EMEA (2)
| Framework | Mapping Values |
|---|---|
| EMEA Israel CDMO 1.0 | 8.4 8.6 9.20 13.6 |
| EMEA UK DEFSTAN 05-138 | 2305 |
APAC (1)
| Framework | Mapping Values |
|---|---|
| APAC New Zealand HISF 2022 | HMS17 |
Capability Maturity Model
Level 0 — Not Performed
There is no evidence of a capability to Cryptographic implement strong cryptography and security protocols to safeguard sensitive/regulated data during transmission over open, public networks.
Level 1 — Performed Informally
Network Security (NET) efforts are ad hoc and inconsistent. CMM Level 1 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- IT personnel use an informal process to design, build and maintain secure networks for test, development, staging and production environments, including the implementation of appropriate cybersecurity and data protection controls.
- Administrative processes are used to configure boundary devices (e.g., firewalls, routers, etc.) to deny network traffic by default and allow network traffic by exception (e.g., deny all, permit by exception).
- Network monitoring is primarily reactive in nature.
Level 2 — Planned & Tracked
Network Security (NET) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- Network security management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
- IT/cybersecurity personnel identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for network security management.
- IT personnel define secure networking practices to protect the confidentiality, integrity, availability and safety of the organization's technology assets, data and network(s).
- Administrative processes and technologies focus on protecting High Value Assets (HVAs), including environments where sensitive/regulated data is stored, transmitted and processed.
- Administrative processes are used to configure boundary devices (e.g., firewalls, routers, etc.) to deny network traffic by default and allow network traffic by exception (e.g., deny all, permit by exception).
- Network segmentation exists to implement separate network addresses (e.g., different subnets) to connect systems in different security domains (e.g., sensitive/regulated data environments).
Level 3 — Well Defined
Network Security (NET) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- A Technology Infrastructure team, or similar function, defines centrally-managed network security controls for implementation across the enterprise.
- Secure engineering principles are used to design and implement network security controls (e.g., industry-recognized secure practices) to enforce the concepts of least privilege and least functionality at the network level.
- IT/cybersecurity architects work with the Technology Infrastructure team to implement a “layered defense” network architecture that provides a defense-in-depth approach for redundancy and risk reduction for network-based security controls, including wired and wireless networking.
- Administrative processes and technologies configure boundary devices (e.g., firewalls, routers, etc.) to deny network traffic by default and allow network traffic by exception (e.g., deny all, permit by exception).
- Technologies automate the Access Control Lists (ACLs) and similar rulesets review process to identify security issues and/ or misconfigurations.
- Network segmentation exists to implement separate network addresses (e.g., different subnets) to connect systems in different security domains (e.g., sensitive/regulated data environments).
Level 4 — Quantitatively Controlled
See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to Cryptographic implement strong cryptography and security protocols to safeguard sensitive/regulated data during transmission over open, public networks.
Level 5 — Continuously Improving
See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to Cryptographic implement strong cryptography and security protocols to safeguard sensitive/regulated data during transmission over open, public networks.
Assessment Objectives
- NET-12_A01 approved authorizations for logical access to information and system resources are enforced in accordance with applicable access control policies.