Aembit security posture

Using Aembit for workload credentials extends your security boundary. This section provides transparency into how Aembit protects your data, meets compliance requirements, and defends against threats.

Core security principles

• Defense in depth: Multiple layers of security controls, not single points of failure
• Least privilege: Components and services only have access they need
• Zero trust: Aembit verifies every request, regardless of source
• Transparency: Aembit documents security practices and makes them auditable

For more information about compliance, monitoring, and subprocessors, see the Aembit Trust Center.

Security architectureComponent isolation, data protection, encryption in transit and at rest, and secure communication patterns.

→

Security complianceSOC 2 Type II certification, ISO 27001 compliance, and data protection requirements.

→

Threat modelAttack vectors, trust boundaries, and the controls that mitigate risks in Aembit deployments.

→

Metadata collectionThe minimal metadata Aembit collects to operate the platform, and the analytics this documentation site collects.

→