CM-02 Baseline Configuration

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

• a. Develop, document, and maintain under configuration control, a current baseline configuration of the system; and

• b. Review and update the baseline configuration of the system:

  • 1. [Assignment: frequency];

  • 2. When required due to [Assignment: circumstances]; and

  • 3. When system components are installed or upgraded.

Guidance

Baseline configurations for systems and system components include connectivity, operational, and communications aspects of systems. Baseline configurations are documented, formally reviewed, and agreed-upon specifications for systems or configuration items within those systems. Baseline configurations serve as a basis for future builds, releases, or changes to systems and include security and privacy control implementations, operational procedures, information about system components, network topology, and logical placement of components in the system architecture. Maintaining baseline configurations requires creating new baselines as organizational systems change over time. Baseline configurations of systems reflect the current enterprise architecture.

Implementation

Flux GitOps

The baseline configuration of each cluster is the tree clusters/<cluster> in talos-platform, versioned in git; nodes and tunnels are from code in talos-multicloud.

Status: implemented.

Evidence:

• Lula validation cm-2-flux-kustomizations-ready
• https://github.com/zeta-reticuli-inc/talos-platform/tree/main/clusters
• Manual check: flux get kustomizations -A

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