.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334){kind=spacer}
The Inventory page gives you a complete view of every asset in your environment. Cloud resources, databases, code repositories, SaaS applications, and physical devices — all tracked in one place with ownership and classification data.Documentation Index
Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
Use this file to discover all available pages before exploring further.
What inventory is for
Auditors ask “what systems do you have?” and “how are they classified?” before anything else. You cannot protect what you do not know about. The Inventory module answers both questions by pulling asset data from connected integrations and letting you add manual entries for anything not covered by an integration.How asset data is collected
Assets flow into DSALTA from two sources:- Integration-sourced — When you connect cloud providers (AWS, GCP, Azure), hosting platforms (Heroku, DigitalOcean, Netlify), or code repositories (GitHub, GitLab), DSALTA automatically pulls the list of resources. Each asset shows the integration name as its source.
- Manual — For assets not covered by integrations (e.g., on-premise servers, physical hardware, SaaS tools without API support), you can add entries manually.
Viewing your inventory
Each asset displays:| Column | Description |
|---|---|
| Name | Resource name (e.g., “prod-db-01”, “api-gateway”) |
| Type | Server, Database, Repository, Application, Storage, Network, or Other |
| Source | Integration name or “Manual” |
| Location / Region | Where the asset is hosted (e.g., us-east-1, europe-west1) |
| Owner | Team or individual responsible for this asset |
| Classification | Critical, High, Medium, or Low |
| Status | Active, Decommissioned, or Under Review |
| Tags | Custom labels for filtering and grouping |
Classifying assets
Classification is required by ISO 27001 (A.8.2.1) and expected by SOC 2 auditors. Every asset should be classified by how critical it is to your operations:- Critical — Production databases, authentication systems, payment processing. Downtime or breach has severe business impact.
- High — Internal tools, staging environments, monitoring systems. Important but not directly customer-facing.
- Medium — Development environments, testing tools, non-sensitive repositories.
- Low — Documentation sites, marketing tools, archived resources.
Integrations that feed Inventory
| Integration | Assets pulled |
|---|---|
| AWS | EC2, RDS, S3, EBS, EFS, Lambda, DynamoDB, Redshift, ElastiCache, and more |
| GCP | Compute Engine, Cloud SQL, GKE, Cloud Storage, BigQuery, Bigtable |
| Azure | VMs, SQL, Storage Accounts, Cosmos DB, AKS, Key Vault, Databricks |
| GitHub / GitLab / Bitbucket | Repositories |
| DigitalOcean / Heroku / Netlify | Droplets, apps, sites |