Posts

Showing posts from October, 2026

Own the pipeline (Part 3)

  Own the pipeline Frozen supply, net-off CI, Ansible for the herd, WebAuthn at the forge, OpenBao for secrets, and canaries against our digest This is the part 3 deep dive under Harden your servers. Own your trust .  which lays out the full map. You own the trust chain. If a third party is hacked, you should not be owned. Seal the golden OS ( part 2 ) made the host an artifact. This post covers everything that produces that artifact and moves it into the herd: the inputs, the build, the people and agents allowed to promote, and the identity layer in front of all of it. Golden supply, golden image Two things get called "golden," and they are different: Golden supply is the frozen set of inputs CI is allowed to fetch: base images mirrored by digest, base RPMs, Python wheels, vendored modules, and the git SHA of the source itself. It is audited before it enters, and it changes only through review. Golden image is the sealed output: the digest cattle boot. An image i...

Seal the golden OS (Part 2)

Image
Seal the golden OS Dockerfile to bootc to our registry, Ignition on first boot, and a host that has nothing to drift This is the first deep dive under Harden your servers. Own your trust.  which lays out the full map. You own the trust chain. If a third party is hacked, you should not be owned. For the host, that means the OS your cattle boot is an artifact you built, signed, and served yourself. Two artifacts are the OS source of truth The OS has exactly two authored sources, and both live in our git: An IaC Dockerfile. CI builds it with bootc into a bootable OCI image, signs it, and pushes it to our LAN registry. The Dockerfile plus the frozen golden supply it consumes is the full OS recipe. Our Ignition config for a minimal ostree-based Fedora CoreOS (or a bootc-derived sibling). Ignition runs on first boot, sets identity and hardening, and starts containerized workloads pulled from our registry. Ansible is not the OS source of truth. It orchestrates the herd from CI,...

Harden your servers. Own your trust.

Image
Harden your servers. Own your trust. How to do security right in the time of AI Agents It's very difficult task to be secure when everybody is acting like "Tony Stark" with his Iron Man suit and JARVIS-like AI Agent. CVE feeds look like weather reports: remote code execution, privilege escalation, sandbox escapes. And this month a public Certificate Authority failed so badly that one private key was the digit 4 . That mess favors attackers. Stacked controls still hold if you treat every layer as disposable and pin the roots yourself. This post is the map. Seal the golden OS ( part 2 ) covers the host; Own the pipeline ( part 3 ) covers supply, CI, and the herd. You own the trust chain. If a third party is hacked, you should not be owned. The eMudhra lesson In October 2026, reporting on the Indian CA eMudhra described private keys for several intermediates that were trivial to guess. One was literally the number 4 ; others were below 256. Anyone who recovered them could...