Skip to main content
In dynamic environments, ephemeral cloud instances, autoscaling pods, and rotating IP addresses frequently break traditional asset inventories. Snapsec solves this through Canonical Asset Identity.

​
How Asset Identity Works

When Snapsec ingests asset data from diverse sources (ASM, Cloud Providers, Kubernetes, Scanners), it applies a multi-factor deduplication and identity resolution algorithm:

​
Identity Resolution Factors

  1. Cloud Resource ID / ARN: Immutable unique identifier for cloud workloads.
  2. Domain & FQDN: Authoritative DNS hierarchy mapping.
  3. Git Repository URL + Branch: Canonical identity for code repositories.
  4. IP + Port + Service Fingerprint: Correlation across rotating network endpoints.

​
Asset Classification Levels

Every asset is tagged with a criticality tier that directly weights vulnerability prioritization:
  • Tier 1 (Mission Critical): Customer-facing production, payment handling, core databases.
  • Tier 2 (High): Internal production services, core employee portals.
  • Tier 3 (Medium): Staging, testing, and QA environments.
  • Tier 4 (Low): Ephemeral dev sandboxes and decommissioned instances.