Head-to-head · updated 13 September 2026

DataShield vs Amazon Macie: who governs the data after Macie finds it?

Amazon Macie is good at one job and honest about it. Turn it on, and it scans your S3 buckets for PII, PHI, card data, and AWS credentials, then hands you a finding with a severity score. The price is printed on a public page: $1 per GB inspected. If you run on AWS, you should probably have it on. We tell prospects that.

Then the ticket lands on someone's desk. Macie says bucket X holds social security numbers. Your RAG pipeline reads bucket X. Now what? That question is ours. Datasets are tokenized at ingest; agents query tokenized data over MCP; detokenization is a privileged, audited operation. Every governed tool call is checked against the agent's current authority, and each decision is sealed into a hash chain you can verify yourself.

Get free Demo Center access Get an instant quote

The short version

Pick DataShield when

Agents or copilots read the buckets Macie just flagged, and you need the access itself governed, not just reported. How Auth does it.
Your sensitive data also sits in Postgres, Snowflake, a file share, or another cloud. Macie only looks at S3 general purpose buckets.
An examiner will ask you to prove an access log wasn't edited. Macie keeps findings for 90 days and they are findings, not evidence of who did what. Run the verifier.
You want to pull an agent's authority mid-session and have the next tool call fail, not wait for a token to expire.

Pick Amazon Macie when

You need to find sensitive data in S3 and you have no idea where it is. This is the job Macie was built for, and it does it well.
You are all-in on AWS and want zero new vendors. Macie is a toggle in a console you already pay for.
You want findings flowing straight into Security Hub CSPM and EventBridge so a Lambda can act on them.
You want to model the cost before you commit. $1 per GB inspected, $0.10 per bucket per month. That is published, and most of this market is not.

Bottom line: keep Macie. It finds the data. It does not tokenize it, decide who may query it, or keep proof that the decision was honoured. That is the layer we sell, and it works on data Macie can't see.

Feature by feature: sensitive data discovery versus agent data governance

Competitor cells describe what Amazon Macie's public site and AWS documentation say as of the date above. If we've mischaracterised something, email support@myorg.ai and we'll correct it, credited.

What matters	DataShield	Amazon Macie	Edge
Sensitive data discovery	We scan, profile and classify a live PostgreSQL source in place, with no rows leaving it. Columns get labelled against 129 field classes covering PII, PHI, financial data and secrets, and the catalog carries a business glossary, typed lineage and stewardship queues. That is PostgreSQL today, not your whole estate: SaaS apps, cloud stores and endpoints are not ours, and the other database providers are declared but not built yet.	Automated and targeted discovery across the S3 estate, with managed data identifiers, custom regex identifiers, allow lists, sampling, and per-bucket sensitivity scores.	◇
Coverage beyond S3	Source-agnostic. Datasets arrive from databases, warehouses, files, and APIs, on any cloud or none.	Amazon S3 general purpose buckets. AWS documentation describes no coverage for RDS, DynamoDB, Redshift, SaaS apps, or non-AWS data.	◆
Tokenization and data handling	Datasets are tokenized at ingest; agents query tokenized data over MCP; detokenization is a privileged, audited operation. Tokens are deterministic, join-preserving, and vault-reversible.	Discovery and reporting. Macie generates a finding for you to review and remediate. It does not tokenize, vault, or rewrite the data it finds.	◆
Agent authorization	Every governed tool call passes a scope ceiling, a declared authority tier, and a revocation re-check before dispatch. Revocation lands mid-session.	No agent identity or per-call authorization. Access control stays with IAM and S3 bucket policy. AWS's agent answer is Bedrock Guardrails, and its PII filter does not evaluate tool call arguments or tool results.	◆
Audit evidence	SHA-256 hash chain with Ed25519-signed checkpoints that are themselves chained. Verification names the failure: tampering, insertion, deletion, or truncation. Public verifier.	Findings are stored for 90 days, then published onward via EventBridge if you build that pipeline. No cryptographic tamper evidence is described.	◆
Break-glass	Scoped, time-boxed emergency access for agents. It auto-revokes and can't be quietly removed from the log.	Not offered. Not the product's job.	◆
GDPR erasure	Crypto-shred of per-subject key material plus ISO 27560 consent receipts. The audit chain still verifies after erasure.	No erasure mechanism. Macie reports where a subject's data sits; deleting it is your job in S3.	◆
MCP and agents	Native MCP endpoints on Auth, Ontology, and Lighthouse. MCP tool tokens with scope ceilings, plus per-call metering attributed to the agent.	No MCP surface and no agent story. The Macie homepage does not mention AI agents at all.	◆
Workflow integration	MCP, REST, and API keys with per-tool tier gating on the Ontology surface; Auth issues MCP tool tokens with scope ceilings. No native Security Hub or EventBridge integration today.	Findings publish automatically to EventBridge and optionally to AWS Security Hub CSPM, which is a genuinely clean path to a Lambda or a SIEM.	◇
Deployment	Self-hosted in your own cloud or data center, or on a dedicated single-tenant server we operate. Your keys.	AWS-managed service, available in most AWS Regions. It runs only inside AWS.	◆
Maturity signals	Auth, Guardian and Lighthouse are live in production (Guardian and Lighthouse since April 2026). SOC 2 not yet certified, and we say so.	An AWS service since 2017, re-architected since, with automated discovery shipped in 2022. It inherits the AWS compliance estate. We are not going to pretend to match that.	◇
Pricing	Published model, scoped instant quote, no sales wall.	Published per-unit pricing: $1 per GB inspected, $0.01 per 100,000 objects monitored, $0.10 per bucket per month. Plus a 30-day trial.	◈

◆ DataShield leads◇ Amazon Macie leads◈ comparable

Amazon Macie claims are drawn from aws.amazon.com/macie, the Macie user guide, and the Amazon Bedrock Guardrails documentation, last checked 13 September 2026. We link them below rather than paraphrase from memory.

Three things you get here that you won't get from a sensitive data scanner

A decision, not a ticket

A finding tells you a bucket holds SSNs. It doesn't stop the agent that reads it an hour later. We check every governed tool call against the agent's current scope and authority tier, and fail closed. How Auth does it.

Proof that survives an audit

Macie keeps findings for 90 days. Your auditor wants March. Our records form a hash chain with signed checkpoints, and the verifier tells you what went wrong, not just that something did. That's the property EU AI Act Article 12 and HIPAA §164.312(b) reviewers care about. Try it in your browser, no signup.

An erasure you can defend

GDPR says delete. Your auditor says keep the log. Crypto-shred resolves that: the subject's key material is destroyed, the data becomes unreadable, and the chain still verifies. See the diagram.

Where Amazon Macie is genuinely stronger

Discovery at estate scale is hard, and Macie is good at it. It samples and clusters objects to keep the bill down, it ships managed data identifiers for a long list of countries, it takes your own regex patterns and allow lists, and it scores every bucket so you know where to look first. It publishes findings to EventBridge on its own and to Security Hub CSPM if you ask. And it does all this behind pricing you can put in a spreadsheet before you talk to anyone. Most vendors in this market still hide their price behind a form. We like Macie for that alone.

Here is the push-back. Finding data is not governing it, and AWS's own docs show where the gap sits. Bedrock Guardrails is the native answer for keeping PII away from a model, and its sensitive information filter says plainly that it evaluates text only: PII the model writes into tool call arguments, PII in tool results handed back to the model, and PII in tool definitions are neither blocked nor masked. That is the agent path. Its mask mode is also one-way, replacing a value with {NAME}, so nothing downstream can join on it or get it back under policy. Our tokens are reversible under audit, which is a different design for a different job.

Questions worth asking both of us

These are the questions we'd want answered if we were buying. Ask them on every vendor call, including ours.

Can you cryptographically prove an audit log entry wasn't deleted?

DataShield: yes. Each record commits to the one before it, checkpoints are signed and chained, and verification tells deletion from truncation from tampering. Try it at /verify. Macie: it stores findings for 90 days and publishes them to EventBridge, which is a stream, not a sealed record. AWS documents no tamper-evidence mechanism for Macie findings. Ask what your evidence looks like on day 91.

What happens to a revoked agent mid-session?

DataShield re-checks authority on every governed tool call, so revocation bites on the next call. Macie has no agent concept at all. In AWS the answer is IAM, and an IAM change does not reach inside a running agent's plan. Ask how long a compromised agent keeps reading the bucket Macie flagged.

How does GDPR erasure interact with the audit trail?

DataShield crypto-shreds per-subject key material and issues an ISO 27560 consent receipt. Actor identities in the chain are HMAC-committed, so the evidence stays verifiable after the subject is gone. Macie tells you where the subject's data is. Deleting it, and keeping a defensible record that you did, is left to you.

Is DataShield an Amazon Macie alternative?

Not really, and we won't sell it that way. Macie is sensitive data discovery for S3. We are not a scanner for your existing estate. If your question is "where is my PII," keep Macie. If your question is "who may query it, under what authority, and can I prove what happened," that is us. Most AWS customers who buy DataShield leave Macie switched on.

We use Bedrock Guardrails to de-identify data for our agents. Isn't that enough?

It helps, and for free-form prompts it does real work. But the AWS documentation is explicit that the sensitive information filter evaluates text content only, and in tool use workloads it does not evaluate tool call arguments, tool results, or tool definitions. It also notes that model invocation logs keep the original unmodified request. So the exact place an agent moves a customer record, the tool call, is out of scope. We tokenize the dataset at ingest instead, so the agent's query never held the raw value.

Macie only covers S3. What do we do about the rest?

That's the honest gap, and it's in AWS's own docs: Macie inventories S3 general purpose buckets. For Postgres, Snowflake, a warehouse, a file share, or another cloud, you need something else. Ontology ingests from those sources, classifies PII and PHI, generalizes quasi-identifiers, and serves the result to agents over MCP with Auth-issued tool tokens. See the architecture.

Does DataShield have SOC 2?

Not yet, and we won't imply otherwise. AWS obviously has the certificate wall and we don't. Auth is live a public threat model and a verifier anyone can run. Guardian and Lighthouse have been in production since April 2026. Design-partner terms include source escrow, so a small vendor isn't a single point of failure. Details on the security page.

Macie's positioning: "Discover and protect your sensitive data at scale," using machine learning and pattern matching. — aws.amazon.com/macie, 13 Sep 2026
Macie inventories and analyses Amazon S3 general purpose buckets, and publishes findings to EventBridge and AWS Security Hub CSPM. — Amazon Macie User Guide, 13 Sep 2026
"Macie stores your policy and sensitive data findings for 90 days." — Amazon Macie User Guide, 13 Sep 2026
Published pricing: $1 per GB inspected, $0.01 per 100,000 objects monitored per month, $0.10 per S3 bucket per month, plus a 30-day free trial. — aws.amazon.com/macie/pricing, 13 Sep 2026
Bedrock Guardrails sensitive information filters evaluate text only; in tool use workloads they do not evaluate tool call arguments, tool results, or tool definitions. Mask mode replaces a value with its PII type, such as {NAME}. — Amazon Bedrock User Guide, 13 Sep 2026
Automated sensitive data discovery launched with sampling, object clustering, and per-bucket sensitivity scores. — AWS What's New, 28 Nov 2022
≥80% of unauthorized agent transactions through 2028 will be internal policy violations rather than attacks. — Gartner, 2026

Other head-to-heads

Direct

Get free Demo Center access

You've seen the proof

Ready for a number? Scope your deployment and we'll price it against your own economics.

Get your quote →