Francis Alexander

236 posts

Francis Alexander

Francis Alexander

@torque59

Security Engineering

SF Katılım Nisan 2013
797 Takip Edilen344 Takipçiler
Francis Alexander
Francis Alexander@torque59·
@decodebytes I see btw, I saw from the documentation that After apply(), there is no way to expand permissions. The sandbox persists for the lifetime of the process and all child processes. /tmp/myapp-<session-id> would not work with nono in that case right ?
English
1
0
0
20
Luke Hinds
Luke Hinds@decodebytes·
@torque59 The answer is: don't grant /tmp. Grant /tmp/myapp-<session-id>/ instead. But nono isn't a guest/host isolation layer; plenty already do a good job there (Kata, Firecracker). This is granular, OS-enforced resource control over what an agent may or may not access.
English
1
0
1
40
Luke Hinds
Luke Hinds@decodebytes·
Containers and microVMs solved a well-defined problem: process isolation between workload and host. They are best in class for host/guest isolation, resource constraint and environment isolation. Industry transformative and nothing less. The mistake is assuming the same specialism solves the new problems that agents present. An agent is not a workload to isolate, it's far more nuanced. It is an autonomous decision-making system operating , sometimes on your behalf, at runtime, against often sensitive material, in ways that cannot be fully anticipated at launch time. Placing it in an isolated environment and considering the security problem solved because the host is protected and the guest is isolated is not enough. The agent needs access to sensitive resources to do its job, and those resources require protection as well. When the agent needs capabilities beyond its initial grant, it requires a secure, mediated channel to request them. Without one, privilege elevation becomes a path that bypasses the very isolation boundary you depended on. Existing primitives enforce boundaries. They do not enforce intent, auditability, or runtime access control over an actor whose behaviour is non-deterministic by design. Nono is built on a different premise: the sandboxed process is untrusted by construction, and capabilities are granted dynamically under explicit oversight, enforced at the kernel level, and recorded with immutably. The supervisor is the mechanism that realises this, and its nono's superpower. The supervisor runs outside the sandbox, intercepts every file access syscall via seccomp-notify, and mediates every access decision before it reaches its entity. The agent never executes its own calls. Privilege elevation requests are trapped, approved over a secure verified channel, and fulfilled via direct file descriptor injection. The audit trail and access gate - is not an instrumentation on top of execution. It is direct in the execution path. API credentials never enter the agent's address space. Files can be cryptographically attested, right back to the source code - before the agent even reads or executes them. And the best bit of all, already have a container orchestration system in place, well nono runs quite at home in either a container or a microVM - belt, braces, and a safety harness. This is not a tightening of existing primitives or a repurposing of previous tools. It is an approach purpose-built for a new era. nono.sh #AgenticAI #Security
Luke Hinds tweet media
English
2
3
11
621
Francis Alexander
Francis Alexander@torque59·
@ZackKorman Definitely observability and detection. Also wouldn't it be better to just manage the MCP servers, especially with enterprise controls available for claude ?
English
1
0
1
122
Zack Korman
Zack Korman@ZackKorman·
If I were a CISO at an org full of devs running Claude Code, I’d focus super hard on observability and detection. Use Claude hooks to pipe audit logs to a server you control, and run frequent AI jobs on those logs to look for problems (eg malicious MCP servers).
English
14
9
142
11.2K
Francis Alexander
Francis Alexander@torque59·
4 Chained zero days and to top it of ML to detect what pictures/documents are relevant to them. Operation Triangulation is quite interesting. Vid: youtube.com/watch?v=7VWNUU…
YouTube video
YouTube
English
0
1
1
252
Jake
Jake@JustJake·
Does @LinkedIn, the 26B company, not have a fucking way to verify employment? Am i taking crazy pills?
English
43
14
646
205.7K
Francis Alexander retweetledi
Luke Young
Luke Young@TheBoredEng·
I'm kicking off a series of blog posts about interesting vulnerabilities I've found and responsibly disclosed over the years, starting with a complex chain of vulnerabilities leading to XSS on accounts.leagueoflegends.com back in 2016: @bored.engineer/xss-on-account-leagueoflegends-com-via-easyxdm-2016-75bcf9d582b5" target="_blank" rel="nofollow noopener">medium.com/@bored.enginee…
English
2
88
298
0
Francis Alexander retweetledi
stephen
stephen@_tsuro·
I made a website: leaky.page
English
10
283
930
0
Ajin Abraham
Ajin Abraham@ajinabraham·
@torque59 A nifty use of V8 Isolates, should call it CaaS: Coroutine as a Service
English
1
0
0
0
Francis Alexander retweetledi
Black Hat
Black Hat@BlackHatEvents·
Learn to pentest the modern stack including continuous build & deployment tools, message brokers, configuration & resource management systems, and distributed file systems from end-to-end in #BHEU Training w/ @torque59 & @tunnelshade_ ow.ly/jAre30lWMI6
English
0
9
15
0