---
title: "DataXray and Virtru technical brief"
description: "How DataXray and Virtru keep protection attached to sensitive files in closed environments, from full-content classification to TDF encryption."
url: "https://www.dataxray.io/resources/virtru-integration-technical-brief/"
language: "en-US"
---

1. [Home](https://www.dataxray.io/)
2. [Resources](https://www.dataxray.io/resources/)
3. DataXray and Virtru technical brief

Technical brief

# Persistent enforcement for sensitive files in closed environments

DataXray reads and classifies every file inside your enclave, and Virtru binds the policy into the file itself, so protection follows each file wherever it moves, with no external connectivity.

[Get your copy](https://cdn.sanity.io/files/k0xw4fsi/production/e6a3ed82d8c41cd425cd0c1aaa45cf389d3fae4a.pdf)

The DataXray and Virtru technical brief: Persistent enforcement for sensitive files in closed environments

What's in the brief

## Three steps from classification to encryption

- Every file read in full

  Read

  ### Every file read in full

  DataXray opens and reads every file on file shares and SharePoint Server, with local AI and OCR for image-based documents.
- Labels become access attributes

  Label

  ### Labels become access attributes

  Each sensitivity label is turned into OpenTDF attribute values that enforcement points can act on.
- Policy bound inside the file

  Protect

  ### Policy bound inside the file

  DataXray calls the Virtru SDK to encrypt each file to TDF, with keys in your own keystore, and writes it back where it lives.

Why this brief

## Classification without enforcement is inventory, not security

A label someone applied once, and can change, is the weak form of protection. The brief shows what the strong form takes: every file read in full, and policy bound inside it.

- ### Classification alone
- Each system keeps its own rules
- Access decided by filename and folder
- Protection lost when the file moves
- Labels applied once, then stale

- ### DataXray and Virtru
- One policy framework, enforced on every surface
- Access decided by what the file contains
- Policy bound inside the file, wherever it goes
- Re-classified and re-encrypted when rules change

## Protection that stays with the file, from first scan to every access

Get the technical brief to share with your architects and security leads.

Get your copy
