Transport encryption
DoorAPI uses TLS 1.3 for supported platform communications.
Traffic between supported clients and DoorAPI services is protected using TLS 1.3.Encryption, controlled access, authentication, API credentials, monitoring and operational resilience form a layered security model.
DoorAPI uses TLS 1.3 for supported platform communications.
Traffic between supported clients and DoorAPI services is protected using TLS 1.3.Object storage and backups are encrypted using AES-256.
DoorAPI protects supported object storage and backup data using AES-256 encryption.MFA is available for DoorAPI users.
Users can add a second authentication factor and manage their active sessions.Customers create, scope and revoke API keys without Doorsecure intervention.
Organizations control API credentials, including multi-tenant scopes where applicable.Core DoorAPI hosting is provided from European data centers through TrueFullstaq.
Doorsecure deliberately avoids dependence on AWS for core DoorAPI hosting.Encrypted backups, geographic redundancy and recovery procedures support service continuity.
Doorsecure maintains backup and disaster recovery procedures appropriate to the platform.DoorAPI can be deployed without storing directly identifying user data.
Customers choose the identifiers and optional biometric features needed for their deployment.