All Resources
In this article:
minus iconplus icon
Share the Blog

Understanding Data Movement to Avert Proliferation Risks

April 10, 2024
4
Min Read
Data Sprawl

Understanding the perils your cloud data faces as it proliferates throughout your organization and ecosystems is a monumental task in the highly dynamic business climate we operate in. Being able to see data as it is being copied and travels, monitor its activity and access, and assess its posture allows teams to understand and better manage the full effect of data sprawl.

 

It ‘connects the dots’ for security analysts who must continually evaluate true risks and threats to data so they can prioritize their efforts. Data similarity and movement are important behavioral indicators in assessing and addressing those risks. This blog will explore this topic in depth.

What Is Data Movement

Data movement is the process of transferring data from one location or system to another – from A to B. This transfer can be between storage locations, databases, servers, or network locations. Copying data from one location to another is simple, however, data movement can get complicated when managing volume, velocity, and variety.

  • Volume: Handling large amounts of data.
  • Velocity: Overseeing the pace of data generation and processing.
  • Variety: Managing a variety of data types.

How Data Moves in the Cloud

Data is free and can be shared anywhere. The way organizations leverage data is an integral part of their success. Although there are many business benefits to moving and sharing data (at a rapid pace), there are also many concerns that arise, mainly dealing with privacy, compliance, and security. Data needs to move quickly, securely, and have the proper security posture at all times.  

These are the main ways that data moves in the cloud:

1. Data Distribution in Internal Services: Internal services and applications manage data, saving it across various locations and data stores.

2. ETLs: Extract, Transform, Load processes, involve combining data from multiple sources into a central repository known as a data warehouse. This centralized view supports applications in aggregating diverse data points for organizational use.

3. Developer and Data Scientist Data Usage: Developers and data scientists utilize data for testing and development purposes. They require both real and synthetic data to test applications and simulate real-life scenarios to drive business outcomes.

4. AI/ML/LLM and Customer Data Integration: The utilization of customer data in AI/ML learning processes is on the rise. Organizations leverage such data to train models and apply the results across various organizational units, catering to different use-cases.

What Is Misplaced Data

"Misplaced data" refers to data that has been moved from an approved environment to an unapproved environment. For example, a folder that is stored in the wrong location within a computer system or network. This can result from human error, technical glitches, or issues with data management processes.

 

When unauthorized data is stored in an environment that is not designed for the type of data, it can lead to data leaks, security breaches, compliance violations, and other negative outcomes.

With companies adopting more cloud services, and being challenged with properly managing the subsequent data sprawl, having misplaced data is becoming more common, which can lead to security, privacy, and compliance issues.

The Challenge of Data Movement and Misplaced Data

Organizations strive to secure their sensitive data by keeping it within carefully defined and secure environments. The pervasive data sprawl faced by nearly every organization in the cloud makes it challenging to effectively protect data, given its rapid multiplication and movement.

It is encouraged for business productivity to leverage data and use it for various purposes that can help enhance and grow the business. However, with the advantages, come disadvantages. There are risks to having multiple owners and duplicate data..

To address this challenge, organizations can leverage the analysis of similar data patterns to gain a comprehensive understanding on how data flows within the organization and help security teams first get visibility of those movement patterns, and then identify whether this movement is authorized. Then they can protect it accordingly and understand which unauthorized movement should be blocked.

This proactive approach allows them to position themselves strategically. It can involve ensuring robust security measures for data at each location, re-confining it by relocating, or eliminating unnecessary duplicates. Additionally, this analytical capability proves valuable in scenarios tied to regulatory and compliance requirements, such as ensuring GDPR - compliant data residency.

 Identifying Redundant Data and Saving Cloud Storage Costs

The identification of similarities empowers Chief Information Security Officers (CISOs) to implement best practices, steering clear of actions that lead to the creation of redundant data.

Detecting redundant data helps reduce cloud storage costs and drive up operational efficiency from targeted and prioritized remediation efforts that focus on the critical data risks that matter. 

This not only enhances data security posture, but also contributes to a more streamlined and efficient data management strategy.

“Sentra has helped us to reduce our risk of data breaches and to save money on cloud storage costs.”

-Benny Bloch, CISO at Global-e

Security Concerns That Arise

  1. Data Security Posture Variations Across Locations: Addressing instances where similar data, initially secure, experiences a degradation in security posture during the copying process (e.g., transitioning from private to public, or from encrypted to unencrypted).
  1. Divergent Access Profiles for Similar Data: Exploring scenarios where data, previously accessible by a limited and regulated set of identities, now faces expanded access by a larger number of identities (users), resulting in a loss of control.
  1. Data Localization and Compliance Violations: Examining situations where data, mandated to be localized in specific regions, is found to be in violation of organizational policies or compliance rules (with GDPR as a prominent example). By identifying similar sensitive data, we can pinpoint these issues and help users mitigate them.
  1. Anonymization Challenges in ETL Processes: Identifying issues in ETL processes where data is not only moved but also anonymized. Pinpointing similar sensitive data allows users to detect and mitigate anonymization-related problems.
  1. Customer Data Migration Across Environments: Analyzing the movement of customer data from production to development environments. This can be used by engineers to test real-life use-cases.
  2. Data Data Democratization and Movement Between Cloud and Personal Stores: Investigating instances where users export data from organizational cloud stores to personal drives (e.g., OneDrive) for purposes of development, testing, or further business analysis. Once this data is moved to personal data stores, it typically is less secure. This is due to the fact that these personal drives are less monitored and protected, and in control of the private entity (the employee), as opposed to the security/dev teams. These personal drives may be susceptible to security issues arising from misconfiguration, user mistakes or insufficient knowledge.

How Sentra’s DSPM Helps Navigate Data Movement Challenges

  1. Discover and accurately classify the most sensitive data and provide extensive context about it, for example:
  • Where it lives
  • Where it has been copied or moved to
  • Who has access to it
  1. Highlight misconfigurations by correlating similar data that has different security posture. This helps you pinpoint the issue and adjust it according to the right posture.
  2. Quickly identify compliance violations, such as GDPR - when European customer data moves outside of the allowed region, or when financial data moves outside a PCI compliant environment.
  3. Identify access changes, which helps you to understand the correct access profile by correlating similar data pieces that have different access profiles.

For example, the same data is well kept in a specific environment and can be accessed by 2 very specific users. When the same data moves to a developers environment, it can then be accessed by the whole data engineering team, which exposes more risks.

Leveraging Data Security Posture Management (DSPM) and Data Detection and Response (DDR) tools proves instrumental in addressing the complexities of data movement challenges. These tools play a crucial role in monitoring the flow of sensitive data, allowing for the swift remediation of exposure incidents and vulnerabilities in real-time. The intricacies of data movement, especially in hybrid and multi-cloud deployments, can be challenging, as public cloud providers often lack sufficient tooling to comprehend data flows across various services and unmanaged databases.

 

Our innovative cloud DLP tooling takes the lead in this scenario, offering a unified approach by integrating static and dynamic monitoring through DSPM and DDR. This integration provides a comprehensive view of sensitive data within your cloud account, offering an updated inventory and mapping of data flows. Our agentless solution automatically detects new sensitive records, classifies them, and identifies relevant policies. In case of a policy violation, it promptly alerts your security team in real time, safeguarding your crucial data assets.

In addition to our robust data identification methods, we prioritize the implementation of access control measures. This involves establishing Role-based Access Control (RBAC) and Attribute-based Access Control (ABAC) policies, so that the right users have permissions at the right times.

Identifying data movement with Sentra

Identifying Data Movement With Sentra

Sentra has developed different methods to identify data movements and similarities based on the content of two assets. Our advanced capabilities allow us to pinpoint fully duplicated data, identify similar data, and even uncover instances of partially duplicated data that may have been copied or moved across different locations. 

Moreover, we recognize that changes in access often accompany the relocation of assets between different locations. 

As part of Sentra’s Data Security Posture Management (DSPM) solution, we proactively manage and adapt access controls to accommodate these transitions, maintaining the integrity and security of the data throughout its lifecycle.

These are the 3 methods we are leveraging:

  1. Hash similarity - Using each asset unique identifier to locate it across the different data stores of the customer environment.
  2. Schema similarity - Locate the exact or similar schemas that indicated that there might be similar data in them and then leverage other metadata and statistical methods to simplify the data and find necessary correlations.
  3. Entity Matching similarity - Detects when parts of files or tables are copied to another data asset. For example, an ETL that extracts only some columns from a table into a new table in a data warehouse. 

Another example would be if PII is found in a lower environment, Sentra could detect if this is real or mock customer PII, based on whether this PII was also found in the production environment.

PII found in a lower environment

Conclusion

Understanding and managing data sprawl are critical tasks in the dynamic business landscape. Monitoring data movement, access, and posture enable teams to comprehend the full impact of data sprawl, connecting the dots for security analysts in assessing true risks and threats. 

Sentra addresses the challenge of data movement by utilizing advanced methods like hash, schema, and entity similarity to identify duplicate or similar data across different locations. Sentra's holistic Data Security Posture Management (DSPM) solution not only enhances data security but also contributes to a streamlined data management strategy. 

The identified challenges and Sentra's robust methods emphasize the importance of proactive data management and security in the dynamic digital landscape.

To learn more about how you can enhance your data security posture, schedule a demo with one of our experts.

<blogcta-big>

Ran is a passionate product and customer success leader with over 12 years of experience in the cybersecurity sector. He combines extensive technical knowledge with a strong passion for product innovation, research and development (R&D), and customer success to deliver robust, user-centric security solutions. His leadership journey is marked by proven managerial skills, having spearheaded multidisciplinary teams towards achieving groundbreaking innovations and fostering a culture of excellence. He started at Sentra as a Senior Product Manager and is currently the Head of Technical Account Management, located in NYC.

Subscribe

Latest Blog Posts

Nikki Ralston
Nikki Ralston
Romi Minin
Romi Minin
March 23, 2026
4
Min Read

How to Protect Sensitive Data in Azure

How to Protect Sensitive Data in Azure

As organizations migrate critical workloads to the cloud in 2026, understanding how to protect sensitive data in Azure has become a foundational security requirement. Azure offers a deeply layered security architecture spanning encryption, key management, data loss prevention, and compliance enforcement. This article breaks down each layer with technical precision, so security teams and architects can make informed decisions about safeguarding their most valuable data assets.

Azure Data Protection: A Layered Security Model

Azure's approach to data protection relies on multiple overlapping controls that work together to prevent unauthorized access, accidental modification, and data loss.

Storage-Level Encryption and Access Controls

Azure Storage Service Encryption (SSE) and Azure disk encryption options automatically protect data using AES-256, meeting FIPS 140-2 compliance standards across core services such as Azure Storage, Azure SQL Database, and Azure Data Lake.

All managed disks, snapshots, and images are encrypted by default using SSE with service-managed keys, and organizations can switch to customer-managed keys (CMKs) in Azure Key Vault when they need tighter control.

Azure Resource Manager locks, available in CanNotDelete and ReadOnly modes, prevent accidental deletion or configuration changes to critical storage accounts and other resources.

Immutability, Recovery, and Redundancy

  • Immutability policies on Azure Blob Storage ensure data cannot be overwritten or deleted once written, which is valuable for regulatory compliance scenarios like financial records or audit logs.
  • Soft delete retains deleted containers, blobs, or file shares in a recoverable state for a configurable period.
  • Blob versioning and point-in-time restore allow rollback to earlier states to recover from logical corruption or accidental changes.
  • Redundancy options, including LRS, ZRS, and cross-region options like GRS/GZRS—protect against hardware failures and regional outages.

Microsoft Defender for Storage further strengthens this model by detecting suspicious access patterns, malicious file uploads, and potential data exfiltration attempts across storage accounts.

Azure Encryption at Rest and in Transit

Encryption at Rest

Azure uses an envelope encryption model where a Data Encryption Key (DEK) encrypts the actual data, while a Key Encryption Key (KEK) wraps the DEK. For customer-managed scenarios, KEKs are stored and managed in Azure Key Vault or Managed HSM, while platform-managed keys are handled by Microsoft.

AES-256 is the default encryption algorithm across Azure Storage, Azure SQL Database, and Azure Data Lake for server-side encryption.

Transparent Data Encryption (TDE) applies this protection automatically for Azure SQL Database and Azure Synapse Analytics data files, encrypting data and log files in real time using a DEK protected by a key hierarchy that can include customer-managed keys.

For compute, encryption at host provides end-to-end encryption of VM data—including temporary disks, ephemeral OS disks, and disk caches - before it’s written to the underlying storage, and is Microsoft’s recommended option going forward as Azure Disk Encryption is phased out over time.

Encryption in Transit

Azure enforces modern transport-level encryption across its services:

  • TLS 1.2 or later is required for encrypted connections to Azure services, with many services already enforcing TLS 1.2+ by default.
  • HTTPS is mandatory for Azure portal interactions and can be enforced for storage REST APIs through the “secure transfer required” setting on storage accounts.
  • Azure Files uses SMB 3.0 with built-in encryption for file shares.
  • At the network layer, MACsec (IEEE 802.1AE) encrypts traffic between Azure datacenters, providing link-layer protection for traffic that leaves a physical boundary controlled by Microsoft.
  • Azure VPN Gateways support IPsec/IKE (site-to-site) and SSTP (point-to-site) tunnels for hybrid connectivity, encrypting traffic between on-premises and Azure virtual networks.
  • For sensitive columns in Azure SQL Database, Always Encrypted ensures data is encrypted within the client application before it ever reaches the database server.

A simplified view:

Scenario Encryption Method Algorithm / Protocol
Storage (blobs, files, disks) Azure Storage Service Encryption AES-256 (FIPS 140-2)
Databases Transparent Data Encryption (TDE) AES-256 + RSA-2048 (CMK)
Virtual machine disks Encryption at host / Azure Disk Encryption AES-256 (PMK or CMK)
Data in transit (services) TLS/HTTPS TLS 1.2+
Data center interconnects MACsec IEEE 802.1AE
Hybrid connectivity VPN Gateway IPsec/IKE, SSTP

Azure Key Vault and Advanced Key Management

Encryption is only as strong as the key management strategy behind it. Azure Key Vault, Managed HSM, and related HSM offerings are the central services for storing and managing cryptographic keys, secrets, and certificates.

Key options include:

  • Service-managed keys (SMK): Microsoft handles key generation, rotation, and backup transparently. This is the default for many services and minimizes operational overhead.
  • Customer-managed keys (CMK): Organizations manage key lifecycles, rotation schedules, access policies, and revocation in Key Vault or Managed HSM, and can bring their own keys (BYOK).
  • Hardware Security Modules (HSMs): Tamper-resistant hardware key storage for workloads that require FIPS 140-2 Level 3-style assurance, common in financial services and healthcare.

Azure supports automatic key rotation policies in Key Vault, reducing the operational burden of manual rotation. When using CMKs with TDE for Azure SQL Database, a Key Vault key (commonly RSA-2048) serves as the KEK that protects the DEK, adding a layer of customer-controlled governance to database encryption.

Azure Encryption at Host for Virtual Machines

Encryption at host extends Azure’s encryption coverage down to the VM host layer, ensuring that:

  • Temporary disks, ephemeral OS disks, and disk caches are encrypted before they’re written to physical storage.
  • Encryption is applied at the Azure infrastructure level, with no changes to the guest OS or application stack required.
  • It supports both platform-managed keys and customer-managed keys via Key Vault, including automatic rotation.

This model is particularly important for regulated workloads (e.g., EHR systems, payment processing, or financial transaction logs) where even transient data on caches or temporary disks must be protected. It also reduces the risk of configuration drift that can occur when encryption is managed individually at the OS or application layer. As Azure Disk Encryption is gradually retired, encryption at host is the recommended default for new VM-based workloads.

Data Loss Prevention in and Around Azure

Encryption protects data at rest and in transit, but it does not prevent authorized users from mishandling or leaking sensitive information. That’s the role of data loss prevention (DLP).

In Microsoft’s ecosystem, DLP is primarily delivered through Microsoft Purview Data Loss Prevention, which applies policies across:

  • Microsoft 365 services such as Exchange Online, SharePoint Online, OneDrive, and Teams
  • Endpoints via endpoint DLP
  • On-premises repositories and certain third-party cloud apps through connectors and integration with Microsoft Defender and Purview capabilities

How DLP Policies Work

DLP policies use automated content analysis - keyword matching, regular expressions, and machine learning-based classifiers - to detect sensitive information such as financial records, health data, and PII. When a violation is detected, policies can:

  • Warn users with policy tips
  • Require justification
  • Block sharing, copying, or uploading actions
  • Trigger alerts and incident workflows for security and compliance teams

Policies can initially run in simulation/audit mode so teams can understand impact before switching to full enforcement.

DLP and AI / Azure Workloads

For AI workloads and Azure services, DLP is part of a broader control set:

  • Purview DLP governs content flowing through Microsoft 365 and integrated services that may feed AI assistants and copilots.
  • On Azure resources such as Azure OpenAI, you use a combination of:
    • Network restrictions (restrictOutboundNetworkAccess, private endpoints, NSGs, and firewalls) to prevent services from calling unauthorized external endpoints.
    • Microsoft Defender for Cloud policies and recommendations for monitoring misconfigurations, exposed endpoints, and suspicious activity.
    • Audit logging to verify that sensitive data is not being transmitted where it shouldn’t be.

Together, these capabilities give you both content-centric controls (DLP) and infrastructure-level controls (network and posture management) for AI workloads.

Compliance, Monitoring, and Ongoing Governance

Meeting regulatory requirements in Azure demands continuous visibility into where sensitive data lives, how it moves, and who can access it.

  • Azure Policy enforces configuration baselines at scale: ensuring encryption is enabled, secure transfer is required, TLS versions are restricted, and storage locations meet regional requirements.
  • For GDPR, you can use policy to restrict data storage to approved EU regions; for HIPAA, you enforce audit logging, encryption, and access controls on systems that handle PHI.
  • Periodic audits should verify:
    • Encryption is enabled across all storage accounts and databases.
    • Key rotation schedules for CMKs are in place and adhered to.
    • DLP policies cover intended data types and locations.
    • Role-based access control (RBAC) and Privileged Identity Management (PIM) are used to maintain least-privilege access.

Azure Monitor and Microsoft Defender for Cloud provide real-time visibility into encryption status, access anomalies, misconfigurations, and policy violations across your subscriptions.

How Sentra Complements Azure's Native Controls

Sentra is a cloud-native data security platform that discovers and governs sensitive data at petabyte scale directly inside your Azure environment - data never leaves your control. It provides complete visibility into:

  • Where sensitive data actually resides across Azure Storage, databases, SaaS integrations, and hybrid environments
  • How that data moves between services, regions, and environments, including into AI training pipelines and copilots
  • Who and what has access, and where excessive permissions or toxic combinations put regulated data at risk

Sentra’s AI-powered discovery and classification engine integrates with Microsoft’s ecosystem to:

  • Feed high-accuracy labels and data classes into tools like Microsoft Purview DLP, improving policy effectiveness
  • Enforce data-driven guardrails that prevent unauthorized AI access to sensitive data
  • Identify and help eliminate shadow, redundant, obsolete, or trivial (ROT) data, typically reducing cloud storage costs by around 20% while shrinking the overall attack surface.

Knowing how to protect sensitive data in Azure is not a one-time configuration exercise; it is an ongoing discipline that combines strong encryption, disciplined key management, proactive data loss prevention, and continuous compliance monitoring. Organizations that treat these controls as interconnected layers rather than isolated features will be best positioned to meet current regulatory demands and the emerging security challenges of widespread AI adoption.

<blogcta-big>

Read More
Ron Reiter
Ron Reiter
March 17, 2026
3
Min Read

Specialized File Format Scanning: DICOM, Tableau, Pickle, and the “We Don’t Scan That” Problem

Specialized File Format Scanning: DICOM, Tableau, Pickle, and the “We Don’t Scan That” Problem

Most security programs are pretty comfortable talking about PDFs, Office documents, and maybe CSVs. But when I ask, “What are you doing about DICOM, EDI, Tableau extracts, pickle files, OneNote notebooks, Draw.io diagrams, and Java KeyStores?” the room usually goes quiet.

The truth is that some of the highest‑risk data stores in your environment live in specialized file formats that traditional DLP and DSPM tools were never designed to understand. If your platform shrugs and treats them as opaque blobs, you’re ignoring exactly the data regulators and attackers care about most.

This blog post looks at why specialized file format scanning matters for DICOM, EDI, Tableau extracts, pickle/joblib, OneNote, Draw.io, Java KeyStores, and LST catalogs, and how making them first‑class citizens in your DSPM program closes a huge visibility gap.

DICOM PHI Scanning: Medical Images That Aren’t “Just Images”

Let’s start with healthcare. In modern environments, nearly every CT, MRI, and X‑ray is stored as DICOM.

To many teams, that’s “just imaging,” but DICOM is actually a rich container: it carries patient names, dates of birth, medical record numbers, referring physicians, institution IDs, sometimes even Social Security numbers and insurance details, all in structured metadata alongside the image.

When those files get exported from tightly controlled PACS systems to research shares, cloud buckets, or AI training pipelines, that PHI comes along for the ride, often without any visibility from security.

Sentra’s DICOM reader pulls those metadata fields into tabular form so we can classify PHI wherever it shows up, not just in EHR databases. Instead of “DICOM = image, ignore,” you get structured visibility into the actual identifiers inside each file.

EDI File Scanning: Healthcare Transactions You Can Finally See

The same story plays out in EDI healthcare transactions. EDI 837s, 835s, and related formats are packed with patient demographics, diagnosis and procedure codes, insurance identifiers, and payment details. These files routinely move between providers, payers, and vendors, land in staging buckets, get archived, and quietly drift out of scope. They’re not human‑readable, so they’re also not on most security teams’ radar.

We built an EDI parser specifically to turn those streams into structured data we can classify, so “EDI” stops being shorthand for “we hope that system is locked down.” With specialized EDI scanning in place, you can actually answer:

  • Where do our 837/835 files live across cloud storage and file shares?
  • Which of them contain regulated PHI and payment data?
  • Who has access, and are they stored in the right geography?

Tableau Extract Scanning: Shadow Data in TDE and Hyper

In analytics, Tableau extracts (TDE/Hyper) are the poster child for shadow data. When an analyst pulls a subset of a production database into a local extract, they’ve just created a new, often uncontrolled copy of that data. Customer records, transaction histories, compensation data - whatever they could query is now sitting in a file that can be emailed, synced, uploaded, and forgotten.

Sentra’s Tableau readers crack open TDE and Hyper, extract the tables, and run the same classification we use on your core data stores. For SOX, financial data governance, and general cloud data security, that’s the only way to have an honest inventory of where your financial and customer data actually lives.

Instead of “Tableau extracts somewhere in that EC2 or S3 bucket,” you get:

  • A clear map of which extracts exist
  • Exactly which columns carry PII, PCI, or sensitive business data
  • Visibility into who can access those shadow datasets

Pickle and Joblib Scanning: Seeing Inside ML and AI Artifacts

In modern ML and AI pipelines, formats like Python’s pickle and scikit‑learn’s joblib are everywhere.

They’re not just “model files”; they frequently contain:

  • Serialized DataFrames
  • Cached training samples
  • Feature stores

All of which can embed PII, financial data, or PHI from the datasets you used to build your models.

As AI governance and model transparency requirements tighten, having zero visibility into what’s baked into those artifacts isn’t tenable. You need to be able to answer questions like:

  • What real data did we use to train this model?
  • Did any regulated data sneak into training samples or feature stores?

Sentra extracts both tabular and textual content from pickle and joblib so you can finally treat ML artifacts as governed data stores, not opaque byproducts. That’s the basis for answering, with evidence, what data you actually trained on.

OneNote, Draw.io, Java KeyStores, and LST: Everyday Tools, High Impact Risk

Even day‑to‑day productivity tools become risk multipliers when you can’t see inside them.

OneNote Notebook Scanning

OneNote notebooks are used for:

  • Meeting notes
  • Project docs
  • Onboarding checklists
  • Internal knowledge bases

Which means they tend to accumulate customer details, credentials, financial numbers, and strategy discussions in an unstructured, nested hierarchy. Without specialized OneNote scanning, those notebooks become an ungoverned archive of PII, secrets, and sensitive business context living in SharePoint, OneDrive, or exported file shares.

Draw.io Diagram Scanning

Draw.io diagrams are full of labels that reference:

  • Server names and IP ranges
  • Database identifiers
  • Customer names and environments

Treating .drawio files as “just diagrams” misses the fact that they often encode both network topology and customer context in plain text. With a dedicated reader, those labels flow through the same classification as any other unstructured text.

Java KeyStore (JKS) Scanning

Java KeyStore (JKS) files hold keys and certificates - the crown jewels of many Java and Spring applications.

You might already inventory them for crypto hygiene, but they also matter for data security posture:

  • Where are private keys stored?
  • Are keystores sitting in publicly reachable locations or over‑permissive buckets?
  • Which identities and apps are effectively protected by (or exposed through) those keystores?

Bringing JKS into your DSPM coverage means you can correlate where keys live with where your most sensitive data lives and moves.

LST Catalog Scanning

LST catalogs quietly index sensitive entities across systems in tabular form, essentially acting as cross‑system indexes of important IDs, records, or objects.

Scanning LST files as structured tables, rather than raw text, lets you:

  • Identify when sensitive IDs or mappings are being replicated into uncontrolled locations
  • Tie those catalog entries back to regulated source systems

Why Specialized File Format Scanning Is Not an Edge Case

None of these formats are edge cases. For healthcare, financial services, and AI‑heavy organizations, they sit squarely in the blast radius of your biggest risks:

  • DICOM & EDI: PHI and claims data well inside HIPAA and regional healthcare regulations
  • Tableau extracts: Financial, customer, and HR data copied into BI workflows—critical for SOX and privacy regimes
  • Pickle/joblib: Training data and features embedded in ML artifacts—central to emerging AI regulations
  • OneNote, Draw.io, JKS, LST: The connective tissue of how your infrastructure and customer data are actually used day‑to‑day

That’s why Sentra’s extraction engine supports 150+ file types and treats specialized formats as first‑class citizens in your DSPM program, not as “we’ll get to that later” backlog items.

From Opaque Blobs to Governed Data: How Sentra Helps

Sensitive data doesn’t respect format boundaries, and neither can your visibility. With Sentra’s specialized file format scanning, you can discover formats like DICOM, EDI, Tableau extracts, pickle/joblib, OneNote, Draw.io, JKS, LST, and more across S3, Azure Blob, GCS, file shares, and SaaS environments. Sentra goes beyond surface metadata by parsing and extracting the true structure and content - both tabular and unstructured - so you can accurately classify PHI, PCI, PII, secrets, and sensitive business data at the level where it actually lives, such as fields, columns, and labels.

All of this is integrated into the same DSPM policies you already apply to databases, data lakes, and email archives. If you want to understand how this specialized format coverage fits into Sentra’s broader AI-ready data security and governance approach, you can explore the data security platform overview at sentra.io or connect with us to discuss your specific stack and file formats. After all, the most dangerous data is often hiding in the files your tools still ignore.

<blogcta-big>

Read More
Nikki Ralston
Nikki Ralston
David Stuart
David Stuart
March 17, 2026
4
Min Read

Best Cloud Data Security Solutions for 2026

Best Cloud Data Security Solutions for 2026

As enterprises scale cloud workloads and AI initiatives in 2026, cloud data security has become a board‑level priority. Regulatory frameworks are tightening, AI assistants are touching more systems, and sensitive data now spans IaaS, PaaS, SaaS, data lakes, and on‑prem.

This guide compares four of the leading cloud data security solutions - Sentra, Wiz, Prisma Cloud, and Cyera - across:

  • Architecture and deployment
  • Data movement and “toxic combination” detection
  • AI risk coverage and Copilot/LLM governance
  • Compliance automation and real‑world user sentiment

Platform Core Strength Deployment Model AI & Data Risk Coverage
Sentra In-environment DSPM and AI-aware data governance, with strong focus on regulated data and unstructured stores Purely agentless, in-place scanning in your cloud and data centers; optional lightweight on-prem scanners for file shares and databases Shadow AI detection, M365 Copilot and AI agent inventory, data-flow mapping into AI pipelines, and guardrails for cloud and SaaS data
Wiz Cloud-native CNAPP and Security Graph tying together data, identity, and cloud posture Primarily agentless via cloud provider APIs and snapshots, with optional eBPF sensor for runtime context Data lineage into AI pipelines via its security graph; AI exposure surfaced alongside misconfigurations and identity risk
Prisma Cloud Code-to-cloud security, infrastructure risk, and compliance across multi-cloud Hybrid: agentless scanning plus optional agents/sidecars for deep runtime protection Tracks data movement into AI pipelines as part of attack-path analysis and compliance checks
Cyera AI-native data discovery with converged DLP + DSPM for cloud data Agentless, in-place scanning using local inspection or snapshots AISPM and AI runtime protection for prompts, responses, and agents across SaaS and cloud environments

What Users Are Saying

Review platforms and field conversations surface patterns that go beyond feature matrices.

Sentra

Pros

  • Strong shadow data discovery, including legacy exports, backups, and unstructured sources like chat logs and call transcripts that other tools often miss
  • Built‑in compliance facilitation that reduces audit prep time for healthcare, financial services, and other regulated industries
  • In‑environment architecture that consistently appeals to privacy, risk, and data protection teams concerned about data residency and vendor data handling

Cons

  • Dashboards and reporting are powerful but can feel dense for first‑time users who aren’t familiar with DSPM concepts
  • Third‑party integrations are broad, but some connectors can lag when synchronizing very large environments

Wiz

Pros

  • Excellent multi‑cloud visibility and security graph that correlate misconfigurations, identities, and data assets for fast remediation
  • Well‑regarded customer success and responsive support teams

Cons

  • High alert volume if policies aren’t carefully tuned, which can overwhelm small teams
  • Configuration complexity grows with environment size and number of integrations

Prisma Cloud

Pros

  • Strong real‑time threat detection tightly coupled with major cloud providers, well suited to security operations teams
  • Proven scalability across large, hybrid environments combining containers, VMs, and serverless workloads

Cons

  • Cost is frequently cited as a concern in large‑scale deployments
  • Steeper learning curve that often requires dedicated training and ownership

Cyera

Pros

  • Smooth, agentless deployment with quick time‑to‑value for data discovery in cloud stores
  • Highly responsive support and strong focus on classification quality

Cons

  • Integration and operationalization complexity in larger enterprises, especially when folding into wider security workflows
  • Some backend customization and tuning require direct vendor involvement

Cloud Data Security Platforms: Architecture and Deployment

How a platform scans your data is as important as what it finds. Sending production data to a third‑party cloud for analysis can introduce its own risk, and regulators increasingly expect clear answers on where data is processed.

Sentra: In‑Environment DSPM for Regulated and AI‑Ready Data

Sentra takes a data‑first, in‑environment approach:

  • Agentless connectors to cloud provider APIs and SaaS platforms mean sensitive content is scanned inside your accounts; it is never copied to Sentra’s cloud.
  • Lightweight on‑prem scanners extend coverage to file shares and databases, creating a unified view across IaaS, PaaS, SaaS, and on‑prem systems.

This design makes Sentra particularly attractive to organizations with strict data residency requirements and privacy‑driven governance models, especially in finance, healthcare, and other regulated sectors.

Wiz: Agentless CNAPP with Optional Runtime Sensors

Wiz is fundamentally agentless, connecting to cloud environments via APIs and leveraging temporary snapshots for inspection.

  • An optional eBPF‑based sensor adds runtime visibility for workloads without introducing inline latency.
  • The same security graph model underpins both infrastructure risk and emerging data/AI lineage features.

Prisma Cloud: Hybrid Agentless + Agent Model

Prisma Cloud combines:

  • Agentless scanning for vulnerabilities, misconfigurations, and compliance posture.
  • Optional agents or sidecars when deep runtime protection or granular workload telemetry is required.

This hybrid approach offers powerful coverage, but introduces more operational overhead than purely agentless DSPM platforms like Sentra and Cyera.

Cyera: In‑Place Cloud Data Inspection

Cyera focuses on in‑place data inspection, using local snapshots or direct connections to datastore APIs.

  • Sensitive data is analyzed within your environment rather than being shipped to a vendor cloud.
  • This aligns well with privacy‑first architectures that treat any external data processing as a risk to be minimized.

Identifying Toxic Combinations and Tracking Data Movement

Static discovery like, “here are your S3 buckets” is a basic capability. Real security value comes from correlating data sensitivity, effective access, and how data moves over time across clouds, regions, and environments.

Sentra: Data‑Aware Risk and End‑to‑End Data Flow Visibility

Sentra continuously maps your entire data estate, correlating classification results with IAM, ACLs, and sharing links to surface “toxic combinations” - high‑sensitivity data behind overly broad permissions.

  • Tracks data movement across ETLs, database migrations, backups, and AI pipelines so you can see when production data drifts into dev, test, or unapproved regions.
  • Extends beyond primary databases to cover data lakes, analytics platforms, and modern big‑data formats in object storage, which are increasingly used as AI training inputs.

This gives security and data teams a living map of where sensitive data actually lives and how it moves, not just a static list of storage locations.

Wiz: Security Graph and CIEM

Wiz’s Security Graph maps identities, resources, configurations, and data stores in one model.

  • Its CIEM capabilities aggregate effective permissions (including inherited policies and group memberships) to highlight over‑exposed data resources.
  • Wiz tracks data lineage into AI pipelines as part of its broader cloud risk view, helping teams understand where sensitive data intersects with ML workloads.

Prisma Cloud: Graph‑Based Attack Paths

Prisma Cloud uses a graph‑based risk engine to continuously simulate attack paths:

  • Seemingly low‑risk misconfigurations and broad permissions are combined to identify chains that could expose regulated data.
  • The platform generates near real‑time alerts when data crosses geofencing boundaries or flows into unapproved analytics or AI environments.

Cyera: AI‑Native Classification and LLM Validation

Cyera pairs AI‑native classification with access analysis:

  • It continuously scans structured and unstructured data for sensitive content, mapping who and what can reach each dataset.
  • An LLM‑based validation layer distinguishes real sensitive data from mock or synthetic data in dev/test, which can reduce false positives and cleanup noise.

AI Risk Detection: Shadow AI and Copilot Governance

Enterprise AI tools introduce a new class of risk: employees connecting business data to unauthorized models, or AI agents and copilots inheriting excessive access to legacy data.

Sentra: AI‑Ready Data Security and Copilot Guardrails

Sentra treats AI risk as a data problem:

  • Tracks data flows between sources and destinations and compares them against an inventory of approved AI tools, flagging when sensitive data is routed to unauthorized LLMs or agents.
  • For Microsoft 365 Copilot, Sentra builds a catalog of data across SharePoint, OneDrive, and Teams, mapping which users and groups can access each set of documents and providing guardrails before Copilot is widely rolled out.

This gives security teams a practical definition of AI data readiness: knowing exactly which data AI can see, and shrinking that blast radius before something goes wrong.

Cyera: AISPM and AI Runtime Protection

Cyera takes a dual‑layer approach to AI risk:

  • AI Security Posture Management (AISPM) inventories sanctioned and unsanctioned AI tools and maps which sensitive datasets each can access.
  • AI Runtime Protection monitors prompts, responses, and agent actions in real time, blocking suspicious activity such as data leakage or prompt‑injection attempts.

For M365 Copilot Studio, Cyera integrates with Microsoft Entra’s agent registry to track AI agents and their data scopes.

Wiz and Prisma Cloud: AI as Part of Data Lineage

Wiz and Prisma Cloud both treat AI as an extension of their data lineage and attack‑path capabilities:

  • They track when sensitive data enters AI pipelines or training environments and how that intersects with misconfigurations and identity risk.
  • However, they do not yet offer the same depth of AI‑specific governance controls and runtime protections as dedicated AI‑aware platforms like Sentra and Cyera.

Compliance Automation and Framework Mapping

For teams preparing for GDPR, HIPAA, PCI, SOC 2, or EU AI Act reviews, manually mapping findings to control sets and assembling evidence is slow and error‑prone.

Platform Approaches to Compliance

Platform Compliance Approach
Wiz Maps cloud and workload findings to 100+ built-in frameworks (including GDPR, HIPAA, and the EU AI Act).
Prisma Cloud Automates mapping to major frameworks’ control requirements with audit-ready documentation, often completing large assessments in minutes to under an hour.
Sentra Focuses on regulated data visibility and privacy-driven governance; its in-environment DSPM, classification accuracy, and reporting are frequently cited by users as key to simplifying data-centric audit prep and proving control over sensitive data. Provides petabyte-scale assessments within hours and consolidated evidence for auditors.
Cyera Provides real-time visibility and automated policy enforcement; supports compliance reporting, though public documentation is less explicit on automatic mapping to specific, named control sets.

Sentra is especially compelling when audits hinge on where regulated data actually lives and how it is governed, rather than just infrastructure posture.

Choosing Among the Best Cloud Data Security Solutions

All four platforms address real, pressing needs—but they are not interchangeable.

  • Choose Sentra if you need strict in‑environment data governance, high‑precision discovery across cloud, SaaS, and on‑prem, and AI‑aware guardrails that make Copilot and other AI deployments provably safer—without moving sensitive data out of your own infrastructure.
  • Choose Wiz if your top priority is broad cloud security coverage and a unified graph for vulnerabilities, misconfigurations, identities, and data across multi‑cloud at scale.
  • Choose Prisma Cloud if you want a code‑to‑cloud platform that ties data exposure to DevSecOps pipelines and workload runtime protection, and you have the resources to operationalize its breadth.
  • Choose Cyera if you’re focused on AI‑native classification and a converged DLP + DSPM motion for large volumes of cloud data, and you’re prepared for a more involved integration phase.

For most mature security programs, the question isn’t whether to adopt these tools but how to layer them:

  • A CNAPP for cloud infrastructure risk
  • A DSPM platform like Sentra for data‑first visibility and AI readiness
  • DLP/SSE for enforcement at egress and user edges
  • Compliance automation to translate all of that into evidence your auditors, regulators, and board can trust

Taken together, this stack lets you move faster in the cloud and with AI, without losing control of the data that actually matters.

<blogcta-big>

Read More
Expert Data Security Insights Straight to Your Inbox
What Should I Do Now:
1

Get the latest GigaOm DSPM Radar report - see why Sentra was named a Leader and Fast Mover in data security. Download now and stay ahead on securing sensitive data.

2

Sign up for a demo and learn how Sentra’s data security platform can uncover hidden risks, simplify compliance, and safeguard your sensitive data.

3

Follow us on LinkedIn, X (Twitter), and YouTube for actionable expert insights on how to strengthen your data security, build a successful DSPM program, and more!

Before you go...

Get the Gartner Customers' Choice for DSPM Report

Read why 98% of users recommend Sentra.

White Gartner Peer Insights Customers' Choice 2025 badge with laurel leaves inside a speech bubble.