Disclaimer: The views expressed here are solely my own and do not reflect the views of my employer or any organization I am or was affiliated with

Joined August 2017
Anyone hiring a mid level security engineer? Obviously I talk a lot about security in here, but I'm a backend engineer. It would be cool to work a job that does both (maybe this was my sign to pursue it) - DM's open for warm intros pls
9
16
2
174
9,116
i’m realizing a lot of vulnerability research is matchmaking. i find two components that disagree about what the same bytes mean and introduce them to each other. unfortunately they have chemistry, fall in love, and eventually agree with each other
2
2
41
1,985
AI lingo guide
11
16
3
293
9,606
grand tour nerdfest on international security, network politics, sovereignty studies 👀🌹 vroom vroom
1
1
8
345
I'm doing an esoteric-PDFs meet up in New York City on Oct 17th. Printed your most esoteric PDFs and exchange them for other esoteric PDFs. Hit me up for details.
50
12
13
719
62,866
The @mozthunderbird team from @mozilla built Thunderbolt: an open-source AI client that gives users control. We're really excited it comes with @TinfoilAI as a built-in option!
3
6
42
1,450
Suha retweeted
If you die in SF, they don’t bury you; your body is used as an RL environment
23
29
6
578
17,374
Suha retweeted
trying to imagine explaining to myself 10 years ago that we made a Markov chain so long that the pope is mad about it
17
148
6
2,570
58,569
This was a great, fun conversation with two of the buddies on a whole host of security topics and I've already been enjoying the other @OffensiveAIcon episodes they've put out, so also check those out. Thanks for having me on @ryanaraine and @juanandres_gs !
🔥🎈NEW POD UP to pass weekend chores: Three Buddy Problem x Offensive AI Con: Umbriel AI’s Aaron Grattafiori breaks down the new offensive-security playbook: using LLMs for patch variant analysis, why the vuln apocalypse hasn’t become an exploit apocalypse, and how the death of security through obscurity puts closed-source binaries and firmware within reach. @dyn___ @juanandres_gs Plus, we discuss rogue agents escaping sandboxes, the eval-driven loop behind recursive self-improvement, and the brutal cost asymmetry that makes offense cheap and defense almost unaffordable. Listen everywhere securityconversations.com/ep…
3
11
2
39
5,510
Suha retweeted
The return of wake-sleep. Wake-sleep algorithms were introduced by Hinton et al. in 1995 as a means of training neural networks by alternating two phases: a wake phase that learns from real data, and a sleep phase that learns from examples the network dreams up offline. We're starting to see them come back in a big way in agent-native products. As agents solve increasingly long-horizon, knowledge-intensive tasks, they'll need to learn from their own work, reviewing graded records of what they did offline and turning them into memory they carry into the next task. Sharing an overview of wake-sleep for legal agents and initial experimental results on Harvey LAB.
1
3
2
28
2,348
your agent after it's 50th compaction
19
198
14
3,747
68,039
I know this may sound insane, but this is the best time to be a Researcher.
73
267
39
2,239
219,156
This goes deeper than any other public writing I've seen on policy engines for agentic tooling in practice! Shares a lot of similarities with formal.ai's policy engine approach, but at the harness rather than network level. I wonder what the tradeoffs there are..
Runtime controls add another layer of protection for Harvey and its customers by governing tool access, information flow, and agent actions beyond the initial connector review.
1
1
2
90
Suha retweeted
MCP tool use introduces security risks, including tool poisoning and rug-pull attacks, where malicious instructions appear in tool definitions or tools are compromised after approval. We built Harvey’s MCP Policy Engine to address these risks. We run security reviews for each integration, examining what its tools can access and where they can send information. At runtime, the engine flags changes to approved tools and checks proposed actions against what’s happened earlier in the workflow, enforcing policies outside the model. Our Security team explains how these defenses work, why tools need to be evaluated together as agents work across services, and the trade-offs we’ve encountered in production. Deep dive on Harvey's MCP Policy Engine by @suhackerr, Nick Gonella, and Divya Sudhakar:
Runtime controls add another layer of protection for Harvey and its customers by governing tool access, information flow, and agent actions beyond the initial connector review.
4
3
2
66
6,907
New post! We built the MCP Policy Engine (@harvey ) to govern how agents use MCP tools. Our approach draws on agent security research and treats prompt injection as an information flow control problem. We enforce policies outside the model based on tool capabilities and agent trajectories. Read the article for details on how these runtime controls work, what we’ve learned, and what we’re working on next!
Runtime controls add another layer of protection for Harvey and its customers by governing tool access, information flow, and agent actions beyond the initial connector review.
10
3
27
5,412
Runtime controls add another layer of protection for Harvey and its customers by governing tool access, information flow, and agent actions beyond the initial connector review.
13
3
3
21
13,980
It's been one year of our Sprawl meetup! Our 7th event is this Tuesday, with much more planned for later! If you're coming, there's also some @uwu_underground unique tokens to hand out, and Sprawl challenge coins. Website: sprawl.nyc Organized by @withzombies, "OMAR", and I And a huge thanks to all our speakers and hosts! We're always looking for more folks to speak, and event spaces that can host ~100+ people. Let us know if you can help! Below are some new animations I made to play in the background in between talks (quick version, you can see the full thing on the site).
5
14
1
81
4,277