TL;DR: Data security weakens when organisations treat valuable information as something to lock away rather than govern in motion, according to AET Europe, because risk sits in the identities, handoffs, and channels that move data through customer workflows. Trust-aware controls beat vault-only thinking when integrity and context matter more than storage alone.
At a glance
What this is: NHI Mgmt Group's analysis, drawing on AET Europe's blog post: Data security is strongest when organisations govern trusted identities, handoffs, and integrity across customer workflows, not just storage.
Why it matters: Identity-aware data controls matter because the real exposure often sits in how information moves, who can touch it, and whether each step remains trustworthy.
Context
Data security is not just a storage problem. The harder governance issue is whether information stays trustworthy while it moves through business workflows, crosses organisational boundaries, and is handled by multiple identities along the way. That makes the access path, not only the repository, part of the security boundary.
This becomes especially relevant where customer, employee, and third-party interactions are chained together across systems. If the organisation cannot verify who is acting, what changed, and whether a step was completed correctly, then compliance alone does not protect the data supply chain.
AET Europe's framing is typical of the broader governance gap: many organisations defend vaults more confidently than the operational paths that make data valuable.
Key questions
Q: How do teams secure data that moves through business workflows?
A: Teams secure data moving through business workflows by classifying the data, applying encryption in transit and at rest, and controlling each transfer channel with authenticated interfaces, DLP rules, and least-privilege access to source and destination systems. Workflow controls should also log every handoff, validate recipients, and block unauthorised exports or re-routing.
Q: Why is compliance not enough for data security?
A: Compliance is a baseline, not a complete security strategy, because regulatory requirements usually define minimum controls rather than the full protection needed for real threats, sensitive data paths, or privileged access. A security programme also needs risk-based control selection, segmentation, monitoring, incident response, and periodic control testing beyond audit evidence.
Q: How do digital certificates support trusted data exchange?
A: Digital certificates support trusted data exchange by binding a public key to a verified identity, usually a system, service, or device, through a certificate authority. They enable mutual TLS, server authentication, and encrypted sessions, so recipients can verify cryptographic trust before exchanging data and reject spoofed endpoints or tampered traffic.
Q: What is the best way to prioritise crown-jewel data protection?
A: The best way is to rank assets by business criticality, then protect the highest-value data with stronger access controls, tighter segmentation, and continuous monitoring. Crown-jewel data should have named owners, explicit handling rules, encryption, restricted sharing, and recovery plans, because its exposure or loss would cause the greatest operational or legal harm.
Technical breakdown
Data security in motion versus data at rest
Data at rest is information stored in databases, files, object stores, or backups. Data in motion is information moving between systems, users, and services across workflow steps. The architectural gap appears when security concentrates on repositories but leaves handoffs, APIs, and application workflows under-governed. In that model, the storage layer can be hardened while the business process still leaks value, integrity, or confidentiality during transfer. For crown-jewel data, the relevant question is not only where it sits, but whether every transfer is authenticated, authorised, and traceable. See the Data Security Guide.
Practical implication: Map where crown-jewel data changes state, then assign controls to each transition rather than only to the final repository.
Trusted identities as a control on customer workflows
A trusted identity is any human, service, or external party whose claimed identity has been verified well enough for the step it is performing. In data workflows, identity assurance is what prevents the wrong party from seeing, changing, or forwarding sensitive information. The article's core operational point is that data trust depends on identity trust at each handoff. Without that linkage, downstream checks become weaker because the system cannot reliably tell who initiated the action or whether that actor was appropriate for the step.
Practical implication: Tie workflow permissions to identity assurance level so each data step is limited to the actor appropriate for that stage.
Digital certificates and secure handoffs
Digital certificates bind a cryptographic identity to a device, user, or service and are commonly used to establish trust between parties that do not know each other directly. In workflow security, certificates support authentication, encryption, and assurance that a message or transaction came from an expected source. Their value is highest where data must move across organisational boundaries or between loosely coupled systems. If certificate lifecycle, trust chains, or revocation are poorly governed, the workflow can still be exposed even when the storage layer is strongly protected.
Practical implication: Use certificate lifecycle controls to secure workflow handoffs and revoke trust quickly when an identity or channel is no longer valid.
Threat narrative
Attacker objective: The objective is to manipulate or steal valuable data by exploiting weak trust controls in the workflow that moves it.
- Entry occurs when data is passed into a customer workflow through a weakly verified identity, an uncontrolled channel, or an unreliable upstream step.
- Credential or trust abuse follows when the process accepts the actor or payload without rechecking authenticity, allowing modified or misdirected data to continue downstream.
- Impact appears as corrupted decisions, exposed crown-jewel information, broken customer trust, or operational delay when the workflow can no longer be relied on.
Breaches seen in the wild
- tj-actions/changed-files compromise 2025: A stolen bot token let attackers poison tj-actions/changed-files so pipelines printed their CI/CD secrets to public logs (CVE-2025-30066).
Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
Crown-jewel data governance fails when organisations protect repositories more tightly than workflows. The real security boundary is the chain of handoffs, validations, and approvals that move information through the business. When those steps are weak, compliance may still look acceptable while the operational process remains fragile. Practitioners should treat movement, not storage, as the primary risk surface.
Identity assurance is the missing control in most data supply chains. A workflow cannot be trusted if the organisation cannot tell who is acting at each step, whether that actor is appropriate, and whether the information has changed in transit. That makes identity verification part of data protection, not a separate discipline. For security leaders, the practical conclusion is to govern access decisions at the point of handoff.
Digital certificates are becoming a trust mechanism for business process integrity, not just transport security. They help bind actions to verified parties and support secure exchange across systems that do not share a common operational context. That matters most when the data itself has business or safety value. The implication for practitioners is to manage certificate trust chains as part of workflow governance, not as a back-end technical detail.
Digital trust is a more useful board-level concept than compliance alone. Compliance answers whether minimum obligations are met, but trust asks whether the workflow remains reliable, understandable, and usable under pressure. That distinction matters when customer experience, speed, and integrity all drive business outcomes. Security teams should present crown-jewel protection as a resilience and value-preservation issue, not only a regulatory one.
From our research library:
- Business leaders plan to spend $124 million on average on AI in 2026, and 91% say data security and risk will shape their AI strategy.
What this signals
Workflow trust becomes the deciding control. As organisations digitise more customer and operational journeys, the security question shifts from whether a vault is hardened to whether every exchange is trustworthy. That makes identity assurance, certificate governance, and integrity checks central to data resilience, especially where sensitive information is repeatedly reused across systems.
Process integrity now matters as much as confidentiality. A workflow that preserves secrecy but loses accuracy or provenance still creates risk, because bad data can drive bad decisions. Security programmes should therefore measure whether a business process remains safe to use, not only whether it remains hard to penetrate.
For practitioners
- Define crown-jewel workflows before controls Identify the workflows where critical data is created, transformed, shared, or relied on, then mark each step where trust can fail.
- Verify identities at each handoff Require step-specific identity assurance for users, services, and third parties before data can move to the next stage.
- Map secure channels across the data supply chain Document which channels carry sensitive information, which protections each one uses, and where integrity checks must occur.
- Treat certificate lifecycle as workflow governance Track issuance, renewal, revocation, and trust-chain ownership for certificates that protect critical exchanges.
- Frame trust controls in business terms Translate workflow risk into customer experience, operational resilience, and business continuity so the board can evaluate trade-offs clearly.
Key takeaways
- Crown-jewel protection fails when security focuses on storage while leaving workflow handoffs under-governed.
- Identity verification and channel trust are part of data security because they determine whether information remains reliable in motion.
- Security teams should treat data flows, certificate trust, and step-by-step integrity as core governance issues rather than back-end implementation details.
Related NHI Mgmt Group resources: Data Security Guide · Crown jewels analysis · Insider Data Theft Guide · Data Exfiltration Playbook
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0, CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | PR.AA-05 — Access Permissions, Entitlements and Authorizations | The article centres on trusted access at each data handoff, which is an authorisation problem. |
| Recommendation — Apply PR.AA-05 to ensure each workflow step grants only the access needed for that transaction. | ||
| CIS Controls v8 | CIS-5 — Account Management | The article depends on knowing which identities can act within each workflow stage. |
| Recommendation — Use CIS-5 to govern account scope and remove unnecessary access from workflow participants. | ||
| NIST SP 800-53 Rev 5 | IA-9 — Identification and Authentication (Non-Organizational Users) | External customers, partners, and third parties are part of the data supply chain described here. |
| IA-5 — Authenticator Management | Certificate and trust lifecycle management are central to secure data exchange in the article. | |
| Recommendation — Use IA-9 to authenticate non-organizational identities before they touch sensitive workflow data. Apply IA-5 to manage issuance, renewal, and revocation for workflow authenticators. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | The article's trust-first approach depends on consistent access control across business processes. |
| Recommendation — Use A.5.15 to enforce access decisions that match the sensitivity of each data flow. | ||
Key terms
- Data Supply Chain: The data supply chain is the end-to-end path data follows from creation or collection through storage, processing, movement, use, and disposal. It includes people, systems, integrations, and controls that handle data at each stage. In security analysis, it defines where trust, integrity, provenance, and exposure can change.
- Digital Trust: Digital trust is the set of cryptographic and identity controls that allow systems, users, and services to verify each other reliably. It includes PKI, federation, certificates, and authentication foundations that must remain adaptable as technologies and threat conditions change.
- Identity Assurance: The confidence an organisation has that a person or system is truly who it claims to be before access or action is granted. In modern IAM, assurance depends on evidence quality, channel trust, and the strength of verification around high-risk decisions.
- Digital certificate: A cryptographic credential issued for a defined period that can be used to prove identity during authentication. It supports stronger, time-bound access control, but only when issuance, renewal, and revocation are managed as part of the identity lifecycle.
Deepen your knowledge
NHI Foundation Level course covers NHI governance, machine identity security, and secrets management through the industry's only accredited NHI security programme. It helps security and identity practitioners connect workflow trust to the controls that govern access, verification, and accountability.
Published by the NHIMG editorial team on November 6, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org