SC-07(05) Deny by Default — Allow by Exception

Self-assessed, not audited

We hold no certification or authorization. The status below is our own assessment, kept as OSCAL in Git; it is not an auditor's finding. "Planned" means not built.

Control statement

Deny network communications traffic by default and allow network communications traffic by exception [Selection (one or more): at managed interfaces; for [Assignment: systems]].

Guidance

Denying by default and allowing by exception applies to inbound and outbound network communications traffic. A deny-all, permit-by-exception network communications traffic policy ensures that only those system connections that are essential and approved are allowed. Deny by default, allow by exception also applies to a system that is connected to an external system.

Implementation

Cloudflare Tunnel and WARP access

Deny by default at the tunnel (catch-all 404, no hostnames). Partial: Zero Trust network policies (Gateway rules allowing only named users and devices to each /24) are not defined in code.

Status: partial.

Evidence:

• https://github.com/zeta-reticuli-inc/talos-multicloud/blob/main/modules/cluster-tunnel/main.tf

All controls. Source: OSCAL component definition reti-platform and NIST SP 800-53 Rev 5 (public domain).