am I missing something here ? why not just render from the existing list and not have me trying to remember how they were named each time?
Luke Hinds
Verified account This account is verified. Learn more@decodebytes
752 Following 3.2K Followers 3K Posts
Latest posts 5
Hey @grok build how are you finding life with nono.sh running underneath you as the security primitive ?
Has anyone found a decent red team agent project around? OSS please, not interested vendor SaaS.
AI agents don't just answer questions any more. They write code, run it, call tools, and spin up sub-agents to do the work.
Every one of those hand-offs is a new place for things to go wrong: a leaked credential, a poisoned dependency, or a sub-agent that reads far more than it should.
On 2 November I'm joining Amazon Web Services (AWS) for a webinar:
Secure AI Agents on Amazon EKS: Sandboxing Sub-Agents with nono.
We'll show how to layer two levels of defense:
→ Amazon EKS isolation around the workload
→ nono's kernel-enforced agent runtime protections around every agent and tool inside it
No root, no code rewrites, nothing for the agent to talk its way around.
If you're running agents on Kubernetes, or about to, come along.
Registration link in the reply 👇
#AIAgents #Kubernetes #AmazonEKS #AppSec #OpenSource
Every one of those hand-offs is a new place for things to go wrong: a leaked credential, a poisoned dependency, or a sub-agent that reads far more than it should.
On 2 November I'm joining Amazon Web Services (AWS) for a webinar:
Secure AI Agents on Amazon EKS: Sandboxing Sub-Agents with nono.
We'll show how to layer two levels of defense:
→ Amazon EKS isolation around the workload
→ nono's kernel-enforced agent runtime protections around every agent and tool inside it
No root, no code rewrites, nothing for the agent to talk its way around.
If you're running agents on Kubernetes, or about to, come along.
Registration link in the reply 👇
#AIAgents #Kubernetes #AmazonEKS #AppSec #OpenSource
The Kubernetes (Official) agent-sandbox project now has a nice rendered example of building a zero trust Grafana agent on a nono protected pod - where the agent is limited to specific scoped execution path when using the Grafana LogCLI.
Having this level of fine-grained execution means you can leave an agent unattended without concern of unwarranted actions as the credential is locked to only a single tools execution path. This is a deeper level of protection you won't get from other projects like @NVIDIA 's Open Agent Safety Platform, which although it can bind credentials to approved endpoints and restrict network access by binary, its sandbox policy does not constrain command-line arguments or make filesystem access and credentials specific to only an individual command and no other.
agent-sandbox.sigs.k8s.io/docs/use-cases…
agent-sandbox.sigs.k8s.io nono with Kubernetes Agent Sandbox Runs nono inside a Kubernetes Sandbox, demonstrating defense in depth for an AI agent with layered isolation and tool execution. Having this level of fine-grained execution means you can leave an agent unattended without concern of unwarranted actions as the credential is locked to only a single tools execution path. This is a deeper level of protection you won't get from other projects like @NVIDIA 's Open Agent Safety Platform, which although it can bind credentials to approved endpoints and restrict network access by binary, its sandbox policy does not constrain command-line arguments or make filesystem access and credentials specific to only an individual command and no other.
agent-sandbox.sigs.k8s.io/docs/use-cases…