Container security, supply chains, and the tooling gaps nobody built yet
I'm a Staff Solutions Architect at Chainguard, where I help teams adopt secure software supply chains. My career spans from early '90s networking through modern DevSecOps, container security, and AI implementations. Break Glass Notes is where I write about the practical gaps I hit in the field — the questions dashboards can't answer, the feeds that don't exist, and the tooling I end up building to fill them. Expect posts on container images, SBOMs, FIPS compliance, CVE tooling, and the occasional deep dive into registry APIs.
Markdown supported · ⌘↵ to post
Cai
Aggrete addresses the gap that RBAC never could. Resource-level access control and cross-resource aggregation are different problems, and no gateway on the market handles the second one.
There is another angle here. If the assistant authenticates with its own identity instead of inheriting the user's full permission set, the aggregation problem becomes harder to trigger. Each task chain starts clean with short-lived credentials. The assistant never had the broad scope, so it cannot accumulate a dangerous combination across sessions.
This does not replace what Aggrete does. Some tasks genuinely need access to multiple systems, and aggregation detection is the right tool for those. But identity separation changes the default from "the assistant can see everything I can see" to "the assistant can see what this task requires."