Autonomous Audits

An autonomous audit runs the deep pipeline, but lets you brief Golem the way you’d brief a human operator: you write the mission in plain English, and the agent plans around it.

How it works

Instead of only picking security focus areas, you provide a scope — a freeform instruction (up to ~1,500 characters) injected into Golem’s system prompt. The agent treats it as authoritative direction and plans accordingly. The scope can be as specific or open-ended as you want:
  • “Focus exclusively on the OAuth flow at auth.acme.com. Probe for token leakage, scope confusion, and replay vulnerabilities.”
  • “Find any way to access customer PII. Document the full kill chain end to end.”
  • “Test only the three subdomains passed as targets. Do not enumerate or interact with anything else under this domain.”

What the scope can include

Combine scope with security focus areas for layered steering.

Running an autonomous audit

API

Writing effective scope

Golem responds best to briefs that mirror real operator language: Good scope
Less effective scope
The more concrete the goal, the more focused the engagement.

Authorization caution

Autonomous mode gives Golem maximum latitude. The scope text is injected into the agent’s system prompt and acts as authoritative direction. Be precise about what’s in scope — and be certain you have written authorization for everything in the brief.

Next steps

The Golem Agent

How the agent interprets and acts on briefs.

Toolkit

What’s pre-installed in the darkops sandbox.