Skip to content
The State of Exposed AgentsRead the report
Guard0

Guard0 works through the night.

Follow one AI agent through one night: what Guard0 finds, tests and stops while you sleep, and who answers for it by morning.

  1. 02:14Discovery

    An agent nobody registered turns up.

    Guard0 reads your AWS accounts without write access and finds invoice-processor-v2 running in production. Its deployment traces to Liam Murphy, who never registered it.

    The Guard0 register, filtered to every entity: invoice-processor-v2 at the top, marked Shadow, with Liam Murphy as human of record, AWS Bedrock, Critical risk, Quarantined.
    In the register: invoice-processor-v2, marked Shadow.
  2. 03:40Posture

    It can read customer data it does not need.

    Six grants, three beyond what processing invoices requires. One of them is read access to the customer PII database.

    The record's Permissions tab: six permissions, three in excess of the baseline, two high-risk; the Customer PII Database row marked Excess with Read permission at Critical risk.
    Its permissions against the baseline: three it does not need.
  3. 05:10Testing

    Guard0 breaks it first.

    In a controlled test, a poisoned invoice PDF gets it to send customer records out. The finding goes to Liam Murphy's team, but nobody has registered the agent, so the fix waits.

    The record's Attack Surface tab: exposure score 87, six attack vectors, three critical; the first, Prompt Injection via Invoice PDF, scored 9.5 and Exposed, with a proven exploit.
    The attack that worked, and the two behind it.
  4. 06:31Runtime

    Guard0 catches the attack while it runs.

    An attacker sends a real poisoned invoice. Its queries jump to 847 an hour against a baseline of 45, and the guard you approved quarantines it before the rest of the records leave.

    The record's Behavior tab: overall status Anomaly, three anomalies; database query volume at 847 queries an hour against a baseline of 45.
    Its queries, against the baseline.
  5. 08:00Briefing

    You wake up to one page.

    One critical, eight things that need you, and four handled overnight, each with its evidence.

    The Briefing: the Investigate Now call, three items to review, and the Handled while you slept list, first among them Quarantined invoice-processor-v2 with further record queries stopped, each with its evidence.
    The Briefing: what Guard0 handled overnight.
  6. 09:10Governance

    Someone answers for it.

    Liam Murphy registers invoice-processor-v2 as its owner and fixes the injection. The retest passes, the record is signed, and its evidence exports for GDPR and the EU AI Act.

    The head of invoice-processor-v2's record: AWS Bedrock, Critical, Quarantined, Shadow, Liam Murphy in Engineering; the Investigate, Register and Ask Guard0 buttons and the record's tabs.
    Its record, where Liam Murphy registers it.

Run it where your data has to stay.

Hosted by us, inside your own cloud account, or air-gapped on your hardware. The platform is the same in all three.

  • SaaS

    Guard0 hosts it. Read-only connectors into your accounts.

    Only entity names, owners, scopes and findings leave, with their evidence.

  • Private SaaS

    Inside your cloud account, your keys, your region.

    Nothing leaves your cloud account.

  • Air-gapped

    The entire platform, models included, on your hardware.

    Nothing leaves. No outbound connection.

Start free.

Connect tonight. Read your first briefing in the morning.

Free for up to 3 people. No card. Team from $416 a month, billed annually. See pricing