<img src="https://ad.doubleclick.net/ddm/activity/src=11631230;type=pagevw0;cat=pw_allpg;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=${GDPR};gdpr_consent=${GDPR_CONSENT_755};ord=1;num=1?" width="1" height="1" alt="">

AWS S3

Object-level data protection for the world's most trusted cloud storage infrastructure

Amazon S3 is the object storage standard. Before "cloud-native" was a design principle, S3 defined what scalable, durable, programmatic object storage looks like — and it became the API that every storage provider since has emulated. Today, S3 runs the data infrastructure for enterprises, defense agencies, and government programs worldwide, delivering eleven nines of durability, automatic storage tiering, and cross-region replication for resilience. For organizations that have built their data infrastructure on AWS, S3 is not a component they're evaluating — it's the foundation they're extending.

AWS S3 + Virtru Data Security Platform

Identity and Access Management controls who can call S3 APIs, which accounts can access which buckets, and what operations users are permitted to perform. But IAM's jurisdiction ends at the S3 API endpoint. The moment an object is retrieved — downloaded to a workstation, shared with a contractor, replicated to another region or account — the data travels beyond IAM's reach. The Virtru Data Security Platform closes that gap. Each object is TDF-encrypted with an embedded ABAC policy at write time, delivering cryptographic, per-object governance that persists wherever the data moves — across regions, accounts, or outside AWS entirely.

This eliminates the bucket proliferation that organizations create to approximate access control. Without object-level governance, teams stand up separate buckets per project, sensitivity tier, or access group — each compounding policy management, access reviews, and operational overhead. With the Data Security Platform, a single S3 bucket holds objects with entirely different governance profiles. Multiple users can share the same bucket, however, actions on the objects are strictly limited to each individual's current data entitlements, enforced by the data itself.

S3's replication capabilities make the case concrete. Cross-Region Replication is a standard resilience pattern, but when data lands in a secondary region or account, new bucket policies must be applied and maintained separately — and governance inevitably drifts. With TDF-encrypted objects, every replica enforces the same entitlements as the source, in any region, under any account, with no separate policy management required. With the Data Security Platform's proxy capabilities for S3, applications continue reading and writing data with no application logic rewrite required.

How It Works

  1. Upload - Files are written to S3 through existing application workflows. The platform's secure object connector operates as a transparent S3-compatible proxy — no application code changes required.
  1. Encrypt - The platform's secure object connector wraps each object in TDF at write time, embedding access policy attributes. The encrypted object is stored in S3. The Key Access Service (KAS) holds the wrapped key.
  2. Access request - When a user or service retrieves an object, the KAS evaluates the requester's current entitlements against the embedded policy in real time.
  3. Authorize or deny - If the policy is satisfied, the KAS returns the key and the object is decrypted for the requester. If not — or if access has been revoked — the request is denied. The encrypted object remains in S3 unchanged.
  4. Audit - Every access attempt — authorized or denied — is logged with the requester identity, timestamp, and policy decision, creating the evidence chain compliance programs require.