[ 01 ] Products / dspm

Where does your sensitive data actually go?

dspm — sensitive data monitoring platform

Powered by eBPF, the platform analyzes inter-service traffic and connected storage, detecting security policy violations in real time.

Request a demo↗ Learn more
1 violation detected · just now

Full visibility

into different types of sensitive data

Continuous monitoring

of inter-service data transfers

Automated detection

of security policy violations

Actual data flows are more complex than the architecture diagram

In Kubernetes, new services constantly emerge, while integrations and interaction routes continuously change. Architectural diagrams, documentation and event logs don’t always show where sensitive data is actually located, which applications process it, and where it is being transmitted — so a number of data flows remain outside the control of information security.

01Incomplete data visibility

Sensitive data is distributed across services, databases and storage systems. Getting a unified picture of its flow becomes difficult.

02Unauthorized data transfers

Changes can create new routes where sensitive data is transmitted outside of authorized interactions.

03Complex incident investigations

To investigate violations, data from multiple sources must be correlated without a unified data transfer context.

[ Solution ]

dspm maps every sensitive data route automatically and ties each discovery to the service, endpoint and interaction behind it — one context instead of scattered logs.

Control not only over transfers planned by the architecture, but over the actual interactions between infrastructure components.

Request a demo↗

Sensitive data monitoring, end to end

Four capabilities, twelve functions. One platform from detection to investigation.

↖Hover over a card to see details

Sensitive Data Detection

01
dspm.sollisero / discovery
Data typesA single dictionary of sensitive data and how it spreads across your infrastructure.+ Add data type
Personal data18PII · 12 types · 1,401 fields
Payment data9PCI · 5 types · 461 fields
Secrets6Tokens · 831 fields
Data typeCategorySensitivityStoresServices
Birth dateBuilt-in detectorPIIMedium114
Driver licenseBuilt-in detectorPIIHigh32
EmailBuilt-in detectorPIIMedium169
IBANBuilt-in detectorPCIHigh73
Card numberBuilt-in detectorPCIHigh54
  • Traffic and storage analysisLocate sensitive data in inter-service requests, databases, and connected storage systems.
  • Automated classificationDetermine sensitive data types based on its content and structure.
  • Infrastructure mappingIdentify which services and storage systems contain the discovered data.
  • dspm.sollisero / discoveryOpen in product →

Inter-Service Transfer Analysis

02
dspm.sollisero / flow-map
Data mapFrom the entry point to the data store — follow the path of sensitive data.Share view
External 3
internetPublic ingress · 4 connections
payment-providerPartner API · 2 connections
partner-sftp 1 riskFile drop · 1 connection
Services 14
checkout-api 2 riskspayments · 6 connections
payments-corepayments · 3 connections
user-profileidentity · 5 connections
crm-sync 1 riskcrm · 2 connections
notification-svcplatform · 1 connection
search-indexerplatform · 2 connections
Data stores 11
PostgreSQL 6 risks3 clusters · 9 schemas
Kafkaevents-bus · 6 connections
S3 / archivecold storage · 2 connections
  • Actual data flowsIdentify which sensitive data is being transmitted between services.
  • Interaction contextLink discovered data with sources, recipients, and endpoints.
  • Real-time visibilityAccount for changes in inter-service interactions without manual diagram updates.
  • dspm.sollisero / flow-mapOpen in product →

Security Policy Enforcement

03
dspm.sollisero / policies
PoliciesConditions that detect how its data at rest, in transit and in access.Create policy
✓Heads-up: 2 of 5 policies are active and checking your perimeter.Enable all
PolicyTypeSeverityTriggeredMonitoring
Card data over plaintext HTTPPCI · in transit · any destinationTransferCritical14
PII leaving EU regionsCustomer data · geoTransferHigh6
IBAN in unprotected policyAll resources · auto-generatedAt restHigh—
SSH autogenerated policyAll resources · auto-generatedAt restMedium—
Driver license autogenerated policyAll resources · auto-generatedAt restMedium—
  • Authorized transfer verificationCompare actual sensitive data flows against predefined rules.
  • Anomaly detectionIdentify unauthorized data transfers between services.
  • Incident loggingLog events with the necessary context for further analysis.
  • dspm.sollisero / policiesOpen in product →

Incident Investigation

04
dspm.sollisero / incidents
EventsPriority, context and owner — everything you need to investigate.Start triage
Open events32+4 since yesterday
Critical42 unassigned
In progress6Assigned to analysts
Resolved18This week · median 4.2 h
EventSeverityStatusOwnerDetected
Card numbers sent over plaintext HTTP#842 · checkout-api → analyticsUnassigned—Nov 3 · 09:41
Public bucket exposes customer PII#839 · s3 / customer-exportsInvestigatingLiam OrtizNov 3 · 08:22
Secret detected in application logs#835 · auth-svc · api-keyInvestigatingMara ChenNov 2 · 22:30
Unusual export volume#831 · reports-worker · 1.2 GBNew—Nov 2 · 18:04
  • Event detailsIdentify the types of transferred data, source, and recipient.
  • Route reconstructionIdentify services, endpoints, and exact data transfer routes.
  • External system integrationSend incident data through integrations to your existing security workflows.
  • dspm.sollisero / incidentsOpen in product →

Unified picture of sensitive data flows

Where the data is stored, which services process it, and what routes it takes — in one workspace for security, compliance and platform teams.

01Data flow map
dspm.sollisero / overview
Workspace›Data map Search assets, events, policies...⌘K ? Copilot
[ 01 ]  TOPOLOGY
Data map
From the entry point to the data store — follow the path of sensitive data.
Resource groups →Share view
Scanning Discovering your infrastructure — the first full map takes up to 7 days56 of ~80 expected nodes found · 3 sensors reporting · last update 4 min ago →Sensor status
Node, data or cluster GroupNamespace⌄ RegionAll⌄ DataAny⌄ High risk only ServiceStoreRisk
External entry points3
internetPublic ingress · 4 connections
payment-providerPartner API · 2 connections
partner-sftp 1 riskFile drop · 1 connection
Services by namespace14
checkout-api 2 riskspayments · 6 connections
payments-corepayments · 3 connections
user-profileidentity · 5 connections
crm-sync 1 riskcrm · 2 connections
reporting-worker 1 riskanalytics · 2 connections
billing-eventspayments · 3 connections
auth-serviceidentity · 4 connections
Data stores by engine11
PostgreSQL 6 risks3 clusters · 9 schemas
Kafkaevents-bus · 6 connections
S3 / archivecold storage
02Incident log
dspm.sollisero / inventory
Protection›EventsSearch assets, events, policies...⌘KCopilot
EventsPriority, context and owner.Events report
Open32
Critical4
In progress6
Resolved18
Card numbers sent over plaintext HTTP#842 · checkout-api → analytics
New
Public bucket exposes customer PII#839 · s3 / customer-exports
Triage
Secret detected in application logs#835 · auth-svc
Open
03Policy rules
dspm.sollisero / reports
Protection›PoliciesSearch assets, events, policies...⌘KCopilot
PoliciesConditions that detect how data is stored, moved and accessed.Create policy
Card data over plaintext HTTPTransfer · PCI
Critical
PII leaving EU regionsTransfer · geo
High
IBAN autogenerated policyAt rest
High
SSH autogenerated policyAt rest
Medium
Traffic // Storage // RoutesDetect // Enforce // Investigate

Why dspm

Visibility into sensitive data inside Kubernetes — without manual diagram updates or external infrastructure.

↖Hover a tab to switch the panel

Infrastructure evolves. Data control stays with you.

Connect new services and integrations while keeping control over sensitive data flows and security policy enforcement.

Discuss your project↗
Detected valueClassified · flaggedViolation
dspm.sollisero / changes
Resource groupsNew group
⟳A new route appeared · reports-worker → partner-sftp
Payments perimeter6 services · 2 stores
Covered
EU customer data4 services · 3 stores
Covered
reports-workerNew · added 2 min ago
Review
01 // Changes

Infrastructure updates

Catch new sensitive-data routes as services, integrations and Kubernetes components change.

dspm.sollisero / inventory
Data storesAdd source
Stores15
Schemas12
Scanned9
Last scan7 days
PostgreSQL · customers14 fields · PII
6 risks
Kafka · events-busEmail · phone
2 risks
S3 · archiveNo sensitive data
Clean
02 // Inventory

Identifying data locations

Find sensitive data across databases and storage, mapped to services and routes.

dspm.sollisero / violations
API endpointsExport
Endpoints778
Requests1.2M
Sensitive590
Violations214
POST /analytics/ingestcard · PCI · plaintext
Violation
GET /crm/contactsemail · PII
Allowed
PUT /users/{id}phone · PII
Allowed
03 // Security

Verifying transfer authorization

Detect transfers between services and clusters that break security policy.

dspm.sollisero / incident-842
ReportsGenerate
Incident#842 · card data over HTTP
Routecheckout-api → analytics
Datacard=5536 •••• 0217 · PCI
WindowNov 3 · 09:41 – 09:52
StatusEvidence exported
04 // Audit

Answering the regulator

Hand auditors a complete record of what data left, where it went and through which service.

Questions & answers

Didn’t find your answer? Our team will walk you through deployment in your environment.

The platform detects sensitive data in inter-service traffic and connected storage systems, including email addresses, phone numbers, and payment card numbers. Data classification is performed using templates, regular expressions, and data structure analysis.

No. Management, classification and storage components are deployed within the customer’s infrastructure. The platform works in an isolated environment and requires no changes to monitored applications — deploy into the cluster and get a live map of where sensitive data lives and moves.

dspm compares actual sensitive data flows against predefined security rules, detects transfers along routes not permitted by policies, logs the violations, and stores the data for further analysis. The event keeps data type, source, recipient, involved services, endpoints and the exact transfer route, and can be sent to Jira, Slack, email or webhooks.

dspm focuses on actual inter-service interactions and connected storage inside Kubernetes — it gives security teams the context of where sensitive data is located, which applications process it and where it is transmitted. Detected violations flow into existing security tools and workflows, so dspm complements the controls you already run.

Trusted by teams that guard sensitive data

Bereke Bank
Highland Gold
kardex
Asakabank
audiomack
SheKnows
// Logos shown with client permission150+ clients worldwide

See dspm in action

We’ll show how the platform maps sensitive data flows in your Kubernetes environment.

[ Request a demo ]

Request received

Thanks. We’ll write to you within one business day.

Other products Sollisero ATMATM network management↗ cash solutionsPOS terminal and merchant portal↗