Skip to content

Add FIPS 140-3, config provenance, and drift detection#7

Merged
bbe64 merged 8 commits intomainfrom
update/fips-provenance-compliance
Mar 7, 2026
Merged

Add FIPS 140-3, config provenance, and drift detection#7
bbe64 merged 8 commits intomainfrom
update/fips-provenance-compliance

Conversation

@ndreno
Copy link
Copy Markdown
Contributor

@ndreno ndreno commented Mar 5, 2026

Summary

  • Landing page: Add 3 new feature cards (FIPS 140-3, Bot Detection, Config Provenance) bringing the grid to 15 cards (5 clean rows). Add provenance/drift detection to control plane bullets, dedicated admin API to data plane bullets, and FIPS to TLS bullet.
  • Blog: Split the compliance article into two parts (~1,500 words each). Part 1 covers the architecture argument (artifact provenance, drift detection, access controls, OPA logs). Part 2 covers operational controls (schema validation, secrets, FIPS 140-3, GitOps, framework mapping table).
  • Compliance mapping: Add FedRAMP SC-13, CMMC L3 SC.3.177, and PCI DSS Req. 3 to the framework mapping table.

Sources: PR #40 in Barbacane (FIPS guide), CHANGELOG [Unreleased] section (provenance, drift detection, admin API).

Test plan

  • Verify landing page renders 15 feature cards in clean 3-column rows
  • Verify both blog posts render correctly and cross-links work
  • Review Part 2 publish date (2026-03-05) — adjust if not publishing today

Landing page:
- Add FIPS 140-3 Ready, Bot Detection, and Config Provenance feature cards (12 → 15, 5 clean rows)
- Add artifact provenance and drift detection to control plane bullets
- Add dedicated admin API to data plane bullets
- Update TLS bullet to mention FIPS 140-3

Blog:
- Split compliance article into two parts for readability
- Part 1: artifact provenance, drift detection, access controls, OPA logs
- Part 2: schema validation, secrets, FIPS 140-3, GitOps, framework mapping
- Add FedRAMP SC-13, CMMC L3 SC.3.177, PCI DSS Req. 3 to compliance mapping table
- Fix duplicate YAML path key in OpenAPI example
@ndreno ndreno assigned ndreno and bbe64 and unassigned ndreno Mar 5, 2026
@ndreno ndreno added documentation Improvements or additions to documentation enhancement New feature or request labels Mar 5, 2026
Comment thread src/content/blog/compliance-by-construction-part-1.md Outdated
Comment thread src/content/blog/compliance-by-construction-part-1.md Outdated
Comment thread src/content/blog/compliance-by-construction-part-1.md Outdated
Comment thread src/content/blog/compliance-by-construction-part-1.md Outdated
Comment thread src/content/blog/compliance-by-construction-part-2.md Outdated
Comment thread src/content/blog/compliance-by-construction-part-2.md Outdated
Comment thread src/content/blog/compliance-by-construction-part-2.md
Comment thread src/content/blog/compliance-by-construction-part-2.md Outdated
Comment thread src/pages/index.astro
ndreno and others added 7 commits March 5, 2026 15:51
Co-authored-by: Baptiste Be <72380093+bbe64@users.noreply.github.com>
Co-authored-by: Baptiste Be <72380093+bbe64@users.noreply.github.com>
Co-authored-by: Baptiste Be <72380093+bbe64@users.noreply.github.com>
Co-authored-by: Baptiste Be <72380093+bbe64@users.noreply.github.com>
Co-authored-by: Baptiste Be <72380093+bbe64@users.noreply.github.com>
Co-authored-by: Baptiste Be <72380093+bbe64@users.noreply.github.com>
Co-authored-by: Baptiste Be <72380093+bbe64@users.noreply.github.com>
---
title: "Compliance by design, part 1: how Barbacane becomes your API audit trail"
description: "Auditors don't just ask whether you have security controls. They ask how you can prove those controls were actually enforced. Explore how Barbacane's compiled approach turns your API gateway into a verifiable compliance artifact."
publishDate: 2026-02-18
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
publishDate: 2026-02-18
publishDate: 2026-03-07

---
title: "Compliance by design, part 2: the compliance controls"
description: "From schema validation and secrets management to FIPS 140-3 cryptography and GitOps workflows — the specific controls Barbacane provides for SOC 2, PCI DSS, HIPAA, FedRAMP, and beyond."
publishDate: 2026-03-05
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
publishDate: 2026-03-05
publishDate: 2026-03-07

@bbe64 bbe64 merged commit e21526b into main Mar 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants