SECURITY & TRUST

Your data never leaves your perimeter

e6data deploys into your own cloud account and runs where your tables live. Zero data movement - your existing governance and residency controls stay in force.

SOC 2 Type II
Audited controls, independently attested
ISO 27001
Certified information-security management
GDPR
Data residency and processing rights
THE ARCHITECTURE

Your data stays in your account

The architecture separates a Data Plane from a Control Plane, so your data never leaves your environment.

DATA PLANE · YOUR AWS ACCOUNT

Holds the actual data and the query engine. It runs entirely inside your account.

CONTROL PLANE · e6data-MANAGED

Receives only metadata and metrics for orchestration. Never your data.

DATA PLANE · YOUR AWS ACCOUNTYour dataS3 buckets · Glue cataloge6data query engineisolated K8s namespaceread-only IAM · MFAaudit logs · CloudTrailCONTROLPLANEmetadata+ metricsonlyneveryour data never crosses this line
HOW IT IS SECURED

Least privilege, end to end

Customer-owned deployment

The engine deploys into an isolated Kubernetes namespace inside your own AWS EKS cluster, via Terraform scripts that are public and auditable.

Least-privilege access

Read-only access to the S3 buckets and Glue catalog you specify, plus a separate bucket for schema metadata. Nothing more.

IAM, scoped per service

Permissions are granted through IAM OIDC for a specific service account. Granular S3 controls, and MFA required for every deployment.

No e6data personnel access

Employees have no access to the production Control Plane and no pathway to your Data Plane. All inter-plane traffic is application-to-application.

Full audit visibility

Kubernetes audit and authenticator logs, S3 access logging on by default, CloudTrail for IAM and STS, and IP allowlisting via EKS authorized networks.

Residency stays in force

e6data runs where your tables already live, so your existing governance and data-residency controls apply unchanged.

WHAT LEAVES THE DATA PLANE

Metadata, never data

Only operational metadata is sent to the Control Plane. Query Editor results stream to your browser through the Control Plane - they are not retained on e6data servers, not written to disk, and inaccessible to employees.

  • Infrastructure and cluster metrics (CPU, memory, I/O)
  • Query counts and durations - SQL text masked, hashes only
  • Schema information (table and column names)
  • User identity, for query attribution

Read the full detail

The complete security documentation - including the auditable Terraform and deployment model - is in our docs.

Security documentation →privacy@e6data.com