Skip to main content
This section describes supporting system architecture using generic terms only. It frames infrastructure as a privacy-supporting control plane for Enigm products rather than as a public map of operational systems.

​
Components

  • Edge runtime
  • Secure identity layer
  • Metadata store
  • Private object storage
  • Threat intelligence pipeline
  • Controlled rollout system
  • Audit and monitoring workflows

​
Security objectives

Supporting systems should enforce least privilege, data minimization, controlled change, auditability, and integrity verification. Public infrastructure documentation focuses on security objectives, privacy boundaries, data minimization, auditability, resilience, and enterprise assurance rather than deployment topology.

​
Public Web Transport Security

Public web surfaces use a strict transport-security baseline. At a public architecture level, this includes:
  • TLS certificates for public proxied hostnames.
  • Automated certificate lifecycle management for public web names.
  • TLS 1.3 preferred transport protection.
  • TLS 1.2 compatibility restricted to approved strong cipher suites.
  • HTTP Strict Transport Security.
  • HSTS maximum age of 6 months.
  • HSTS subdomain coverage.
  • Encrypted Client Hello for compatible public web access paths.
Public web transport security protects web access paths and supported transport metadata. It does not replace Enigm App end-to-end encryption, Device Trust, protected key material, or verification workflows. Certificate authority names, public edge relationship names, non-public network identifiers, non-public domains, private routing topology, certificate automation internals, and operational deployment details remain controlled operational material.