Encryption

Polyaxon employs robust encryption methods to protect your data both while it's being transferred and while it's stored.

This page describes the encryption practices for Polyaxon Cloud. For self-hosted deployments, please refer to the Self-hosting Guide.

Data Flow

Data into System

Polyaxon provides UI, CLI, Clients, and SDKs that securely send events and metadata to the API, which processes and stores the metadata.

Data through System

Metadata is sent securely to Polyaxon via TLS to an HTTPS endpoint. All data is AES-256bit encrypted, both in transit and at rest.

Data out of System

Once the metadata is processed, it can then be accessed via Polyaxon's user interface, CLI, and REST APIs.

Encryption in Transit

All data transferred between your applications, the Polyaxon SDKs, and the Polyaxon server is encrypted using TLS 1.2 (Transport Layer Security). Polyaxon exclusively sends data over HTTPS transport layer security (TLS) encrypted connections for additional security as data transits to and from the application. This ensures that data is protected from eavesdropping or tampering during transmission.

Encryption at Rest

All data in Polyaxon servers is encrypted at rest using AES-256, a strong industry-standard encryption algorithm. Google Cloud Platform stores and manages data cryptography keys in its redundant and globally distributed Key Management Service. So, if an intruder were ever able to access any of the physical storage devices, the Polyaxon data contained therein would still be impossible to decrypt without the keys, rendering the information a useless jumble of random characters.

Encryption at rest also enables continuity measures like backup and infrastructure management without compromising data security and privacy.

This applies to data stored in:

Contact

For questions regarding encryption practices, please contact [email protected].

---