---
title: "Zero Trust Architecture: Standards and Enforcement | Lattix"
description: Zero trust grants no implicit trust and verifies every request against policy. Reference coverage of NIST SP 800-207, CISA maturity, and data enforcement.
source: "https://lattix.io/blog/topics/zero-trust/"
content-type: text/markdown
---

# Zero Trust Architecture: Standards and Enforcement | Lattix

[Blog](https://lattix.io/blog/) [Topics](https://lattix.io/blog/topics/) Zero Trust Architecture

Topic

# Zero Trust Architecture

How zero trust works, what the standards require, and why enforcement usually stops before it reaches the data itself.

63posts

Zero trust is a security model that grants no implicit trust to any user, device, network, or workload, and verifies every access request against policy at the moment it is made. NIST SP 800-207 defines the architecture: a policy decision point (PDP) evaluates the request, and a policy enforcement point (PEP) carries out the verdict. The default answer is deny, and a correct implementation stays fail-closed when the PDP is unreachable.

Most programs implement zero trust at the identity and network layers and stop there. That leaves the data plane governed by whatever the receiving system chooses to do, and once a file is decrypted and downloaded, every enforcement point sits behind it. The CISA Zero Trust Maturity Model 2.0 scores data as its own pillar, and it is the pillar where maturity ratings fall furthest.

Posts under this hub cover the standards that define the model, including NIST SP 800-207, NIST SP 1800-35, CISA Zero Trust Maturity Model 2.0, and the DoD Zero Trust Overlays. Others work through attribute-based access control (ABAC), data-centric zero trust, and breach analyses where identity controls held and the data layer did not.

## Frequently asked questions

### What is zero trust architecture?

Zero trust architecture verifies every access request against policy instead of trusting anything inside a network perimeter. NIST SP 800-207 describes the logical components: a policy decision point evaluates identity, device, and context attributes, and a policy enforcement point grants or denies the request. Decisions happen per request rather than per session, and the system denies by default when policy cannot be evaluated.

### What does NIST SP 800-207 actually require?

NIST SP 800-207 is a reference architecture rather than a compliance checklist, so it mandates no specific product. It defines the components of a zero trust deployment: a policy engine, a policy administrator, a policy enforcement point, and the data sources that feed access decisions. NIST SP 1800-35 adds implementation guidance built from working demonstrations of those components.

### How is zero trust different from a VPN?

A VPN authenticates a user once and then grants network reachability, which is implicit trust at scale. Zero trust makes an authorization decision for each request using current attributes about the subject, device, and resource. Compromise a VPN concentrator and an attacker inherits the tunnel; under zero trust, every subsequent request still faces a policy decision evaluated against attributes the attacker does not control.

### Why do zero trust programs stall at the data layer?

Identity and network controls end at the moment of release. Once a user is authorized and a file is decrypted, nothing stands between that copy and its next recipient. The CISA Zero Trust Maturity Model 2.0 treats data as a separate pillar for this reason, and organizations reporting advanced identity maturity routinely report traditional maturity on data.

## Reading on zero trust architecture

[![Lattix branded cover for What Is Data-Centric Security: A Technical Reference. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing a single data object carrying a classification label, a bound access policy and an encrypted payload.](https://lattix.io/images/blog/what-is-data-centric-security-cover.svg) What Is Data-Centric Security: A Technical Reference August 22, 2026 Data-centric security attaches classification, access policy and cryptographic protection to the data object itself. Every read triggers a fresh authorization decision, so the control survives the loss of the network, device or application holding the object. Read More →](https://lattix.io/blog/what-is-data-centric-security/)

[![Lattix branded cover for What Is Trusted Data Format: A Technical Reference. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing an encrypted payload nested inside a manifest that carries a bound access policy.](https://lattix.io/images/blog/what-is-trusted-data-format-cover.svg) What Is Trusted Data Format: A Technical Reference August 22, 2026 Trusted Data Format is an open specification that wraps a file in an encrypted envelope carrying its own access policy, so the policy travels with the object and is checked every time the object is opened. Read More →](https://lattix.io/blog/what-is-trusted-data-format/)

[![Lattix branded cover for AI Agents Need Authorization Decisions, Not Guardrails. /43 section number, dark grid background with surgical yellow accent rules, IBM Plex Mono typography, a reference box contrasting probabilistic steering against an evaluated signed decision, and an attribute strip naming subject, device, environment, purpose, network, risk and object.](https://lattix.io/images/blog/ai-agents-need-authorization-decisions-not-guardrails-cover.svg) AI Agents Need Authorization Decisions, Not Guardrails August 21, 2026 Prompt filters and output classifiers steer a model. They do not authorize anything. An AI action request is an access request, and it belongs at a policy decision point that returns a signed allow or deny with the reasons attached. Read More →](https://lattix.io/blog/ai-agents-need-authorization-decisions-not-guardrails/)

[![Lattix branded cover for the Model Context Protocol 2026-07-28 specification analysis. /44 section number, dark grid background with surgical yellow accent rules, IBM Plex Mono typography, a reference box listing the credential-layer changes the specification lands, and a request-path strip where the object policy enforcement point is highlighted as the decision the specification leaves to the deployer.](https://lattix.io/images/blog/mcp-2026-07-28-spec-credential-not-decision-cover.svg) The MCP 2026-07-28 Spec Hardens the Token. The Action Still Needs a Decision. August 21, 2026 The 2026-07-28 Model Context Protocol specification closes real credential-layer gaps with RFC 9207 issuer validation and issuer-bound client credentials. It answers which client is calling. It does not answer whether this action on this object is permitted. Read More →](https://lattix.io/blog/mcp-2026-07-28-spec-credential-not-decision/)

[![Lattix branded cover for OpenTDF, TDF, and ZTDF: How the Three Terms Relate. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box separating a format, a profile of that format, and an implementation of it.](https://lattix.io/images/blog/opentdf-tdf-ztdf-terminology-cover.svg) OpenTDF, TDF, and ZTDF: How the Three Terms Relate August 21, 2026 TDF is a data object format. ZTDF is a coalition profile of that format. OpenTDF is the open-source specification and implementation. The three names are used interchangeably in the market and refer to different things. Read More →](https://lattix.io/blog/opentdf-tdf-ztdf-terminology/)

[![Lattix branded cover for What Is Persistent Data Protection. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing one encrypted file leaving an organizational boundary while its bound policy and key request path remain attached.](https://lattix.io/images/blog/what-is-persistent-data-protection-cover.svg) What Is Persistent Data Protection August 21, 2026 Persistent data protection keeps an access policy bound to a data object for the life of that object, including after it is copied or downloaded to an unmanaged device. Opening the object requires a fresh authorization decision, not possession of the file. Read More →](https://lattix.io/blog/what-is-persistent-data-protection/)

[![Lattix branded cover for Zero Trust Data Security in 2026: The Standards Map. /45 section number, dark grid background with surgical yellow accent rules, IBM Plex Mono typography, a reference box grouping the standards by the question each one settles, and a strip naming architecture, implementation, measurement, sequencing, cryptographic floor and AI systems.](https://lattix.io/images/blog/zero-trust-data-security-2026-standards-map-cover.svg) Zero Trust Data Security in 2026: The Standards Map August 21, 2026 Nine documents govern zero trust data security in 2026, and each settles a different question. This is the map of which standard answers what, and the one question none of them answers for you. Read More →](https://lattix.io/blog/zero-trust-data-security-2026-standards-map/)

[![Lattix branded cover for Data-Centric Security vs Zero Trust: How the Two Relate. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing five zero trust pillars and a bound policy sitting inside the data pillar.](https://lattix.io/images/blog/data-centric-security-vs-zero-trust-cover.svg) Data-Centric Security vs Zero Trust: How the Two Relate August 20, 2026 Zero trust is the framework. Data-centric security is how its data pillar gets built. Zero trust governs identity, devices, networks, applications and data; data-centric security governs the last of those at the object rather than at the path. Read More →](https://lattix.io/blog/data-centric-security-vs-zero-trust/)

[![Lattix branded cover for What Is a Policy Decision Point. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing a request arriving at a decision component and a signed allow or deny answer returning to an enforcement component in the request path.](https://lattix.io/images/blog/what-is-a-policy-decision-point-cover.svg) What Is a Policy Decision Point August 20, 2026 A policy decision point evaluates an access request against policy and returns allow or deny. NIST SP 800-207 splits it from the enforcement point, and that split is what makes real-time authorization possible. Read More →](https://lattix.io/blog/what-is-a-policy-decision-point/)

[![Lattix branded cover for ABAC, RBAC and ReBAC: Which Model Answers Which Question. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing three policy models side by side above a single data object that each one describes differently.](https://lattix.io/images/blog/abac-rbac-rebac-compared-cover.svg) ABAC, RBAC and ReBAC: Which Model Answers Which Question August 19, 2026 RBAC grants by role, ABAC evaluates attributes at request time, ReBAC traverses relationships between subjects and objects. All three decide who may act. None of them decides whether a specific object should open under current conditions. Read More →](https://lattix.io/blog/abac-rbac-rebac-compared/)

[![Lattix branded cover for How TDF Enforces Access Policy at Decrypt Time. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box tracing a key request through attribute evaluation to a signed allow or deny.](https://lattix.io/images/blog/how-tdf-enforces-policy-at-decrypt-time-cover.svg) How TDF Enforces Access Policy at Decrypt Time August 19, 2026 A TDF object is opened by requesting its key, not by holding it. This reference walks the decrypt sequence from request through attribute evaluation to key release, and describes what the decision contains and what evidence it leaves. Read More →](https://lattix.io/blog/how-tdf-enforces-policy-at-decrypt-time/)

[![Lattix branded cover for Ransomware Doesn't Work on Policy-Bound Data. /10 section number, double-extortion failure metadata, IBM Plex Mono on dark grid background, surgical yellow accent.](https://lattix.io/images/blog/ransomware-doesnt-work-on-policy-bound-data-cover.svg) Ransomware Doesn't Work on Policy-Bound Data August 19, 2026 Modern ransomware exfiltrates before it encrypts and demands payment under the threat of public release. Neither lever works when the data is already encrypted and policy-bound at the object layer. Read More →](https://lattix.io/blog/ransomware-doesnt-work-on-policy-bound-data/)

[![Lattix branded cover for TDF vs Traditional File Encryption: What Each One Enforces. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box contrasting a key held by a holder against a policy bound to an object.](https://lattix.io/images/blog/tdf-vs-traditional-file-encryption-cover.svg) TDF vs Traditional File Encryption: What Each One Enforces August 18, 2026 Traditional file encryption enforces key possession. Trusted Data Format enforces an access policy bound to the object and evaluated at every decrypt. Both are strong cryptography; they answer different questions. Read More →](https://lattix.io/blog/tdf-vs-traditional-file-encryption/)

[![Lattix branded cover for DLP, DRM, DSPM and Data-Centric Security: What Each One Enforces. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing four control layers positioned at inspection, application, inventory and decrypt.](https://lattix.io/images/blog/dlp-drm-dspm-data-centric-security-compared-cover.svg) DLP, DRM, DSPM and Data-Centric Security: What Each One Enforces August 17, 2026 DLP inspects content at egress boundaries. DRM binds usage rights checked by a cooperating application. DSPM discovers and reports exposure without deciding access. Data-centric security binds policy to the object and evaluates it at every decrypt. Read More →](https://lattix.io/blog/dlp-drm-dspm-data-centric-security-compared/)

[![Lattix branded cover for Posture Is Not Enforcement: What DSPM Can and Cannot Do. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box separating an inventory and exposure map from a request-time allow or deny decision.](https://lattix.io/images/blog/dspm-posture-is-not-enforcement-cover.svg) Posture Is Not Enforcement: What DSPM Can and Cannot Do August 17, 2026 DSPM discovers data stores, classifies contents, maps permissions and prioritizes exposure findings. It is not in the request path, so it does not decide access. DSPM and an enforcement layer are complements: one supplies attributes, the other acts on them. Read More →](https://lattix.io/blog/dspm-posture-is-not-enforcement/)

[![Lattix branded cover for How to Revoke Access to a File Someone Already Downloaded. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing a key unwrap request returning deny while the encrypted file remains on a remote disk.](https://lattix.io/images/blog/how-to-revoke-access-to-a-downloaded-file-cover.svg) How to Revoke Access to a File Someone Already Downloaded August 16, 2026 Revoking access to a downloaded file works only when the file was encrypted with a bound policy before distribution. Revocation changes the answer the key service gives at the next open. It prevents future key release and does not reach extracted plaintext. Read More →](https://lattix.io/blog/how-to-revoke-access-to-a-downloaded-file/)

[![Lattix branded cover for What Is Data Sovereignty: Enforcement, Not Geography. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing a jurisdiction constraint bound to a data object rather than to a data center outline.](https://lattix.io/images/blog/what-is-data-sovereignty-cover.svg) What Is Data Sovereignty: Enforcement, Not Geography August 16, 2026 Data sovereignty is the question of whose law governs a data object and who can compel its disclosure. Storage location is a proxy for that answer, and SaaS control planes, vendor support access and AI inference have made the proxy unreliable. Read More →](https://lattix.io/blog/what-is-data-sovereignty/)

[![Lattix branded cover for Policy-Based Data Residency: Turning a Requirement Into a Control. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing a geography attribute entering a decision point and a key release being withheld.](https://lattix.io/images/blog/policy-based-data-residency-cover.svg) Policy-Based Data Residency: Turning a Requirement Into a Control August 15, 2026 Policy-based data residency enforces a geographic restriction as an evaluated attribute at the access decision point rather than as a deployment choice. The control is only as strong as the location claim it evaluates. Read More →](https://lattix.io/blog/policy-based-data-residency/)

[![Lattix branded cover for Data-Centric Zero Trust. /15 section number, policy-bound data object traversing trust boundaries with persistent enforcement, IBM Plex Mono on dark grid background, surgical yellow accent.](https://lattix.io/images/blog/data-centric-zero-trust-policy-travels-with-data-cover.svg) Data-Centric Zero Trust: Policy That Travels With the Data August 14, 2026 Data-centric zero trust binds authorization, encryption, provenance, and revocation directly to the data object, so policy persists and enforces wherever the data goes, independent of infrastructure trust boundaries. Read More →](https://lattix.io/blog/data-centric-zero-trust-policy-travels-with-data/)

[![Lattix branded cover for Data Provenance vs Lineage vs Chain of Custody. /12 section number, three overlapping evidence circles with cryptographic seals, IBM Plex Mono on dark grid background, surgical yellow accent.](https://lattix.io/images/blog/data-provenance-lineage-chain-of-custody-cover.svg) Data Provenance vs Lineage vs Chain of Custody: What Runtime Security Actually Needs August 14, 2026 Provenance tells you where data came from. Lineage shows how it transformed. Chain of custody proves who held it. Each answers a different security question, and conflating them weakens your evidence model. Read More →](https://lattix.io/blog/data-provenance-lineage-chain-of-custody/)

[![Lattix branded cover for How to Give an AI Agent Access to Sensitive Data Safely. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing an agent issuing repeated tool calls, each one hitting a separate authorization decision before any object opens.](https://lattix.io/images/blog/how-to-give-an-ai-agent-access-to-sensitive-data-cover.svg) How to Give an AI Agent Access to Sensitive Data Safely August 14, 2026 Give an AI agent a distinct identity, authorize each action rather than each session, require purpose as an asserted attribute, and enforce at the data object so derived artifacts stay governed. Read More →](https://lattix.io/blog/how-to-give-an-ai-agent-access-to-sensitive-data/)

[![Lattix branded cover for Protecting RAG Context and Agent Tool Outputs Across Trust Boundaries. Section number, data-flow trust boundary map, IBM Plex Mono on dark grid background, surgical yellow accent on policy enforcement points.](https://lattix.io/images/blog/protecting-rag-context-agent-tool-outputs-trust-boundaries-cover.svg) Protecting RAG Context and Agent Tool Outputs Across Trust Boundaries August 14, 2026 Modern AI systems copy, cache, retrieve, and forward data across multiple trust boundaries. Session-level authorization does not persist once data leaves its origin. A data-centric security model with persistent policy, contextual authorization, and cross-boundary evidence closes the gap. Read More →](https://lattix.io/blog/protecting-rag-context-agent-tool-outputs-trust-boundaries/)

[![Lattix branded cover for Data-Centric Security for Defense: A Reference Architecture. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing seven stacked pillars and a labelled data object bound to a policy decision.](https://lattix.io/images/blog/data-centric-security-for-defense-reference-cover.svg) Data-Centric Security for Defense: A Reference Architecture August 13, 2026 Data-centric security for defense protects the data object itself rather than the network around it. This reference architecture maps the DoD Zero Trust Strategy data pillar to NIST SP 800-53 controls and to the NSA implementation phases. Read More →](https://lattix.io/blog/data-centric-security-for-defense-reference/)

[![Lattix branded cover for How Coalition Partners Share Classified Data Without Shared Infrastructure. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing a labelled object crossing between two national enclaves that share no common network.](https://lattix.io/images/blog/coalition-classified-data-sharing-reference-cover.svg) How Coalition Partners Share Classified Data Without Shared Infrastructure August 12, 2026 Coalition partners share classified data by binding a machine-readable confidentiality label to each object and enforcing release at the object, not by building a common network. STANAG 4774, STANAG 4778 and Federated Mission Networking define how. Read More →](https://lattix.io/blog/coalition-classified-data-sharing-reference/)

[![Lattix branded cover for ACP 240 and Zero Trust Data Format: What the CCEB Standard Specifies. Dark grid background, surgical yellow accent, IBM Plex Mono typography, with a reference box showing a labelled data object crossing a coalition boundary intact.](https://lattix.io/images/blog/nato-acp-240-zero-trust-data-format-cover.svg) ACP 240 and Zero Trust Data Format: What the CCEB Standard Specifies August 11, 2026 ACP 240 is a CCEB allied publication covering data-centric security interoperability, and it is where Zero Trust Data Format is specified. A ZTDF object carries NATO STANAG 4774 labels and STANAG 4778 bindings. NATO has not adopted ZTDF for its own framework. Read More →](https://lattix.io/blog/nato-acp-240-zero-trust-data-format/)

[![Lattix branded cover for the SonicWall SMA1000 CVE-2026-15409 and CVE-2026-15410 analysis. Dark grid background, surgical yellow accent, IBM Plex Mono typography, July 14 2026 KEV addition and July 17 2026 federal deadline, CVSS 10.0 and CVSS 7.2 reference box, and a compromise-path strip where the object policy enforcement point is highlighted as the control that survives a gateway takeover.](https://lattix.io/images/blog/sonicwall-sma1000-cve-2026-15409-gateway-not-data-boundary-cover.svg) SonicWall SMA1000 Zero-Days Chain to Root. The Gateway Is Not the Data Boundary. July 21, 2026 CISA added SonicWall SMA1000 CVE-2026-15409 and CVE-2026-15410 to KEV on July 14, 2026. Chained, an unauthenticated SSRF and a root code injection hand an attacker the remote-access gateway. Object-level enforcement is what still refuses the reach it grants. Read More →](https://lattix.io/blog/sonicwall-sma1000-cve-2026-15409-gateway-not-data-boundary/)

[![Lattix branded cover for AD FS CVE-2026-56155 Forges Federation Tokens. Dark grid background, surgical yellow accent, IBM Plex Mono typography, July 14 2026 KEV addition and July 28 2026 federal deadline, CVSS 7.8 and CWE-1220 reference row, and a token-issuance strip where the object policy enforcement point is highlighted as the control that survives forgery.](https://lattix.io/images/blog/adfs-cve-2026-56155-federation-token-forgery-data-boundary-cover.svg) AD FS CVE-2026-56155 Forges Federation Tokens. Identity Is Not the Data Boundary. July 20, 2026 CISA added AD FS CVE-2026-56155 to KEV on July 14, 2026 with a July 28 federal deadline. The flaw hands an attacker the token-signing keys, and a forged federation token replays against every connected application. Object-level enforcement is what still refuses it. Read More →](https://lattix.io/blog/adfs-cve-2026-56155-federation-token-forgery-data-boundary/)

[![Lattix branded cover for Check Point VPN CVE-2026-50751. /42 section number, June 2026 KEV disclosure date, CVSS 9.3 authentication-bypass statistic, IBM Plex Mono on dark grid background, surgical yellow accent on the object-level policy enforcement point in a VPN-to-data flow strip.](https://lattix.io/images/blog/check-point-vpn-cve-2026-50751-concentrator-trust-boundary-cover.svg) Check Point VPN CVE-2026-50751 Is in KEV. The Concentrator Is Not the Trust Boundary. July 6, 2026 Check Point VPN CVE-2026-50751 is an actively exploited IKEv1 authentication bypass that grants an unauthenticated attacker a valid VPN session. CISA added it to KEV with a June 11, 2026 federal deadline. A VPN session is network reachability, not authority over data. Read More →](https://lattix.io/blog/check-point-vpn-cve-2026-50751-concentrator-trust-boundary/)

[![Lattix branded cover for the sovereign data architecture mid-year analysis, /45 section number on a dark grid in IBM Plex Mono with surgical yellow accent lines, headline stating sovereignty is a property of the object, and a stat panel citing the DOJ Data Security Program enforcement dates.](https://lattix.io/images/blog/sovereign-data-architecture-federal-mission-mid-year-cover.svg) Sovereign Data Architecture at Mid-2026: Policy Bound to the Object July 6, 2026 A mid-2026 stocktake of data sovereignty: DOJ 28 CFR Part 202 enforcement, the EU's sovereign cloud framework, and coalition data sharing all point to the same conclusion. Region-pinning fails at the data layer. Only policy bound to the object travels with the data. Read More →](https://lattix.io/blog/sovereign-data-architecture-federal-mission-mid-year/)

[![Lattix branded cover for the Executive Order 14409 post-quantum analysis. /42 section number, IBM Plex Mono on a dark grid background, the order named and dated June 22 2026, the December 31 2030 key-establishment deadline, and a crypto-inventory strip with the object-level enforcement point highlighted in surgical yellow.](https://lattix.io/images/blog/eo-14409-post-quantum-mandate-cryptographic-bill-of-materials-cover.svg) EO 14409 Sets Federal Post-Quantum Deadlines. The Cryptographic Bill of Materials Is the Test. July 3, 2026 Executive Order 14409 sets December 2030 and 2031 deadlines for federal post-quantum migration and orders a cryptographic bill of materials. The binding requirement is naming which algorithm protects which data object, not swapping a transport cipher. Read More →](https://lattix.io/blog/eo-14409-post-quantum-mandate-cryptographic-bill-of-materials/)

[![Lattix branded cover for HHS HC3 Q2 2026 Threat Brief. /32 section number, Q2 2026 threat brief publish window, healthcare-targeted intrusion count statistic, IBM Plex Mono on dark grid background, surgical yellow accent on the architectural response pillar in a threat actor strip.](https://lattix.io/images/blog/hhs-hc3-healthcare-q2-2026-data-centric-threat-response-cover.svg) HHS HC3 Q2 2026 Threat Brief: Healthcare Data Is the Target. The Response Is Architectural. July 2, 2026 HHS HC3 quarterly threat briefs catalog the threat actor groups and tactics targeting healthcare data through Q2 2026. The pattern across Medtronic, Change Healthcare aftermath, and recent intrusions is consistent. Healthcare data is high-value and weakly bound to enforcement. Read More →](https://lattix.io/blog/hhs-hc3-healthcare-q2-2026-data-centric-threat-response/)

[![Lattix branded cover for the Oracle PeopleSoft CVE-2026-35273 analysis. /41 section number, IBM Plex Mono on a dark grid background, the unauthenticated Environment Management flaw named, a CVSS 9.8 statistic, a 68 percent higher-education victim share, and an exploit-to-data strip with the object-level enforcement point highlighted in surgical yellow.](https://lattix.io/images/blog/oracle-peoplesoft-cve-2026-35273-unauth-rce-data-layer-cover.svg) Oracle PeopleSoft CVE-2026-35273: Unauthenticated Access Reaches Data the Identity Layer Never Sees July 2, 2026 ShinyHunters exploited an unauthenticated PeopleSoft flaw as a zero-day for two weeks before Oracle's advisory. Universities took 68 percent of the hits. No credential was stolen and none was needed. The data carried no policy of its own. Read More →](https://lattix.io/blog/oracle-peoplesoft-cve-2026-35273-unauth-rce-data-layer/)

[![Lattix branded cover for the OWASP Top 10 for Agentic Applications 2026. /44 section number, IBM Plex Mono typography on a dark grid background, surgical yellow accent on the object-level policy enforcement point, ASI03 identity abuse and ASI06 memory poisoning callouts, LATTIX wordmark and lattix.io footer.](https://lattix.io/images/blog/owasp-agentic-ai-top-10-data-layer-cover.svg) OWASP Agentic Top 10: Memory Poisoning and Identity Abuse Are Data-Layer Risks July 2, 2026 OWASP's Top 10 for Agentic Applications 2026 names memory poisoning, identity abuse, and tool misuse among the top agentic risks. Several entries reduce to ungoverned data access, and object-level cryptographic enforcement is the control the taxonomy implies but does not name. Read More →](https://lattix.io/blog/owasp-agentic-ai-top-10-data-layer/)

[![Lattix branded cover for the mid-year 2026 breach pattern analysis. /27 section number, IBM Plex Mono on dark grid background, the identity-to-data pivot named across six 2026 incidents, a 4.67 million dollar credential-breach statistic, and a pivot strip with the data-layer enforcement point highlighted in surgical yellow.](https://lattix.io/images/blog/mid-year-2026-breach-pattern-identity-to-data-pivot-cover.svg) The Mid-Year 2026 Breach Pattern: Identity Holds, Data Does Not June 30, 2026 Six 2026 breaches, from Mercor to the Canvas and Medtronic disclosures, trace one pattern. Identity and network controls evaluate correctly. The compromised principal reads data the credential is authorized to reach. The data carries no policy of its own. Read More →](https://lattix.io/blog/mid-year-2026-breach-pattern-identity-to-data-pivot/)

[![Lattix branded cover for Federal Cloud Migration ATO Acceleration Lives at the Data Layer. /31 section number, ATO control family pace comparison, IBM Plex Mono on dark grid background, yellow accent on the data-control families that consistently bottleneck ATO timelines.](https://lattix.io/images/blog/federal-cloud-migration-ato-acceleration-data-layer-cover.svg) Federal Cloud Migration ATO Acceleration Lives at the Data Layer June 26, 2026 ATO timelines for federal cloud workloads consistently exceed the planned program schedule. Boundary, identity, and configuration controls converge quickly. Data controls do not. The architecture that produces ATO evidence by construction is the architecture that compresses the cycle. Read More →](https://lattix.io/blog/federal-cloud-migration-ato-acceleration-data-layer/)

[![Lattix branded cover for Microsoft Purview Sensitivity Labels and ZTDF Diverge When the Label Stops Carrying Policy. /30 section number, label metadata versus policy-bound object comparison, IBM Plex Mono on dark grid background, yellow accent on the boundary where Purview enforcement ends and ZTDF enforcement persists.](https://lattix.io/images/blog/microsoft-purview-sensitivity-labels-ztdf-policy-divergence-cover.svg) Microsoft Purview Sensitivity Labels and ZTDF Diverge When the Label Stops Carrying Policy June 22, 2026 Microsoft Purview sensitivity labels travel with files and provide a useful classification overlay. The label is metadata; the policy lives in the Purview service. ZTDF binds policy to the object cryptographically. Compare what survives a cross-tenant transfer in each model. Read More →](https://lattix.io/blog/microsoft-purview-sensitivity-labels-ztdf-policy-divergence/)

[![Lattix branded cover for JADC2 Cross-Domain Data Sharing Requires a Data-Centric Substrate. /29 section number, JADC2 milestone date, four cross-domain release patterns statistic, IBM Plex Mono on dark grid background, surgical yellow accent on the policy enforcement point in a multi-domain release strip.](https://lattix.io/images/blog/jadc2-cross-domain-data-sharing-zero-trust-architecture-cover.svg) JADC2 Cross-Domain Data Sharing Requires a Data-Centric Substrate June 18, 2026 DoD JADC2 and CJADC2 milestones depend on cross-domain release of mission data at operational tempo. Guard-appliance cross-domain solutions do not scale to that tempo. ABAC at the policy enforcement point over ZTDF-formatted objects is the substrate that does. Read More →](https://lattix.io/blog/jadc2-cross-domain-data-sharing-zero-trust-architecture/)

[![Lattix branded cover for TDF and ZTDF for Procurement Officers. /29 section number, TDF-to-ZTDF specification diff at the policy and key access layers, IBM Plex Mono on dark grid background, yellow accent on the procurement language that resolves to a configurable capability rather than a custom integration.](https://lattix.io/images/blog/tdf-ztdf-procurement-officers-specification-binds-cover.svg) TDF and ZTDF for Procurement Officers: What the Specification Actually Specifies June 17, 2026 NSA Phase Two cites ZTDF and IC-TDF as data rights management schema examples. The two specifications differ in scope, lifecycle, and required cryptographic agility. The differences matter when writing FY27 acquisition language. Walk through what each binds and how that maps to procurable capability. Read More →](https://lattix.io/blog/tdf-ztdf-procurement-officers-specification-binds/)

[![Lattix branded cover for Cross-Domain Solutions Modernize From Guard Appliances to Object-Level Release. /27 section number, twenty-year guard lineage to ZTDF/IC-TDF object-level release, IBM Plex Mono on dark grid background, yellow accent on the object-level release decision point.](https://lattix.io/images/blog/cross-domain-solutions-guard-appliances-object-level-release-cover.svg) Cross-Domain Solutions Modernize From Guard Appliances to Object-Level Release June 8, 2026 Guard appliances have served twenty years of joint and coalition cross-domain release. They evaluate data at the boundary. NSA Phase Two cites ZTDF and IC-TDF as schemas that move release evaluation to the object itself, at cryptographic speed. Read More →](https://lattix.io/blog/cross-domain-solutions-guard-appliances-object-level-release/)

[![Lattix branded cover for AI Agents Form Credential Delegation Chains. /25 section number, agent-to-agent delegation hops metric, IBM Plex Mono on dark grid background, surgical yellow accent on the policy enforcement point in a multi-hop chain strip.](https://lattix.io/images/blog/ai-agent-credential-delegation-chains-policy-bound-tokens-cover.svg) AI Agents Form Credential Delegation Chains. Static Tokens Cannot Hold. June 4, 2026 Autonomous agent workflows now span multiple hops, multiple vendors, and multiple identity domains. A bearer token at any hop is the failure point. Treating each delegated credential as a policy-bound data object closes the chain. The architecture is procurable today. Read More →](https://lattix.io/blog/ai-agent-credential-delegation-chains-policy-bound-tokens/)

[Lattix Anthropic's Zero Trust for AI Agents Framework Reaches the Data Layer at the Optimized Tier June 2, 2026 Anthropic published a Zero Trust framework for autonomous AI agents on May 27, 2026. The framework names the right architecture for the agent threat model. The Optimized tier reaches the data layer. Data-centric enforcement is how organizations get there. Read More →](https://lattix.io/blog/anthropic-zero-trust-ai-agents-framework-data-layer-optimized-tier/)

[![Lattix branded cover for The Nx Console Supply Chain Attack Is a Credentials-as-Data Story. /22 section number, May 18 2026 incident timestamp, 3,800 GitHub internal repositories statistic, IBM Plex Mono on dark grid background, surgical yellow accent on the policy enforcement point in a credential release flow strip.](https://lattix.io/images/blog/nx-console-supply-chain-credentials-as-data-cover.svg) The Nx Console Supply Chain Attack Is a Credentials-as-Data Story May 22, 2026 On May 18, 2026, a compromised Nx Console VS Code extension exfiltrated credentials from developer workstations. By May 19, GitHub disclosed that 3,800 internal repositories had been exfiltrated as a result. The pivot was static credentials. The architectural answer is to treat credentials as policy-bound data. Read More →](https://lattix.io/blog/nx-console-supply-chain-credentials-as-data/)

[![Lattix branded cover for Vercel + Context.ai: OAuth Is the Quiet Supply Chain. /07 section number, OAuth supply chain metadata, IBM Plex Mono on dark grid background.](https://lattix.io/images/blog/vercel-context-ai-oauth-supply-chain-policy-bound-secrets-cover.svg) Vercel + Context.ai: OAuth Is the Quiet Supply Chain May 13, 2026 Vercel's April 19, 2026 security bulletin documented an OAuth compromise that exfiltrated environment variables through an authorized AI integration. Identity, network, and device controls all evaluated correctly. The data did not enforce its own policy. Read More →](https://lattix.io/blog/vercel-context-ai-oauth-supply-chain-policy-bound-secrets/)

[![Lattix branded cover for The DoD Zero Trust Overlays Already Describe a Data-Centric Architecture. /15 section number, 152 capability outcomes statistic, seven pillar map highlighting data pillar, IBM Plex Mono on dark grid background, surgical yellow accent.](https://lattix.io/images/blog/dod-zt-symposium-capability-overlays-data-centric-cover.svg) The DoD Zero Trust Overlays Already Describe a Data-Centric Architecture May 12, 2026 The September 2024 DoD Zero Trust Overlays define 152 capability outcomes across seven pillars. The Data Pillar outcomes do not name a vendor and do not name a product category. They describe the architecture data-centric security has been building toward since the original strategy. Read More →](https://lattix.io/blog/dod-zt-symposium-capability-overlays-data-centric/)

[![Lattix branded cover for The Medtronic Breach Is the Canvas Playbook Run Against a Medical Device Maker. /12 section number, 9M records statistic, ShinyHunters extortion timeline, IBM Plex Mono on dark grid background, surgical yellow accent.](https://lattix.io/images/blog/medtronic-shinyhunters-breach-healthcare-data-enforcement-cover.svg) The Medtronic Breach Is the Canvas Playbook Run Against a Medical Device Maker May 12, 2026 Medtronic confirmed a ShinyHunters extortion event in an SEC 8-K on April 24, 2026. Nine million records claimed, the leak site listing pulled before the deadline. The architectural lesson is the same one the Canvas breach already wrote: containment closes the access path, not the copies that already left. Read More →](https://lattix.io/blog/medtronic-shinyhunters-breach-healthcare-data-enforcement/)

[![Lattix branded cover for NSA's Zero Trust Implementation Guidelines Turn Target-Level Maturity Into Sequence. /06 section number, Phase One and Phase Two metadata, IBM Plex Mono on dark grid background.](https://lattix.io/images/blog/nsa-zero-trust-implementation-guidelines-target-level-sequence-cover.svg) NSA's Zero Trust Implementation Guidelines Turn Target-Level Maturity Into Sequence May 12, 2026 NSA published Phase One of its Zero Trust Implementation Guidelines in January 2026 and Phase Two later that month. The market did not need another zero trust definition. It needed the sequence, and the guidelines provide it. Read More →](https://lattix.io/blog/nsa-zero-trust-implementation-guidelines-target-level-sequence/)

[![Lattix branded cover for NSA Phase Two Cites ZTDF and IC-TDF as DRM Examples. Procurement Catches Up Next. /13 section number, ZIG Phase Two metadata, Data Rights Management schema callout, IBM Plex Mono on dark grid background, surgical yellow accent.](https://lattix.io/images/blog/nsa-ztdf-interoperability-standard-phase-two-cover.svg) NSA Phase Two Cites ZTDF and IC-TDF as DRM Examples. Procurement Catches Up Next. May 12, 2026 NSA's Zero Trust Implementation Guideline Phase Two, released January 30, 2026, tells participating components to standardize a data rights management schema and cites ZTDF and IC-TDF as the examples. A recommendation, not a mandate, and enough to write a requirement against. Read More →](https://lattix.io/blog/nsa-ztdf-interoperability-standard-phase-two/)

[![Lattix branded cover for Why Network Zero Trust Stops at the Data Boundary. /14 section number, five pillar maturity map showing data pillar gap, IBM Plex Mono on dark grid background, surgical yellow accent.](https://lattix.io/images/blog/why-network-zero-trust-stops-at-data-boundary-cover.svg) Why Network Zero Trust Stops at the Data Boundary May 12, 2026 NIST SP 800-207 and the CISA Zero Trust Maturity Model define five pillars. Most enterprise programs stop at networks. The data pillar requires cryptographic enforcement bound to the object, not perimeter or session controls, and the gap is architectural rather than budgetary. Read More →](https://lattix.io/blog/why-network-zero-trust-stops-at-data-boundary/)

[![Lattix branded cover for Coalition Data Sharing. /06 section number, IBM Plex Mono on dark grid background, surgical yellow accent.](https://lattix.io/images/blog/classified-data-sharing-coalition-partners-cover.svg) Coalition Data Sharing Without Infrastructure Agreement May 8, 2026 When allied partners operate separate networks and classification systems, data-centric security moves enforcement from infrastructure to the data itself. Read More →](https://lattix.io/blog/classified-data-sharing-coalition-partners/)

[![Lattix branded cover for the Canvas breach analysis. /05 section number, IBM Plex Mono on dark grid background, surgical yellow accent, 275M record stat panel and FERPA enforcement gap reference.](https://lattix.io/images/blog/instructure-canvas-breach-data-enforcement-cover.svg) The Canvas Breach Is a Data Enforcement Story, Not a Containment Story May 8, 2026 ShinyHunters claimed 275 million records from Instructure across 9,000 institutions. Containment closed the access path. The records had already crossed the policy boundary. The disclosure surface is what FERPA, schools, and downstream subjects have to deal with now. Read More →](https://lattix.io/blog/instructure-canvas-breach-data-enforcement/)

[![Lattix branded cover for secure file transfer. /15 section number, IBM Plex Mono on dark grid background, surgical yellow accent.](https://lattix.io/images/blog/secure-file-transfer-age-of-zero-trust-cover.svg) Secure File Transfer in the Age of Zero Trust May 8, 2026 Every managed file transfer product trusts the endpoint. Recent MFT breaches proved that trust fails at scale. Zero Trust requires the file itself to carry its own security policy. Read More →](https://lattix.io/blog/secure-file-transfer-age-of-zero-trust/)

[![Lattix branded cover for autonomous AI agent identity and zero trust. /16 section number, IBM Plex Mono on dark grid background, surgical yellow accent. Agent-action pillars: PROMPT, TOOL-CALL, DATA-ACCESS, SUB-AGENT, and AUDIT with AUDIT highlighted.](https://lattix.io/images/blog/securing-autonomous-ai-agents-cover.svg) Identity and Authority at Machine Speed May 8, 2026 Autonomous agents make decisions and move data at machine speed. Zero Trust identity architecture must evolve to grant and audit authority at that pace. Read More →](https://lattix.io/blog/securing-autonomous-ai-agents/)

[![Lattix branded cover for Trusted Data Format evolution from IC origins to ZTDF. /19 section number, IBM Plex Mono on dark grid background, surgical yellow accent.](https://lattix.io/images/blog/trusted-data-format-origin-evolution-future-cover.svg) Trusted Data Format: From IC Origin to ZTDF Standard May 8, 2026 The Trusted Data Format began in the intelligence community as a solution to cross-domain data sharing. Its evolution reflects the shift from network-centric to data-centric security. Read More →](https://lattix.io/blog/trusted-data-format-origin-evolution-future/)

[![Lattix branded cover for ABAC vs RBAC. /08 section number, ABAC and RBAC contrast metadata, IBM Plex Mono on dark grid background, surgical yellow accent.](https://lattix.io/images/blog/abac-vs-rbac-zero-trust-default-cover.svg) ABAC vs RBAC: Why Attribute-Based Access Control Is the Zero Trust Default May 7, 2026 Role-based access grants standing privileges that outlive their purpose. Attribute-based access evaluates every request in context. For zero trust, only one of these actually works. Read More →](https://lattix.io/blog/abac-vs-rbac-zero-trust-default/)

[![Lattix branded cover for DoD Zero Trust Strategy 2.0 Extends to OT and Weapon Systems. /05 section number, FY27 91 capability outcomes metadata, IBM Plex Mono on dark grid background.](https://lattix.io/images/blog/dod-zero-trust-strategy-2-data-pillar-ot-weapons-cover.svg) DoD Zero Trust Strategy 2.0 Extends to OT and Weapon Systems May 7, 2026 DoD Zero Trust Strategy 2.0, published March 2026, brings operational technology, IoT, defense critical infrastructure, and weapon systems under the same target-level maturity expectations as enterprise IT. The data pillar is where the new scope hits hardest. Read More →](https://lattix.io/blog/dod-zero-trust-strategy-2-data-pillar-ot-weapons/)

[![Lattix branded cover for Federal Zero Trust Deadlines Are Binding. Data Layer Enforcement Is Not. Yellow accent bar, /02 section number, IBM Plex Mono typography on dark grid background.](https://lattix.io/images/blog/federal-zero-trust-deadlines-data-layer-enforcement-cover.svg) Federal Zero Trust Deadlines Are Binding. Data Layer Enforcement Is Not. May 6, 2026 CISA's April 2026 binding directive sets Q3/Q4 2026 deadlines for identity, network, and device zero trust controls. The data layer remains optional. Programs that hit every milestone without object-level enforcement still fail on a compromised service account. Read More →](https://lattix.io/blog/federal-zero-trust-deadlines-data-layer-enforcement/)

[![Lattix branded cover for CISA's April 2026 OT Zero Trust Guidance Leaves the Data Plane Unaddressed. /04 section number, OT zero trust maturity reference, IBM Plex Mono on dark grid background, surgical yellow accent.](https://lattix.io/images/blog/cisa-ot-zero-trust-april-2026-data-plane-gap-cover.svg) CISA's April 2026 OT Zero Trust Guidance Leaves the Data Plane Unaddressed May 5, 2026 On April 30, 2026, CISA and four federal partners released a joint guide adapting zero trust principles to operational technology. The guide advances identity, network, and visibility maturity for OT. The data plane remains an open enforcement gap. Read More →](https://lattix.io/blog/cisa-ot-zero-trust-april-2026-data-plane-gap/)

[![Lattix diagram showing an MCP-connected AI agent with injected prompts denied at policy enforcement points, ABAC-compliant accesses allowed with ML-KEM-768 unwrap, and every decision committed to a Merkle-tree lineage.](https://lattix.io/images/blog/mcp-blast-radius-cryptographic-data-enforcement-cover.svg) How Cryptographic Data Enforcement Contains the MCP Blast Radius April 24, 2026 AI agents acting on injected instructions are now the dominant exfiltration vector. Two April 2026 incidents show why ABAC enforcement at the data object, not the network or the identity plane, is the control that actually contains MCP. Read More →](https://lattix.io/blog/mcp-blast-radius-cryptographic-data-enforcement/)

[![Abstract Lattix diagram of a compromised runtime pipeline feeding downstream data stores, with policy-bound data objects remaining sealed.](https://lattix.io/images/blog/mercor-breach-data-centric-security-story-cover.svg) The Mercor Breach Is a Data-Centric Security Story. Not an Identity One. April 17, 2026 A malicious LiteLLM package pushed March 27, 2026 cascaded into a four-terabyte exfiltration from an AI training-data vendor whose customer list reads like the frontier lab leaderboard. Identity controls were present. They were not the control that mattered. Read More →](https://lattix.io/blog/mercor-breach-data-centric-security-story/)

[![Lattix branded cover for How Blockchain Enhances Cybersecurity in the Era of Digital Threats. /01 section number, tamper-evident audit trail metadata, IBM Plex Mono on dark grid background.](https://lattix.io/images/blog/blockchain-for-cybersecurity-cover.svg) How Blockchain Enhances Cybersecurity in the Era of Digital Threats April 29, 2025 Blockchain technology offers unique capabilities for cybersecurity: tamper-proof audit trails, smart contracts for access control, and decentralized identity management. Read More →](https://lattix.io/blog/blockchain-for-cybersecurity/)

[![Lattix branded cover for Can You Trust AI? Not Without Securing the Data It Trains On. /02 section number, training-data integrity metadata, IBM Plex Mono on dark grid background.](https://lattix.io/images/blog/can-you-trust-ai-not-without-securing-the-data-it-trains-on-cover.svg) Can You Trust AI? Not Without Securing the Data It Trains On April 15, 2025 AI trustworthiness depends entirely on training data integrity. Without securing the data pipeline, AI outputs cannot be trusted. Read More →](https://lattix.io/blog/can-you-trust-ai-not-without-securing-the-data-it-trains-on/)

[![Lattix branded cover for What is Zero Trust Data Format (ZTDF) and Why Does It Matter? /08 section number, embedded-control self-enforcing metadata, IBM Plex Mono on dark grid background.](https://lattix.io/images/blog/what-is-zero-trust-data-format-and-why-does-it-matter-cover.svg) What is Zero Trust Data Format (ZTDF) and Why Does It Matter? February 9, 2025 ZTDF creates a self-enforcing security boundary around every data object with embedded encryption, access policies, and audit capabilities. Read More →](https://lattix.io/blog/what-is-zero-trust-data-format-and-why-does-it-matter/)

[![Lattix branded cover for Why Zero Trust is the Future of Data Security. /09 section number, verify-always trust-model metadata, IBM Plex Mono on dark grid background.](https://lattix.io/images/blog/why-zero-trust-is-the-future-of-data-security-cover.svg) Why Zero Trust is the Future of Data Security February 9, 2025 Traditional perimeter-based security is failing. Zero Trust architecture operates on a simple principle: never trust, always verify. Read More →](https://lattix.io/blog/why-zero-trust-is-the-future-of-data-security/)

## Related topics

- [Data Security](https://lattix.io/blog/topics/data-security/)
- [Zero Trust Data Format](https://lattix.io/blog/topics/ztdf/)
- [Access Control](https://lattix.io/blog/topics/access-control/)
- [AI Security](https://lattix.io/blog/topics/ai-security/)
- [Post-Quantum Cryptography](https://lattix.io/blog/topics/post-quantum-cryptography/)
- [Cryptography and Key Management](https://lattix.io/blog/topics/cryptography/)

[All topics →](https://lattix.io/blog/topics/)