We use the latest versions of Encryption TLS v1.3
Clusters are deployed behind proxies and are not visible to internet scanning. Transport Layer Security (TLS) encrypted communication from the Internet is provided in the default configuration (version 1.3). Accept Mission nodes run in isolated containers, configured according to the principle of least privilege, and with restrictions on system calls and allowed root operations. Accept Mission nodes communicate using TLS. Cluster data is encrypted at rest. API access is limited to Accept Mission APIs, and no remote access to the instance or container at the Linux level is allowed. Containers have no means of setting up communication with containers from another cluster.
We do not perform Internet-based penetration testing against production Accept Mission offerings, however, we do use third parties to perform application security assessments against the Accept Mission software components used to deliver these services.
Data into servers
All the incoming connections towards our servers are required to be encrypted with industry standard SSL encryption. Latest SSL Labs report can be found here.
Data between our servers
Connections between our servers (i.e. web servers <-> databases) are encrypted via TLS v1.3 with a AES-256bit encryption method. Secrets such as database password, API secrets are encrypted using the same AES-256bit method.
Data out of our servers
Once the request is processed, the response is sent back using the same HTTPs SSL encrypted connection.
Read all of encryption in our Security Overview page