Platform.sh User Documentation

Security and data privacy

Upsun Beta

Access our newest offering - Upsun!

Get your free trial by clicking the link below.

Get your Upsun free trial

Platform.sh is committed to protecting your data and keeping your site safe, secure, and available at all times. All Dedicated projects are isolated and their data is fully encrypted.

Should a security breach occur, Platform.sh follows a strict security incident handling procedure to deal with the issue as promptly and efficiently as possible.

Project isolation Anchor to this heading

All Dedicated clusters are single-tenant. The three hosts are exclusively used by a single customer and each cluster is launched into its own isolated network (VPC on AWS, equivalent on other providers).

The network is behind a firewall for incoming connections. Only ports 22 (SSH), 80 (HTTP), and 443 (HTTPS) are opened to incoming traffic.

There are no exceptions for this rule, so any incoming web service requests, ETL jobs, or otherwise need to transact over one of these protocols.

Outgoing TCP traffic isn’t behind a firewall. Outgoing UDP traffic is disallowed.

For containers to be allowed to connect to each other, the following requirement must be met:

  • The containers must live in the same environment.
  • You need to define an explicit relationship between the containers in your app configuration.

Security incident handling procedure Anchor to this heading

Should Platform.sh become aware of a security incident β€” such as an active or past hacking attempt, virus or worm, or data breach β€” senior personnel, including the CTO, are promptly notified.

The security incident procedure includes the following steps:

  1. Isolating the affected systems.
  2. Collecting forensic evidence for later analysis, including a byte-for-byte copy of the affected systems.
  3. Restoring normal operations.

Once normal service is restored, a root cause analysis is performed to determine exactly what happened. Upon request, Platform.sh can provide you with a Reason for Outage report that summarizes the incident, cause, and steps taken.

Platform.sh cooperates with relevant law enforcement, and informs law enforcement in the event of an attempted malicious intrusion. Depending on the type of incident, the root cause analysis may be conducted by law enforcement rather than Platform.sh personnel.

Platform.sh endeavors to notify affected customers within 24 hours in case of a personal data breach and 72 hours in case of a project data breach.

Under the European General Data Protection Regulation (GPDR), Platform.sh is required to notify its supervising authority within 72 hours of a discovered breach that may result in risk to the rights and freedoms of individuals. The supervising authority for Platform.sh is the French Commission Nationale de l’Informatique et des LibertΓ©s.

Audit trail Anchor to this heading

As part of the security incident process, Platform.sh records a log of all steps taken to identify, isolate, and respond to the incident. This log may include:

  • A byte-for-byte copy of the affected systems
  • How the intrusion was detected
  • The steps taken to contain the intrusion
  • Any contact with third parties, including law enforcement
  • Any conclusions reached regarding the root cause

Encryption Anchor to this heading

AWS Anchor to this heading

AWS EBS Volumes are encrypted on Platform.sh, which means Dedicated Gen 3 and Dedicated Gen 2 sites are fully encrypted. Keys are managed by the AWS Key Management Service. AWS automatically rotates these keys every three years. In some cases, temporary storage (such as swap) is stored on unencrypted local storage volumes.

Azure Anchor to this heading

By default, data is encrypted using Microsoft-Managed Keys for Azure Blobs, Tables, Files, and Queues.

GCP Anchor to this heading

Data is encrypted using default encryption at rest.

Is this page helpful?