The question isn't if they get in. It's what they leave with.

Shield applies persistent, field-level protection to sensitive data across your estate, so a breach yields nothing readable. Encryption stays with the file wherever it goes. Your keys stay in your environment.

SharePoint · LegalSHIELDED
Account compromisedUnknown device · 09:42 · Mass download
YOUR PERIMETER
root@exfil:~/sharepoint_legalFiles taken 2.1K31.8K96.5KReadable 0
claims_review.docx
hr_records.xlsx
counsel_memo.pdf
downloading…
claims_review.docxEncrypted
Protected content
hr_records.xlsxTokenized
EmployeeProtected
SSNProtected
SalaryProtected
counsel_memo.pdfRedacted
Protected content
See it work

Watch protection applied to a live document

Shield protects the sensitive bit inside the file, whether it's the word, the field, the paragraph. Run it and watch what an attacker would actually get.

app.confidencial.io/shield
demo
Shield Demo
1
Build policy
2
Apply protection
3
View by identity
Step 1 — Define your protection policy
PHI / Patient data
SSNs / Policy numbers
Financial figures
Privileged communications
Step 2 — Shield applying policy
Q3_Claims_Analysis.docx — scanning
The following covers claims submitted between July and September 2026. Total claim volume was 4,847, with an average settlement of $12,400...
Initializing policy engine... 0%
Step 3 — View protected document by identity
📄 Q3_Claims_Analysis.docx Shield Active
Viewing as: Clinical Team
Encrypted
Tokenized
Redacted
Switch identity
The problem with classification

A label is not a control.

Most teams have classified their data. They have sensitivity labels, a posture score, a dashboard full of green. What they don't have is any assurance the data those labels point to is actually protected.

LABEL ALONE

What a sensitivity label gives you

A file marked "Highly Confidential" in metadata, a ticket routed and queued and approved, and content still sitting in plaintext, exactly as exposed as it was the day it was tagged.

Sensitivity-Labels.csv
Highly Confidential1,841
Confidential284
PHI labeled619
Protection appliedNone
opens ticket ↓
#4821Route to InfoSec47 days
#4822Awaiting IT review47 days
#4823Pending approval47 days
Data still in plaintext ↑
WITH SHIELD

What Shield changes

Shield reads the same label and acts on it. Classification becomes the trigger for cryptographic protection, applied at the field level, in the same platform, with no ticket in between.

Reads the label
Confidencial Discover, Purview, Varonis, BigID
Applies selective encryption
WORDFIELDPARAGRAPHPAGE
Protection travels with the file
Revocable · identity-bound · persistent
Protected · no ticket · no wait
How Shield works

From classification signal to protected estate

Connect your sources, read the classification already in your environment, apply protection at scale, and keep control of every key, with no agents, and no re-tagging.

1

Connect

Point Shield at S3, SharePoint, OneDrive, Azure Blob, Box, and on-prem servers. Agentless for most cloud sources.

2

Read classification

Whether it's identified or ingested,  Discover is Shield's native analysis engine, scanning and classifying sensitive content directly, or reading existing labels from Purview, Varonis, or BigID. Either path feeds the same policy engine.

3

Apply at scale

Encrypt, tokenize, redact, delete, or archive across the full estate, from terabyte to petabyte, at the granularity each field needs.

4

Keep control

Revoke one person's access remotely without re-encrypting anything. Keys stay in your environment. Confidencial never sees plaintext.

Classified data from
Discover findings
Purview / Varonis
S3 / Azure / GCS
SharePoint / Box
Shield
Any data object
Word
Field
Cell
Paragraph
Page
Any protection
Encrypt
Tokenize
Redact
What you get
Policy-driven and automatic
Your policies apply protection as data is classified. No manual steps.
Protection travels
Encryption stays with the file wherever it moves.
Your keys, your environment
No plaintext leaves your environment.
Capabilities

What Shield does to your data

It protects the sensitive element, not the whole file, so data stays usable, collaboration keeps working, and a breach produces nothing an attacker can read.

targeted protection

Protect the word, not the file

Protect at the word, field, paragraph, page, or full-document level. Original format is preserved, which means a Word doc still opens as Word.

Policy engine

Five actions, applied automatically

Encrypt, tokenize, redact, delete, or archive, all chosen per data type, sensitivity, and who needs access. One policy engine decides.

Scale

Terabyte-to-petabyte processing

Protects the full data estate. No per-GB caps, a 1TB job runs in roughly 13 hours.

Key control

Customer-controlled keys, always

Your KMS, your environment. Keys are identity-bound through your IDP, so you can revoke one person's access without
re-encrypting anything.

Integration

Reads your DSPM labels natively

Turns Purview, Varonis, and BigID sensitivity labels into enforcement triggers. Add Discover for native classification.

Post-quantum

PQC-ready by architecture

Built for a seamless transition to NIST post-quantum standards. The data you encrypt today stays protected, no re-protecting the estate later.

Shield in the wild

The moments where enforcement changes the outcome

Four situations where a label leaves you exposed, and where Shield changes what an attacker, an auditor, or an acquirer actually finds.

Insider threat

A departing employee downloads files on the way out. Every one is readable.

The account was authorized, so DLP stayed quiet. Encryption at rest protected the bucket, not the file.

With Shield

Sensitive fields stay encrypted on their laptop. Access is revoked by identity, with no device touch.

DSPM upgrade

Your files carry Purview labels. None of them are actually protected.

Every dashboard is green, but a label is metadata, not a control. Labels don't encrypt.

With Shield

Shield reads the labels and encrypts the files they point to. No re-tagging.

AI governance

Analytics wants to train on clinical data. The PHI can't enter the pipeline.

The data has real value, but PHI can't touch a model without HIPAA exposure. The usual answer is don't use it.

With Shield

PHI is encrypted at the word level. The model trains on everything else.

Cloud migration

Sensitive data can't move to the cloud. No one trusts the destination.

On-prem costs keep rising and AI projects are waiting. Every migration stalls on what happens to PHI, IP and financials in a cloud bucket.

With Shield

Protect the data before it moves. Field-level encryption travels with it.

Why teams trust Confidencial

Built for the environments that matter

40+

File types protected, original format preserved

2026

Data Solution of the Year in Legal, Data Breakthrough Awards

DoD

Tradewinds Marketplace Awardable

HIPAA Compliant
PCI DSS Compliant
AFWERX STTR Phase II
Customer-controlled keys
Connects to your existing environment
AWS S3Azure BlobOneDriveSharePointBoxMicrosoft PurviewMicrosoft EntraOkta
Questions about Shield

What security teams ask us first

We already have Microsoft Purview. Why do we need Shield?

Purview classifies and labels your data — it doesn't protect it. A sensitivity label is metadata: it tells you a file is sensitive, but it doesn't encrypt the content. Shield reads your Purview labels and applies cryptographic protection to the files they identify, turning classification into actual enforcement.

How is selective encryption different from full-file encryption?

Full-file encryption makes the entire document unusable unless decrypted in full. Selective encryption protects only the sensitive fields, words, or paragraphs inside the file — the rest stays readable, usable for collaboration, and processable by AI. Protection at the element level, not the file level.

Does Shield break our AI workflows?

The opposite — Shield is what makes AI workflows safe to run. Because protection is field-level, AI systems process the non-sensitive content freely and encounter ciphertext only where sensitive fields appear. You get the analytical value of your unstructured data without feeding PHI or IP into an LLM.

Who controls the encryption keys?

You do. Confidencial never sees plaintext. Keys are managed in your environment — bring your own KMS or use Shield's built-in key server. Access is identity-bound through your existing IDP, so revoking one person's access is an IDP group change, not a re-encryption job.

Does Shield work if we don't have Discover yet?

Yes. Shield ingests classification signals from any DSPM you already have — Purview, Varonis, BigID, Laminar — or you define protection policies directly by data type and regulatory category. Discover adds native classification if you want discovery and enforcement from one platform, but Shield operates independently.

Act on what you already found

Stop reporting exposure. Start closing it.

Shield connects to your environment in days. No re-architecture. Just persistent protection for the sensitive data your classification tools have already found.