Skip to main content
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.

​
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: Click any asset to open its detail drawer: an Asset Details field list (Source, Type, Category, Account, Region, Owner, Scope, Last Updated, First Seen, Tags — each row appears when the asset carries that value) above three tabs, Summary, Vulnerabilities and Tests. Controls are tracked on their own Controls page.

​
Classifying assets

ISO 27001 (A.8.2.1) requires an asset classification scheme, and SOC 2 auditors expect one. Record yours using the Tags column — a tag such as criticality:critical or tier-1 travels with the asset and can be filtered on, which is what an auditor needs to see. A scheme that works well:
  • 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.
Use the same tag vocabulary across every asset, and set an Owner on each one so the tag has someone accountable behind it.

​
Integrations that feed Inventory

To connect an integration, go to Integrations in the DSALTA sidebar.