SC-08 Transmission Confidentiality and Integrity

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

Protect the [Selection (one or more): confidentiality; integrity] of transmitted information.

Guidance

Protecting the confidentiality and integrity of transmitted information applies to internal and external networks as well as any system components that can transmit information, including servers, notebook computers, desktop computers, mobile devices, printers, copiers, scanners, facsimile machines, and radios. Unprotected communication paths are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of information can be accomplished by physical or logical means. Physical protection can be achieved by using protected distribution systems. A protected distribution system is a wireline or fiber-optics telecommunications system that includes terminals and adequate electromagnetic, acoustical, electrical, and physical controls to permit its use for the unencrypted transmission of classified information. Logical protection can be achieved by employing encryption techniques. Organizations that rely on commercial providers who offer transmission services as commodity services rather than as fully dedicated services may find it difficult to obtain the necessary assurances regarding the implementation of needed controls for transmission confidentiality and integrity. In such situations, organizations determine what types of confidentiality or integrity services are available in standard, commercial telecommunications service packages. If it is not feasible to obtain the necessary controls and assurances of control effectiveness through appropriate contracting vehicles, organizations can implement appropriate compensating controls.

Implementation

Talos node

Node-to-node traffic is carried by KubeSpan (WireGuard); the Talos API and the Kubernetes API are mutual TLS.

Status: partial. Configured as described, but the only evidence is a configuration file; no Lula validation or assessment result proves it on the lab clusters yet. Raise to implemented when one exists.

Evidence:

• https://github.com/zeta-reticuli-inc/talos-multicloud/blob/main/talos/patches/common-kubespan.yaml

Lab artifact cache and boot image distribution

Transmission confidentiality and integrity between lab nodes and the cache: not met; zot and Caddy serve plain HTTP on the lab LAN.

Status: planned.

Evidence:

• https://github.com/zeta-reticuli-inc/agents/blob/main/research/lab-cache.md

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