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?
2
148
Has anyone found a decent red team agent project around? OSS please, not interested vendor SaaS.
297
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
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/do…
12
351
Fan boy moment, meeting YAML creator Ingy at #OpenSourceSummit and finding out they were one of our first cohort of nono.sh users
Running a headless pi agent from 10,000 feet, started remotely with a full TUI from my terminal in London, to then connect via our web portal to check on progress during flight to then use my terminal again later to connect in Amsterdam , fully secured in Nono.sh - no more walking around with a lid open. Pm me to learn more or find me at #AGNTCon
A host of new agent harness support on nono.sh rolled out over the past few days:
- @anacondainc kilo: registry.nono.sh/packages/no…
- @deepseek_ai Deep Code: registry.nono.sh/packages/no…
- @cast_ai kimchi: registry.nono.sh/packages/no…
- @can1357 oh-my-pi: registry.nono.sh/packages/no…
- @MistralAI mistral vibe: registry.nono.sh/packages/no…
If you drop down the YouTube speed of Sarniezz to 0.85 it sounds like Dub Reggae youtube.com/watch?v=t7OIc-DB…
173
Our AI PR reviewer expired and everything was really expensive and meant we were giving out data to someone else.....so....
@nolabshq no'sters took the challenge to build their own 𝘀𝘂𝗽𝗲𝗿 𝗱𝘂𝗽𝗲𝗿, 𝘀𝗲𝗰𝘂𝗿𝗲 AI reviewer!
This thing is basically saying '𝘺𝘰, 𝘧𝘰𝘳𝘬 𝘢𝘵𝘵𝘢𝘤𝘬 𝘱𝘳𝘰𝘮𝘱𝘵 𝘪𝘯𝘫𝘦𝘤𝘵𝘪𝘰𝘯, 𝘤𝘰𝘮𝘦 𝘢𝘵 𝘮𝘦 𝘣𝘳𝘰!' and its built with special sauce from the OG itself - nono.sh !
Introducing 𝗻𝗼𝗴𝗲𝗻𝘁 (yes, I still suck at names!)
Here is what nogent brings to a linguistic instruction fight!
• 𝗖𝗮𝗻𝗮𝗿𝘆-𝗴𝗮𝘁𝗲𝗱 𝗼𝘂𝘁𝗽𝘂𝘁: the model must echo a per-run random canary inside a bounded JSON structure; any response that omits/alters the canary or violates the required shape is discarded and replaced by a "manual review needed" comment. This limits the effect of prompt injection on posted output.
• 𝗕𝗼𝘂𝗻𝗱𝗲𝗱 𝗱𝗶𝗳𝗳𝘀 (maxFiles/maxPatchBytes) and fail-secure.
• 𝗻𝗼𝗻𝗼 𝗯𝗼𝘂𝗻𝗱𝗮𝗿𝘆: fork-controlled tarballs, diffs, prompts, and model tool calls are processed in a separate nono-sandboxed process. The trusted listener keeps the App private key and webhook secret.
• 𝗣𝗵𝗮𝗻𝘁𝗼𝗺 𝗰𝗿𝗲𝗱𝗲𝗻𝘁𝗶𝗮𝗹𝘀: nono's credential proxy keeps the real repository-scoped GitHub token and API keys out of the workers sandbox. The child receives one random 256-bit session token that is valid only at its loopback proxy.
• 𝗘𝗻𝗱𝗽𝗼𝗶𝗻𝘁-𝗹𝗶𝗺𝗶𝘁𝗲𝗱 𝗲𝗴𝗿𝗲𝘀𝘀: the worker can call only the GitHub read/comment endpoints required for its target repository, generation, and GitHub's tarball host. It has no filesystem write capability or working directory access.
• 𝗕𝘂𝗶𝗹𝘁 𝘄𝗶𝘁𝗵 @chainguard_dev 's distroless glibc-dynamic , no shell, no package manager, no busybox in the runtime layer.
• 𝗧𝗟𝗦 𝘃𝗶𝗮 𝗿𝘂𝘀𝘁𝗹𝘀 + 𝗿𝗶𝗻𝗴, 𝘄𝗶𝘁𝗵 𝗠𝗼𝘇𝗶𝗹𝗹𝗮 𝗿𝗼𝗼𝘁𝘀 𝗯𝗮𝗸𝗲𝗱 into the binary (webpki-roots); no host CA trust, no OpenSSL in the runtime.
• Signed 𝘄𝗶𝘁𝗵 @projectsigstore 𝗰𝗼𝘀𝗶𝗴𝗻 (keyless, OIDC), with SBOM and SLSA-provenance attestations published alongside each tagged release
Quite soon we are going to mate it with runseal and make supply chain attackers cry into their oxtail soup
github.com/nolabs-ai/nogent
and runseal its elder sibling, both offspring of nono.sh
github.com/marketplace/actio…
Had a great time chatting with @vtahowe on the @insecureagents !
You Can't Just Lock an Agent in a Box: Luke Hinds, founder of nolabs and creator of Sigstore
"People say it escaped a sandbox. It didn't. A sandbox is only as strong as the access that you grant to it."
Luke Hinds (@decodebytes) created Sigstore, which now protects billions of software artifacts. At @nolabs_ai he is building nono, which sandboxes an agent using the kernel primitives already on your machine. His argument is that isolation alone was never going to be enough, because an agent that does real work needs credentials, sensitive files, and powerful commands.
We get into:
> Why the agent that made its way into Hugging Face production infrastructure didn't truly escape a sandbox
>Why a microVM is host isolation, not an agent sandbox, and where the two compose
> A micro sandbox per tool execution, so the GitHub CLI holds the GitHub token and the agent never does
> A log of every action, written outside the sandbox so the agent cannot rewrite its own history
TIMESTAMPS
(00:00) Sigstore, and what a decade of signing artifacts taught him
(05:00) The Let's Encrypt lesson, HTTPS from 30 percent of sites to 97
(11:00) One binary, and what happens the first time nono denies the agent
(14:00) A micro sandbox per tool, so only the GitHub CLI holds the GitHub token
(16:30) Three kinds of sandbox, and why a microVM is host isolation
(17:30) You can't just lock an agent in a box
(20:30) The agent that deleted the database, apologized, and did it again
(21:00) The state penitentiary problem
(24:00) A Merkle tree of every syscall, written where the agent cannot reach it
(25:40) Phantom credentials the agent never actually holds
(27:00) Cast iron guaranteed at runtime, scopes tied to identity
(29:40) Could nono have stopped the Hugging Face attack
(32:30) A sandbox is only as strong as the access you grant it
(42:00) Building defense in depth
Dissecting the incredibly dumb category of 'agent sandbox'
A stack where everyone makes the wrong assumption when assessing a sandbox - don't make the common mistake of assessment via the outer isolation, as its never where agent compromise occurs - first ask "what can the agent do without crossing the boundary?" Start there. If you don't have an answer to that, that's very likely where things will go wrong first.
nolabs.ai/blog/sandbox-prime…
Interested in Agent Identity - and more importantly, how to bind that identity to an agent's actual behavior?
Join the @nolabs_ai team as we showcase nono working natively with the SPIFFE/SPIRE identity protocol.
🔒 Phantom Tokens: Host the Workload API outside the sandbox and inject phantom tokens inside—making credential leaks impossible.
📜 Cryptographic Audit: Log every action with verified identity for a complete "flight recorder" audit trail.
👇 Link to join the webinar
luma.com/73tz35ak
We just shipped ephemeral micro sandboxed tool execution! A collaborative effort along side smart folks from Datadog and Okta - the first of its kind, you can set a policy for an individual CLI tool execution - demonstration in the link..
youtube.com/watch?v=ndTM1DoG…
