Plainsight

Vertrouwelijk · Publieke sector

Our data is encrypted on disk and on the network. What about while it is being processed?

Plainsight designed a data platform that processes terabytes of highly sensitive data every day and keeps it encrypted at rest, in transit and, with Databricks confidential compute, even in memory while it is being processed.

We can't name this client. The sensitivity of the data is exactly why.

  • Client confidential
  • Terabytes of data a day
  • Databricks confidential compute
  • Encrypted at rest, in transit and in use

Uitdaging

At rest and in transit wasn't enough

Processing terabytes of data every day takes strong foundations. Most data platforms protect data in two states: stored on disk and moving over the network.

For this client that was only two thirds of the answer. The data is highly sensitive, and it had to be certain that it is encrypted at every point, including the moment it is being computed on. On a normal platform, that is exactly when data sits unencrypted in memory.

Wat we deden

Privacy and security from the ground up

Security designed in from the first decision.

Privacy and data security were design inputs before anything was built. Every later choice in the architecture had to fit them.

Lake zones with their own rules.

The data lake is split into specific zones with extra policies and security rules, so the most sensitive data sits behind the tightest controls.

Encrypted while it is being processed.

Databricks confidential compute runs the workloads on hardware that keeps data encrypted in the processor's memory, so it stays protected even while it is being computed on. That closes the last gap: encrypted at rest, in transit and in use.

Our Databricks practice →

Impact

Compliance, and peace of mind

The data is encrypted in every state it can be in, which leaves zero nightmares about what could go wrong.

  • Regulatory compliance
  • Reduced risk exposure
DatabricksConfidential computeEncryption at rest, in transit and in useData lake zoningPrivacy by design

Veelgestelde vragen

What is confidential computing?

Processing data inside a hardware-protected environment where it stays encrypted in memory. It protects data in use, the one state that encryption at rest and in transit doesn't cover.

When do you need encryption in use, not just at rest and in transit?

When the data is highly sensitive or regulated, and you need to rule out that anyone with access to the underlying infrastructure could read it while it is being processed.

What are lake zones?

Separate areas in a data lake, each with its own access rules and policies. Sensitive data goes into a zone with stricter controls, so protection follows the data instead of being one setting for everything.

Why is this client not named?

Because of the same sensitivity the platform was built for. We describe the architecture, not the organisation.

Een gelijkaardig probleem bij jou?

Contacteer een expert