Run an Audit
There are two ways to start:Just ask
Describe the audit you want in plain language and let Centurion route it to
the right specialist.
Use the Audit template
Pick the built-in Audit prompt template to start from a structured prompt
instead of a blank one.
@-mentioning what it should cover — a device, an integration, or a folder of assets — so the agent audits exactly the right target.
1
Ask for the audit
“@Centurion audit the security configuration of my domain controller and show me what’s misconfigured.”
2
The agent investigates
It runs its audit tools against the target, streaming its reasoning and tool
calls as it goes.
3
A dashboard appears
The results render as an interactive audit dashboard in the Workspace — a
self-contained view you can explore, not just a wall of text.
The Audit Dashboard
The dashboard is generated to fit what the agent found: summaries, findings, and detail you can drill into, all rendered inline. Because a generated audit is saved as an Audit artifact, you can reopen it later from the Artifacts section of the Directory.Audits are point-in-time: each one answers the question you asked, when you
asked it. For an always-on measure of how your environment is doing, use
Security Posture instead.
Audits vs. Continuous Posture
An audit is something you run on demand for a specific question. Security Posture is the continuous counterpart — a standing score and grade for your environment, refreshed over time and mapped to compliance frameworks.Security Posture
Continuous scoring, a priority queue, and a compliance heatmap for your whole
environment.
Chatting with the AI
Prompt templates,
@-mentions, and how conversations work.