Skip to main content
PromptGuard is built with enterprise security requirements in mind. This page outlines our security practices, compliance status, and data handling policies.

At a glance

For security teams evaluating PromptGuard, the three things that usually matter most:
  1. What we do with your data — pass-through architecture: we scan prompts and responses in real time and don’t store prompt content or train on it. Your LLM provider keys stay with you. (See Data Handling.)
  2. Proof for auditors — every security decision is recorded in a tamper-evident, hash-chained audit log with event ID, threat type, confidence, and timestamp.
  3. Where we stand on frameworks — summarized in the table below.
“Compliant” vs “Aligned”: Compliant means we meet the requirement (with a DPA or independent attestation where applicable). Aligned means PromptGuard provides the technical controls a framework requires, but formal third-party certification is still in progress or out of scope. We don’t claim certifications we don’t hold.

Security Certifications

“Aligned” means PromptGuard provides the technical controls that satisfy the framework’s requirements. Formal certification (where applicable) requires third-party audit. For enterprise customers requiring specific compliance certifications, contact sales@promptguard.co to discuss your requirements.

EU AI Act Alignment

The EU AI Act (Regulation 2024/1689) imposes requirements on high-risk AI systems, enforceable from August 2, 2026. PromptGuard provides technical controls that map to each requirement:

ISO/IEC 42001 Alignment

ISO/IEC 42001:2023 is the international standard for AI Management Systems. PromptGuard’s controls map to its Annex A requirements:

Data Handling

What Data We Process

Data Flow

Pass-Through Architecture

PromptGuard operates as a pass-through proxy:
  • Prompts and responses are scanned in memory
  • Content is not stored after processing
  • Only metadata (timestamps, threat types, confidence scores) is logged
  • Your data never touches disk in unencrypted form
Security event logs may contain sanitized snippets of blocked content for debugging purposes. These are automatically purged after the retention period. Enterprise customers can disable content logging entirely.

Infrastructure Security

Cloud Infrastructure

Encryption

Network Security

  • All endpoints require HTTPS
  • Cloud Armor per-IP anti-abuse rate limiting at the network edge
  • No public SSH access to infrastructure
  • VPC-based isolation between services
  • Private database connections (no public IP)

Access Control

Authentication Methods

API Key Security

  • Keys are hashed with Argon2id before storage
  • Only the prefix (pg_live_xxxxxxxx...) is stored in plain text
  • Full key shown only once at creation
  • Keys can be rotated without downtime
  • Project-scoped API keys (no per-key permission types; tier gating via subscription)

Role-Based Access (Enterprise)

Audit Logging

What’s Logged

Accessing Audit Logs

  1. Go to Dashboard → Settings → Audit Logs
  2. Filter by date range, event type, or user
  3. Export as CSV or JSON

Log Export (Enterprise)

Enterprise customers can configure:
  • SIEM Integration: Stream logs to Splunk, Datadog, etc.
  • S3 Export: Daily log exports to your bucket
  • Webhook: Real-time log forwarding

Incident Response

Security Incident Process

  1. Detection: Automated monitoring + manual review
  2. Containment: Isolate affected systems
  3. Investigation: Root cause analysis
  4. Notification: Affected customers notified within 72 hours
  5. Remediation: Fix deployed, post-mortem published

Reporting Security Issues

Found a vulnerability? Contact us:

Data Residency

Current Regions

Planned Regions

Enterprise customers requiring specific data residency can request dedicated deployment in their preferred region.

Vendor Security

Subprocessors

LLM Providers

PromptGuard forwards requests to your chosen LLM provider. We do not store data sent to:
  • OpenAI
  • Anthropic
  • Google AI
  • Cohere
  • AWS Bedrock
  • Azure OpenAI
Your data handling agreement is with each LLM provider directly.

AI Agent Governance

PromptGuard provides four governance capabilities for AI agents operating in production:

Agent Identity — issuance and rotation (Partial)

Register an agent and it receives a unique pgag_ secret, stored bcrypt-hashed, shown once, and rotatable. Exactly one credential per agent is active at a time, enforced by a database constraint.
  • POST /api/v1/agent/register — Register and receive a one-time credential
  • POST /api/v1/agent/{agent_id}/rotate-credential — Revoke old credential, issue new one
PromptGuard does not currently verify a presented credential at request time; agent IDs on tool-call and guard requests remain self-asserted. Issuing and rotating a credential is the whole of the implemented control. Audit entries record the agent ID the caller asserted, and governance reports do not report credential-verification counts. Treat this control as Partial in a control matrix. If you need enforced agent identity today, bind it at your own network or gateway layer.

Behavioral Drift Detection

After an agent accumulates sufficient observations, PromptGuard freezes a behavioral baseline capturing the agent’s normal tool-usage distribution. Every subsequent request is compared against this baseline using Jensen-Shannon divergence. If the distribution shifts beyond the configured threshold, a BEHAVIORAL_DRIFT alert fires.

Tamper-Evident Audit Trail

Every audit event’s SHA-256 hash covers every field the event stores and incorporates the previous event’s hash in your organization’s chain, forming a cryptographic chain that every PromptGuard instance extends in sequence. If any event is modified or deleted, the chain breaks and verification fails. Use POST /dashboard/audit-log/verify-chain to verify the integrity of your own events over any time range; the evidence package’s Audit Chain Integrity control (CC7.4) reports the chain walk.
If you exported an evidence package before 3 September 2026, re-export it. Two things changed:
  • Audit events written before 27 August 2026 were signed over eight of their fields (hash version 1). Events since then are signed over every stored field (hash version 2). Version-1 events are never re-signed and are reported as unverifiable — not intact, not tampered. Every package now states v1_count, v2_count and cutover_at so you can see which rows carry which signature.
  • Earlier packages could show CC7.4 as compliant over a period in which no events were verified. A period with nothing to verify now reports insufficient-data with the narrative “No events in window; chain not evaluated”, and a package is not produced at all if the audit log cannot be read.
  • A row whose category, severity or outcome predates a schema narrowing can no longer be decoded, and is reported rather than treated as a read failure: it is excluded from verified_count and counted in malformed_count, with the affected event IDs listed (up to 20) in malformed_events. It does not make the chain around it look broken.

Governance Reports

Generate auditor-facing narrative reports covering all four governance capabilities:
The report includes sections for agent identity verification rates, behavioral drift alerts, audit chain integrity status, security decision summaries, and a chronological incident timeline.

Enterprise Security Features

Available on the Enterprise tier:

Security Questionnaire

Need to complete a vendor security assessment? We provide:
  • CAIQ (Consensus Assessment Initiative Questionnaire)
  • SIG Lite (Standardized Information Gathering)
  • Custom Questionnaires (for Enterprise customers)
Contact security@promptguard.co for these documents.

Responsible Disclosure

We appreciate security researchers who help keep PromptGuard secure:
  1. Report the issue to security@promptguard.co
  2. Do not publicly disclose until we’ve addressed it
  3. Provide steps to reproduce
  4. Allow reasonable time for remediation (90 days)

Next Steps

Security Overview

Learn about threat detection

Audit Logs

Monitor user activity

Enterprise

See Enterprise features

Contact Sales

Discuss your requirements