HOW IT WORKS
Two lines of config.
Every AI call evidenced.
This page walks through exactly what happens to an AI call inside Guard: what gets checked, what gets signed, and why an auditor can trust the result. Ten minutes, no prior knowledge assumed.
Step 01
Point your AI calls through Guard
Swap the base URL and API key in your app config. Guard works with any OpenAI-compatible endpoint: OpenAI, Anthropic, Azure AI, Bedrock, Gemini, or your own model. Existing code keeps working. Typical integration is under a day.
Step 02
Every call checked, signed, logged
Guard intercepts the request, scans for PII, checks for prompt injection, flags cross-border disclosure, and generates a signed attestation. The call continues to the provider. The response is scanned on the way back. Detection overhead is typically under 50 milliseconds, plus the upstream call.
Step 03
An audit trail your board and regulators can trust
Every call is logged with timestamp, model, user, PII findings, compliance outcome, and regulatory mapping against CPS 234 S14/S15/S16/S17, APP 8, and AI transparency (T1–T4) controls. Export attestations as JSON. Feed them to your GRC platform. Answer a 72-hour notification with confidence.
Detection overhead is typically under 50 milliseconds. Your team won't notice it's there.
The AI you build, and the AI you buy.
Most regulated businesses run both kinds of AI. Guard evidences both, two different ways.
The AI you build (live proxy).
Your applications, RAG tools, agents, and product features call AI providers by API. Point those calls through Guard: one base URL, one key. Guard sees the call itself, checks it in-line, and signs the record before the response reaches your app. This is the strongest evidence Guard produces, because nothing is reconstructed after the fact.
The AI you buy (ingest).
Claude Enterprise, ChatGPT Enterprise, and Microsoft 365 Copilot publish compliance and audit feeds. Guard ingests them, maps each event to the same Australian regulatory checks, and signs it into the same evidence trail. An ingested record is only as complete as the platform's own export, and Guard always tells you which path produced which evidence.
WHAT GUARD DETECTS
The threats your current tools don't see.
Guard scans every prompt and every response. Every AI interaction is checked for sensitive data and manipulation attempts.
Watch Guard read four sample messages. Everything highlighted below is caught before it leaves your organisation.
Australian PII detection
Catches sensitive data before it leaves your organisation.
Guard scans for personally identifiable information specific to Australian regulations, not just generic patterns.
What happens when PII is found:
Configurable per policy: block the request, mask the sensitive data, or flag and log it. Every detection is recorded in the audit trail with the PII type, location, and action taken.
Guard scans prompts and the content of uploaded files (PDF, DOCX). A staff member uploading a customer document for AI summarisation is covered.
Prompt injection detection
Catches hidden instructions before the AI reads them.
Prompt injection is when someone hides instructions inside content that gets fed to an AI. The AI follows those hidden instructions, potentially leaking data or bypassing controls. Guard catches these before they reach the model.
What Guard detects:
Why this matters for compliance:
If an AI system can be tricked into bypassing controls, your information security controls are ineffective. Under CPS 234, that's a reportable control weakness. Under APP 8, it could result in an uncontrolled cross-border disclosure of personal information.
Flag, redact, or block. Your call.
Every data type in every compliance profile has one of three modes, set per team and per use case.
Flag
Records the finding and lets the call through.
Redact
Replaces the sensitive value before it leaves.
Block
Refuses the call outright.
Whichever mode you choose, the record shows which one was active on every call. The proof is the constant.
TRY IT
Verify a signed attestation in your browser.
Guard signs every attestation with ECDSA-P256. The signature verifies without Guard online, so your audit archive is regulatory evidence on its own. This demo generates a fresh keypair in your browser and signs a sample attestation.
Keypair generated fresh in your browser and never transmitted. The attestation is synthetic demo data. Production Guard uses Cloud KMS with HSM-managed keys that never touch application code.
A seven-year memory nobody can edit.
Every signed record is written to an append-only evidence vault with 7-year retention, aligned to financial services record keeping. Records can't be modified or deleted after creation, by you or by us. The trail is searchable, filterable, and exportable as JSON at any time.
Guard Connect
Guard Connect delivers evidence where your team already works. Every detection fires a signed webhook into your GRC, SIEM, or ITSM the same minute: ServiceNow, Archer, OneTrust, MetricStream, LogicGate, Diligent, or anything that accepts a webhook. Events arrive already mapped to the obligation they relate to, with 90-day replay. Included in every plan.
Every record, mapped to the obligation it serves.
Guard doesn't just log that a call happened. Each record is tagged against the specific requirement it evidences.
CPS 234
Sections 14 to 17: information security and third-party oversight.
APP 8
Cross-border disclosure of personal information.
AI transparency
The disclosure controls that commence in December 2026.
Quarterly CPS 234 and AI transparency reports generate as PDFs, built to go straight into an auditor's evidence pack or a board paper.
- Where it runs
- Google Cloud in Sydney (australia-southeast1), Melbourne failover.
- Signing
- Cloud KMS with hardware-managed keys.
- Encryption
- Keys are customer-managed (CMEK).
- Fail behaviour
- Configurable: fail-open (allow calls, log the gap) or fail-closed (block until Guard is back).
- Availability
- 99.9% uptime SLA.