Security Features
The following control documents are available for access in our trust center:
1. Access Control Policy (EN)
Asset Management Policy (EN)
Business Continuity and Disaster Recovery Plan (EN)
Code of Conduct (EN)
Cryptography Policy (EN)
Data Management Policy (EN)
Human Resource Security Policy (EN)
Incident Response Plan (EN)
Information Security Policy (AUP) (EN)
Information Security Roles and Responsibilities (EN)
Operations Security Policy (EN)
Physical Security Policy (EN)
Risk Management Policy (EN)
Secure Development Policy (EN)
Third-Party Management Policy (EN)
Data handling
Data at rest
All datastores with customer data, in addition to S3 buckets, are encrypted at rest. Sensitive collections and tables also use row-level encryption.
This means the data is encrypted even before it hits the database so that neither physical access, nor logical access to the database, is enough to read the most sensitive information.
Data in transit
Entangl uses TLS 1.2 or higher everywhere data is transmitted over potentially insecure networks. We also use features such as HSTS (HTTP Strict Transport Security) to maximize the security of our data in transit. Server TLS keys and certificates are managed by AWS and deployed via Application Load Balancers.
Secret Managment
Encryption keys are managed via AWS Key Management System (KMS). KMS stores key material in Hardware Security Modules (HSMs), which prevents direct access by any individuals, including employees of Amazon and Entangl. The keys stored in HSMs are used for encryption and decryption via Amazon’s KMS APIs.
Application secrets are encrypted and stored securely via AWS Secrets Manager and Parameter Store, and access to these values is strictly limited.
Entangl requires vulnerability scanning at key stages of our Secure Development Lifecycle (SDLC):
Static analysis (SAST) testing of code during pull requests and on an ongoing basis
Software composition analysis (SCA) to identify known vulnerabilities in our software supply chain
Malicious dependency scanning to prevent the introduction of malware into our software supply chain
Dynamic analysis (DAST) of running applications
Network vulnerability scanning on a
period basis
External attack surface management (EASM) continuously running to discover new external-facing assets


