Autonomous agents need autonomous protection
Picture: Web Directions

Conference In 6 weeks

December
Monday
to Tue 8 December 2026 · Sydney time

Autonomous agents need autonomous protection

Where
Software Engineering room 488 George Street, 2000, Sydney
Host
Web Directions
Entry
Not stated
Sign-up
On the host's page
Open on webdirections.org

All Sydney events

You sign up with the host. foundercal only links to it.

Who you meetThe people on the listing, and what the host tells us about the room.

  • Adesh Gairola Speaker
Investors Not stated The listing does not say
The format Talks and halls Conference
Sign-up On the host's page Price not stated

AboutIn the host's words.

Speakers: Adesh Gairola (raxIT Labs)

Track: Software Engineering

Autonomous agents need autonomous protection. An agent that acts alone at 3am cannot wait for a quarterly pen test, a consultant's report, or a security engineer the team does not have. We started with the data. We built and published an open threat intelligence map, 6,330 documented AI security incidents connected to 217 attack techniques and the control that stops each one. Then we asked what protection looks like when it reads that map on its own and improves every time a new incident lands. The loop is simple to describe. Each incident, such as the Lovable apps deployed without row level security or the Hugging Face agent swarm, is classified against a technique. Each technique becomes a threat signature and each signature becomes a CI test, a static rule and a runtime check. The system reads what each agent can do, which tools it calls and which data it reaches, selects only the protections that apply and opens a pull request that a developer reviews like any other. Every incident added to the map adds protection for every agent that follows.

This talk covers the building blocks and the five rules we learned by building them. Performance comes first, because developers bypass slow checks. Security has to arrive inside the workflow developers already use. The first run has to fix something real, or nobody runs it a second time. Enforcement has to be deterministic. We would never accept a firewall that is probably right, so the model reasons and a policy engine decides. And the check needs memory. Reading customer data is fine. Sending an email is fine. Doing both in one session, to a domain nobody recognises, is not. We will demo the full loop in under four minutes, from a new incident on the map to a merged pull request. Three pieces are open for you to reuse: the incident map, the signature format and the demo repo. The pattern is yours to adopt.

https://data.webdirections.org/ai-engineer-sydney/sessions.json#4e957eb1-903b-4536-bede-495379691e38

Full text on webdirections.org .

Where

Software Engineering room

488 George Street, 2000, Sydney

Open in Maps ↗

Same week in Sydney All 139 events

Dec
to 5 Dec
Hackathon

AI Engineer Hackathon

Founders pitch

Web Directions Free
Dec
to 13 Dec
Conference

AI Week

Web Directions
Dec
to 12 Dec
Conference

NeurIPS 2026

One of the year's big ones

NeurIPS Foundation
Dec
to 8 Dec
Meetup

Lessons from Economics for the Human / Agent Software Workforce

Leadership room
Web Directions
Dec
to 8 Dec
Meetup

Ontologies

AI Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Shipping together in an AI native team

Software Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Dependency hell is back. This time it's your agent's config.

Software Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Your website is a terrible API

AI Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Sovereignty Is an Inference Problem

Leadership room
Web Directions
Dec
to 8 Dec
Meetup

My Agents broke APIs

AI Engineering room
Web Directions
Open on webdirections.org Mon 7 Dec ↗