Skip to main content

dspm

Data Security Posture Management (DSPM)

The DSPM domain within Kscope KDefend monitors and protects your data stores — S3 buckets, RDS instances, and databases — by detecting encryption gaps, access misconfigurations, and public exposure risks. It correlates storage and database findings through the context graph to surface data security insights with business context.


How It Works

Data Blueprints

  • AWS
  • Database

Context Graph

  • Storage & Database Topology
  • Access Pattern Analysis

DSPM Analyzers

  • Storage Security
  • RDS Security
  • Database Access

Insight Feeds

  1. Data Blueprints ingest metadata from S3, RDS, and direct database connections using read-only credentials
  2. Context Graph maps storage objects, database schemas, access policies, and IAM relationships
  3. DSPM Analyzers detect encryption gaps, public exposure, and excessive access patterns
  4. Insight Feeds surface prioritized findings scored by data sensitivity and business impact

Analyzers

AnalyzerWhat it coversBlueprints
AWS StorageS3 buckets — encryption, public access, versioning, logging, IAM policies, embedded policies, CloudTrail access events, EBS volumes and snapshotsAWS
AWS RDSRDS instances — storage encryption, SSL/TLS enforcement, IAM authentication, security groups, snapshot encryptionAWS
DatabaseDirect database environments — tables, schemas, users, views, access patterns, admin privilegesDatabase
Azure StorageAzure storage accounts, containers, encryption, access policies, replication, static site hostingAzure
Azure DatabaseAzure database services — SQL Database, Cosmos DB, access controls, encryptionAzure
GCP StorageGCP Cloud Storage buckets — access controls, encryption, lifecycle policiesGCP
GCP DatabaseGCP database services — Cloud SQL, Spanner, Firestore security and accessGCP

What It Detects

Encryption Validation

  • S3 buckets without server-side encryption
  • RDS instances with storage encryption disabled
  • Unencrypted EBS snapshots (publicly or privately shared)
  • Missing KMS key configurations

Public Exposure Prevention

  • S3 buckets with public access or permissive ACLs
  • Buckets whose objects can be made public
  • RDS instances with unrestricted security group access
  • Publicly shared EBS snapshots

Access Misconfiguration

  • IAM policies granting full S3 access (read/write/delete)
  • Users with direct bucket access bypassing role-based controls
  • EC2 instances exposing non-public S3 buckets to the internet
  • Federated users with direct S3 access via assumed roles
  • Database admin users with excessive privileges

Storage Hygiene

  • Buckets without versioning or server access logging
  • Unused or never-accessed buckets consuming storage
  • Buckets without embedded or IAM policies
  • Empty database tables and unused schemas

Key Metrics

MetricDescription
Total Data AssetsS3 buckets, RDS instances, and database environments monitored
Unencrypted StorageCount of storage resources missing encryption at rest
Public ExposureNumber of publicly accessible buckets, snapshots, or database endpoints
Access ViolationsUsers or roles with excessive data access permissions
Data VolumeTotal data under management across monitored stores
DSPM Security Risk ScoreComposite 0–100 score dynamically weighted across all active DSPM analyzers. Only analyzers with a configured blueprint contribute to the score.

Key Sightlines

  • S3 Bucket Security Distribution — Encryption, versioning, and public access status across all buckets
  • RDS Encryption Compliance — Storage encryption distribution across database instances
  • User Access to S3 — Which users access which buckets, and through what mechanisms (direct, IAM, inline, EC2)
  • EBS Snapshot Exposure — Public vs private vs unencrypted snapshot counts
  • Database User Privilege Map — Admin users, schema access, and table ownership across database environments

  • CSPM — IAM misconfigurations in CSPM directly affect who can access data stores. Storage analyzer findings correlate with IAM analyzer results.
  • ASPM — Application code may contain hardcoded credentials or connection strings that expose database access paths detected by DSPM.