Security, Privacy, and
Reliability by Design

Data Encryption In Transit and At Rest

All customer data is encrypted at rest using AES-256-GCM and in transit using TLS 1.3+. Encryption keys are managed through AWS KMS with FIPS 140-2 Level 2 validated hardware security modules. Keys are rotated on a 90-day schedule.

Role-Based Access Control

Every resource in TerraBog enforces granular, role-based permissions. Users receive the minimum access required for their function. Privilege escalation requires manager approval and is automatically logged. Access reviews run quarterly.

Infrastructure Isolation

Customer data is logically isolated at the database and storage layer using dedicated schemas and scoped credentials. Strict VPC segmentation prevents cross-tenant access. Production environments are fully isolated from staging and development.

Continuous Monitoring

All production systems are monitored 24/7 for anomalous behavior, unauthorized access attempts, and performance degradation. Automated alerting routes to the on-call security engineer within five minutes of anomaly detection.

Audit Logging

Every user action, API call, and administrative operation is recorded in append-only, tamper-evident audit logs. Logs are retained for 12 months and are exportable by Enterprise customers for SIEM integration.

Penetration Testing

TerraBog undergoes annual penetration testing by independent security firms. Critical findings are remediated within 30 days; high-severity within 60 days. Summaries of findings are available to Enterprise customers under NDA.

Multi-Region Deployment

TerraBog operates across three AWS regions: us-east-1 (primary), eu-west-1 (EU data residency option), and ap-southeast-1. Traffic is automatically routed to the nearest healthy region.

Automated Backups

Full database snapshots run every 6 hours. Incremental backups every 15 minutes. All backups are encrypted, replicated cross-region, and retained for 90 days with point-in-time restore.

Disaster Recovery

Documented disaster recovery procedures define recovery objectives by incident severity. Cross-region failover is rehearsed quarterly in a dedicated staging environment isolated from production.

Infrastructure as Code

All infrastructure is defined in version-controlled Terraform configurations. Configuration drift is detected in real time. No manual infrastructure changes are permitted in production environments.

Automated monitoring systems detect anomalies and issue alerts. All alerts are immediately routed to the on-call security engineer via PagerDuty with full context.

On-call engineer triages the alert, determines severity (P1–P4), and activates the appropriate incident response runbook. Initial severity may be upgraded as more information becomes available.

Affected systems are isolated or quarantined. Automated circuit breakers and rollback procedures are engaged to minimize blast radius and prevent further data exposure.

Affected customers notified per contractual and regulatory requirements within 24 hours of a confirmed data breach. Live status updates posted to status.terrabog.com throughout the event.

Full root cause analysis completed and remediation report published within five business days. Findings and preventive measures are reviewed with affected customers upon request.