NET-06.5: Direct Internet Access Restrictions
Mechanisms exist to prohibit, or strictly-control, Internet access from sensitive/regulated data enclaves (secure zones).
Control Question: Does the organization prohibit, or strictly-control, Internet access from sensitive/regulated data enclaves (secure zones)?
General (6)
| Framework | Mapping Values |
|---|---|
| MPA Content Security Program 5.1 | TS-2.4 TS-2.8 |
| NIST 800-53 R5 (source) | SC-7(28) |
| NIST 800-53 R5 (NOC) (source) | SC-7(28) |
| NIST 800-82 R3 LOW OT Overlay | SC-7(28) |
| NIST 800-82 R3 MODERATE OT Overlay | SC-7(28) |
| NIST 800-82 R3 HIGH OT Overlay | SC-7(28) |
US (1)
| Framework | Mapping Values |
|---|---|
| US CISA CPG 2022 | 2.X |
EMEA (3)
| Framework | Mapping Values |
|---|---|
| EMEA Saudi Arabia CSCC-1 2019 | 2-4-1-3 2-4-1-6 |
| EMEA Saudi Arabia OTCC-1 2022 | 2-3-1-13 2-4-1-7 |
| EMEA Saudi Arabia SACS-002 | TPC-41 |
Capability Maturity Model
Level 0 — Not Performed
There is no evidence of a capability to prohibit, or strictly-control, Internet access from sensitive/regulated data enclaves (secure zones).
Level 1 — Performed Informally
C|P-CMM1 is N/A, since a structured process is required to prohibit, or strictly-control, Internet access from sensitive/regulated data enclaves (secure zones).
Level 2 — Planned & Tracked
C|P-CMM2 is N/A, since a well-defined process is required to prohibit, or strictly-control, Internet access from sensitive/regulated data enclaves (secure zones).
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 prohibit, or strictly-control, Internet access from sensitive/regulated data enclaves (secure zones).
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 prohibit, or strictly-control, Internet access from sensitive/regulated data enclaves (secure zones).
Assessment Objectives
- NET-06.5_A01 Internet access from sensitive / regulated data enclaves (secure zones) is prohibited or strictly-controlled.
Technology Recommendations
Micro/Small
- Secure Baseline Configurations (SBC)
- Access Control Lists (ACLs)
Small
- Secure Baseline Configurations (SBC)
- Access Control Lists (ACLs)
Medium
- Secure Baseline Configurations (SBC)
- Access Control Lists (ACLs)
Large
- Secure Baseline Configurations (SBC)
- Access Control Lists (ACLs)
Enterprise
- Secure Baseline Configurations (SBC)
- Access Control Lists (ACLs)