Infrastructure Architecture ✓ Zero-Trust Model 4 min read

Security & Compliance

Hardened access controls, TLS 1.3 encryption, and 6-hour offsite backup restoration standards.

1. Zero-Trust Access Control

  • Mandatory MFA/2FA: Hardware-backed and app-based two-factor authentication required on all Google Workspace and production root accounts.
  • Role-Based Access Control (RBAC): Associates access client databases exclusively through named accounts limited to their active sprint scope.
  • Automated Session Expiration: Production sessions terminate automatically after inactivity to eliminate stale logins.

2. Data Encryption Standards

All client communications and database operations enforce strict end-to-end cryptographic safeguards:

  • In Transit: Enforced TLS 1.3 with HSTS (HTTP Strict Transport Security) on all endpoints.
  • At Rest: Volume-level AES-256 encryption across Frappe database volumes and private file attachments.
  • API Webhooks: Cryptographically signed HMAC SHA-256 signatures on all AppSheet and webhook payloads.
Isolated Tenancy: Each customer deployment runs on dedicated Linux user sites with segregated MariaDB database instances.

3. Backups & Disaster Recovery

Automated database snapshots are generated every 6 hours and replicated to geo-redundant, encrypted offsite object storage buckets. Scheduled restoration drills ensure our Recovery Time Objective (RTO) remains under 60 minutes.

Security Operations & Vulnerability Disclosure

To report a security finding or request our comprehensive infrastructure audit checklist, contact our SecOps team.

Email SecOps (nomeshwer@ommnomi.in)