An SBOM is an ingredients list, not a safety check
What goes into a software bill of materials, what having one actually buys you, and the question it still cannot answer.
18 posts tagged “Security”.
What goes into a software bill of materials, what having one actually buys you, and the question it still cannot answer.
Why a padlock anyone can check but only you can close is what actually holds up HTTPS, SSH and signed commits.
From an unsigned image to a keyless signature anyone can verify, using Sigstore's public infrastructure. No key to lose.
Declare images and charts in one manifest, package them into a single archive, carry it across, and serve it from a binary with no dependencies.
One scanner for container images, dependencies, Terraform and secrets: install it, read its output, and fail a build on the right things.
Install Syft, scan an image or a directory, choose an output format, and wire it into CI so every build produces one.
cdxgen reads your lockfiles and build system rather than the finished image. How to run it, and when that difference matters.
How CycloneDX models components, dependencies and vulnerabilities, and when to pick it over SPDX.
Where SPDX came from, how its document model is shaped, and why licence teams reach for it before security teams do.
Watch a running cluster for attacks with Falco, stop running containers from being changed with a read-only root filesystem, and record every API request with audit logs.
Everything between a commit and a running Pod can be attacked. Minimal and signed images, scanning in CI, locked-down pipelines and secrets, and checks at runtime.
Enforce Pod Security Standards per namespace, limit what a container can do with AppArmor and seccomp, and isolate untrusted workloads with gVisor or Kata Containers.
Check a cluster against the CIS Kubernetes Benchmark with kube-bench, then control who can do what through the API server with authentication, RBAC and network policies.
A pre-commit hook that blocks AWS access key IDs, a commit-msg hook that enforces Conventional Commits, and Husky so a fresh clone arms them by itself.
Keep configuration out of your images with ConfigMaps, handle passwords and keys with Secrets, and know what base64 does and does not protect.
Generate a key, make a CSR, inspect a certificate, debug a TLS handshake, and convert between the formats that keep breaking.
Every Pod can reach every other Pod by default. Network policies cut that down to what you allow, starting from a default deny.
Upload a file to a Civo object store with s3cmd, then hand out a link that works for exactly one hour and then stops.