> ## Documentation Index
> Fetch the complete documentation index at: https://docs.snapsec.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Assets & Asset Identity

> How Snapsec establishes persistent, canonical asset identity across hybrid environments.

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:

```mermaid theme={null}
flowchart LR
    A["Raw Ingestion Data
(DNS, IP, Cloud ARN, Git Repo)"] --> B["Identity Resolution Engine"]
    B --> C["Canonical Asset ID
(e.g., ast_8f93a10c)"]
    C --> D["Enriched Attributes
- Technical Owner
- Business Unit
- Classification (Prod/Dev)
- Historical Exposure"]
```

### 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.