Skip to content

docs: map CDS controls to Zero Trust principles - #1069

Merged
RonaldHensbergen merged 2 commits into
mainfrom
agents/implement-and-pr-issue-778
Oct 31, 2026
Merged

RonaldHensbergen merged 2 commits into
mainfrom
agents/implement-and-pr-issue-778

Conversation

@RonaldHensbergen

Copy link
Copy Markdown
Owner

Summary

  • Add a NIST SP 800-207 mapping for CDS identity, transport, least-privilege, audit, and target-specific controls, including remaining gaps.
  • Align the Haven parity plan and roadmap with delivered NetworkPolicy and maturity work, and link the Secured tier definition to the mapping.
  • Clarify in cds maturity text output that contract presence is not runtime enforcement or NIST conformity.
  • File and order the separate workload-identity follow-up (Define a workload-identity contract for attested service identity #1068).

Validation

  • python -m unittest tests.test_maturity
  • ruff check cli/maturity.py tests/test_maturity.py
  • npx --yes markdownlint-cli@0.49.0 docs/zero-trust-architecture.md docs/haven-parity-plan.md docs/roadmap.md CHANGELOG.md
  • git diff --check

Closes #778
References #1068

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@sonarqubecloud

Copy link
Copy Markdown

@RonaldHensbergen
RonaldHensbergen merged commit 69a8229 into main Oct 31, 2026
16 checks passed
@RonaldHensbergen
RonaldHensbergen deleted the agents/implement-and-pr-issue-778 branch October 31, 2026 22:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Define an explicit Zero-Trust Architecture maturity tier consolidating TLS, identity, mesh, and network-policy work

1 participant