Security Model¶

Ag2Trust is built with enterprise security requirements in mind. This document covers the security architecture and features.

Security Overview¶

┌─────────────────────────────────────────────────────────────┐
│                    Security Layers                          │
├─────────────────────────────────────────────────────────────┤
│  Edge: Cloudflare WAF, DDoS Protection                      │
├─────────────────────────────────────────────────────────────┤
│  Transport: TLS 1.2+, HTTPS everywhere                      │
├─────────────────────────────────────────────────────────────┤
│  Authentication: Firebase JWT, API Keys                     │
├─────────────────────────────────────────────────────────────┤
│  Authorization: RBAC, Resource isolation                    │
├─────────────────────────────────────────────────────────────┤
│  Data: KMS encryption, PII redaction                        │
├─────────────────────────────────────────────────────────────┤
│  Runtime: Container isolation, Network segmentation         │
└─────────────────────────────────────────────────────────────┘

Authentication¶

Dashboard Authentication¶

The Ag2Trust Dashboard uses Firebase Authentication:

• Email/password login
• Google OAuth 2.0
• Session management with secure tokens
• Automatic token refresh

API Authentication¶

The Customer API uses API key authentication:

curl -H "X-API-Key: cust_xxx" https://api.ag2trust.com/api/v1/...

API Key Security:

Authorization (RBAC)¶

Role Hierarchy¶

Owner (most privileged)
  └── Admin
      └── Member
          └── Viewer (least privileged)

Permission Matrix¶

Resource Isolation¶

All resources are scoped by organization (customer_id):

• Agents belong to organizations, not users
• Queries always filter by customer_id
• Cross-organization access is impossible

Data Encryption¶

At Rest¶

Provider Credentials (API Keys):

┌─────────────────────────────────────────────┐
│         KMS Envelope Encryption              │
│                                              │
│  1. Generate random DEK (AES-256)           │
│  2. Encrypt credential with DEK             │
│  3. Wrap DEK with KMS master key            │
│  4. Store: encrypted_credential + wrapped_DEK│
└─────────────────────────────────────────────┘

Database:

• PostgreSQL with encrypted connections (SSL required)
• Managed database with automatic encryption at rest

In Transit¶

PII Protection¶

Ag2Trust automatically redacts PII in all content—both inbound (user messages) and outbound (agent responses).

Bidirectional Redaction¶

Detected PII Types¶

• Email addresses
• Phone numbers
• US Social Security Numbers
• Credit card numbers
• IP addresses
• Names (when detectable)
• Dates of birth
• Financial account numbers

Fail Mode Behavior¶

PII redaction has different fail modes depending on direction:

Implementation¶

Ag2Trust uses Microsoft Presidio for PII detection and redaction. Redaction is centralized in a dedicated PII service—no other component performs PII detection.

Container Security¶

Agent Isolation¶

Each agent runs in an isolated Docker container:

Security measures:
  - Non-root user execution
  - Read-only /app directory
  - Write access only to /workspace
  - Resource limits (memory, CPU)
  - No privileged capabilities

Network Segmentation¶

┌─────────────────────────────────────────┐
│           ag2trust-internal             │
│  (Redis, PostgreSQL - no internet)      │
├─────────────────────────────────────────┤
│           ag2trust-public               │
│  (LLM API access only)                  │
└─────────────────────────────────────────┘

Agents are dual-homed:
- Internal: Redis messaging
- Public: LLM API calls only

Rate Limiting¶

Defense-in-depth rate limiting:

Audit Logging¶

Agent Audit Logs¶

All agent interactions are logged:

{
  "timestamp": "2025-01-15T10:30:00Z",
  "agent_id": "uuid",
  "customer_id": "uuid",
  "event_type": "message",
  "content": "[REDACTED]",
  "tokens_used": 150,
  "model": "gpt-4o"
}

Note: Content is PII-redacted before storage.

Compliance Audit Logs¶

System events for compliance:

{
  "timestamp": "2025-01-15T10:30:00Z",
  "event_type": "user_login",
  "actor_id": "user-uuid",
  "customer_id": "uuid",
  "ip_address": "[REDACTED]",
  "details": {...}
}

Retention¶

Configure retention in Settings > Data Retention.

GDPR posture (avoid over-claims)¶

Ag2Trust includes controls that support GDPR-aligned operations (retention controls, audit logging, encryption), but this document should avoid blanket claims like “GDPR compliant” unless you can point to concrete legal/process artifacts.

Data Subject Rights¶

Data Retention¶

• Configurable retention periods (30-365 days)
• Automatic cleanup job runs daily
• Compliance audit logs retained for 7 years

Data Processing¶

• All data processed within your chosen region
• No data sharing with third parties (except LLM providers)
• LLM providers receive only message content (no PII metadata)

Security Best Practices¶

For Administrators¶

1. Use strong passwords and unique credentials
2. Rotate API keys regularly
3. Limit user roles to minimum necessary
4. Monitor audit logs for unusual activity
5. Configure retention per compliance requirements

For Developers¶

1. Never expose API keys in client-side code
2. Use environment variables for credentials
3. Validate webhook signatures for authenticity
4. Implement retry logic with exponential backoff
5. Handle rate limits gracefully

For System Prompts¶

# Good: Set boundaries
You must never:
- Share internal information
- Execute harmful commands
- Bypass safety guidelines

# Avoid: No boundaries
You are a helpful assistant (no constraints)

Incident Response¶

Reporting Security Issues¶

If you discover a security vulnerability:

1. Do not disclose publicly
2. Email: security@ag2trust.com
3. Include detailed description
4. We'll respond within 24 hours

See our Security Disclosure policy for scope and safe-harbor guidance.

Security Updates¶

• Critical patches deployed immediately
• Security advisories published as needed
• Customers notified of relevant issues

Compliance¶

Current (technical controls)¶

• PII redaction in audit logs
• Configurable data retention
• Audit trail for actions

Roadmap¶

• SOC 2 Type II (planned)
• HIPAA BAA (planned)
• ISO 27001 (planned)

Security Architecture Diagram¶

                    Internet
                        │
                        ▼
              ┌─────────────────┐
              │   Cloudflare    │
              │  WAF + DDoS     │
              └────────┬────────┘
                       │ TLS
                       ▼
              ┌─────────────────┐
              │     Nginx       │
              │  Rate Limiting  │
              └────────┬────────┘
                       │
         ┌─────────────┼─────────────┐
         │             │             │
         ▼             ▼             ▼
    ┌─────────┐  ┌─────────┐  ┌─────────┐
    │ Backend │  │Customer │  │  Admin  │
    │   API   │  │   API   │  │  Panel  │
    └────┬────┘  └────┬────┘  └────┬────┘
         │            │            │
         └─────────┬──┴────────────┘
                   │
    ┌──────────────┼──────────────┐
    │              │              │
    ▼              ▼              ▼
┌────────┐    ┌─────────┐    ┌─────────┐
│ Redis  │    │Postgres │    │   KMS   │
│internal│    │  (SSL)  │    │(encrypt)│
└────────┘    └─────────┘    └─────────┘
    │
    ▼
┌─────────────────────────────────────┐
│         Agent Containers            │
│  (isolated, non-root, rate-limited) │
└─────────────────────────────────────┘