# IT Asset Inventory for Security: What to Track and How to Build One

Source: https://truvocyber.com/blog/it-asset-inventory
Published: 2026-11-21
Topic cluster: Cybersecurity

> IT asset inventory for security: which assets and fields to track, how to build one from APIs, and how asset tiers set control depth for SOC 2 and ISO.

An IT asset inventory is a complete, current list of every system a company runs, with an owner, a risk tier and a data classification on each entry. For security, the IT asset inventory covers more than laptops and servers: cloud resources, SaaS apps, identities and service accounts, data stores, code repositories, API endpoints and domains all belong on the list.

At a glance

- **Asset types**: Hardware, cloud resources, SaaS apps, identities and service accounts, data stores, code repositories, API endpoints, domains
- **Fields on every entry**: Owner, tier, data classification, environment, source of truth, last seen
- **How to build the inventory**: Pull from APIs and admin consoles on a schedule, reconcile, review the gaps manually
- **Biggest blind spot**: Legacy and forgotten assets built before the security process existed
- **What tiers decide**: Scan frequency, baseline depth and review cadence for each asset
- **Framework fit**: CIS Controls v8 Control 1 and 2, ISO/IEC 27001:2022 A.5.9, SOC 2 CC6.1

## Why is an IT asset inventory the first security control?

An IT asset inventory comes first because every other security control depends on a list of what to protect. A team cannot scan, patch, review access for, or monitor a system that nobody has written down. The [CIS Critical Security Controls](https://www.cisecurity.org/controls/inventory-and-control-of-enterprise-assets) put Inventory and Control of Enterprise Assets at Control 1 and [Inventory and Control of Software Assets](https://www.cisecurity.org/controls/inventory-and-control-of-software-assets) at Control 2, ahead of vulnerability management and access control. CIS describes both controls with the same verbs: actively manage, meaning inventory, track and correct.

The asset inventory also sets the boundary for the rest of the program:

- **Vulnerability management:** scanner coverage is checked against the inventory. The [vulnerability scan guide](/blog/what-is-a-vulnerability-scan) covers why scan results are only as accurate as the asset list behind them.
- **Access reviews:** each system on the inventory needs a named owner who approves who has access.
- **Audit scope:** the systems in [SOC 2 scope](/blog/soc-2-scope-systems-people-processes) come from the inventory, so a missing system is a scoping gap.
- **Incident response:** responders need to know who owns a compromised system and what data the system holds.

## What should an IT asset inventory include?

A security-grade IT asset inventory includes every asset type an attacker could use to get in or get data out. Asset types to cover, with examples:

- **Hardware:** laptops, desktops, phones, servers, network devices, printers, IoT devices. The [ISO 27001 A.8.1 guide](/blog/iso-27001-a-8-1-endpoint-devices) covers the endpoint part in detail.
- **Cloud resources:** accounts, projects and subscriptions, plus the VMs, buckets, databases, functions, keys and enabled APIs inside them.
- **SaaS applications:** every app that holds company data, including apps bought on a credit card outside procurement.
- **Identities and service accounts:** user accounts, admin accounts, service accounts, API keys and OAuth grants. In cloud environments we often see more service accounts and keys than people.
- **Data stores:** production databases, data warehouses, file shares, backups and exports.
- **Code repositories and pipelines:** source repositories, CI/CD systems and the secrets stored in them.
- **API endpoints:** public and internal endpoints, with the authentication method for each.
- **Domains and external IP addresses:** registered domains, DNS zones, subdomains and public IPs.

For a traditional company with on-prem servers, the hard part is usually the network: external IP addresses, IoT devices, printers and old servers. For a software company, the same blind spot tends to be API endpoints. The principle is the same in both cases: know every asset the company owns.

## Which fields does each asset inventory entry need?

Each asset inventory entry needs enough fields to answer three questions: who is responsible, how much protection the asset needs, and whether the record is still true. My approach uses these fields:
FieldWhat the field recordsWhy security needs the fieldOwnerA named person or role accountable for the assetApproves access, accepts risk, answers during an incidentTierCriticality, for example Tier 1, 2 or 3Sets scan frequency and baseline depthData classificationHighest class of data on the asset, for example Confidential or PublicDecides encryption, access and retention rulesEnvironmentProduction, staging, development, corporateSeparates audit scope from test systemsSource of truthThe API or console the record comes fromLets the team re-pull and verify the recordInternet-facingYes or noRaises priority for patching and reviewLast seenDate the source last reported the assetFlags stale and decommissioned assetsStatusActive, retired, pending deletionKeeps retired assets out of active scope

ISO/IEC 27001:2022 Annex A 5.9, Inventory of information and other associated assets, asks for an inventory that includes owners and is kept up to date. In practice, a missing owner causes the most trouble, because an asset with no owner tends to be an asset nobody patches.

## How do you build an IT asset inventory from APIs instead of spreadsheets?

Build the IT asset inventory by pulling records from the systems that already know about each asset, on a schedule, and reconciling the results. A spreadsheet typed by hand goes out of date quickly, and an inventory pulled from APIs can be refreshed on demand. Example sources by asset type:
Asset typeExample sources of truthLaptops and phonesMDM console (Intune, Jamf, Google endpoint management)Cloud resourcesGoogle Cloud Asset Inventory, AWS Config or Resource Explorer, Azure Resource GraphIdentities and service accountsIdentity provider (Microsoft Entra ID, Google Workspace, Okta), cloud IAMSaaS applicationsSSO app catalog, OAuth grants in the identity provider, expense and card dataCode repositoriesGitHub or GitLab organization APIDomains and DNSRegistrar and DNS provider APIsOn-prem servers and network devicesNetwork discovery scans, hypervisor console, agent check-ins

On Google Cloud, one command lists every resource across an organization:

```
gcloud asset search-all-resources --scope=organizations/ORG_ID
```

Cloud Asset Inventory is free to use, and only exported storage is billed, per the [GCP security best practices checklist](/blog/gcp-security-best-practices-checklist). Google's [Security Command Center Premium](/blog/security-command-center-standard-vs-premium) adds SQL queries over the same inventory.

Steps in my approach:

1. Pull each source on a schedule (weekly is a reasonable start) into one table or database.
2. Match records across sources, for example a laptop in MDM with the same user in the identity provider.
3. Flag records with no owner, no tier or no classification.
4. Flag assets that appear in one source and are missing from another, for example a server in the hypervisor with no scanning agent.
5. Review the flags manually and record a decision for each flagged item.

Key insight

**Every inventory gap needs a recorded decision.**

For each asset type nothing tests or monitors, the team either adds a check or records reviewed, not security-relevant, with a date. The list of open gaps shrinks with every review cycle, and an auditor can see each decision.

## Why are legacy and forgotten assets the biggest blind spot?

Legacy assets are the biggest blind spot because they were built before the security process existed and nobody went back to review them. New systems tend to get threat modeling, testing and hardening. In many companies, old systems keep the controls they had on day one.

Watch out

**Blind spot: the break-in came through endpoints built four years earlier.**

In one incident response, the new parts of a company's stack were well secured. The attacker came in through a few API endpoints built about four years earlier, when the company was small. The endpoints lacked proper authentication and authorization checks and had never been hardened. New work went through the security process, and old work never did.

A second engagement had the same root problem at a larger scale. The client ran a large application and could not afford to security-test every component, so the team tested new components only. My advice was to build a minimum inventory of every API endpoint first, then flag the endpoints that were sensitive and the endpoints that were old, and test those.

Cloud accounts collect forgotten assets the same way. A scan of a small company's own Google Cloud organization found 15 projects, and 8 of them were stale: an untitled project, projects that AI tools and an Apps Script created automatically on first use, an old website project and an empty duplicate. Four of the stale projects still held API keys that worked. After cleanup, 7 projects remained, and the organization-wide security scan dropped from about 1 hour 45 minutes to 6 minutes. The [Google Cloud IAM best practices guide](/blog/google-cloud-iam-best-practices) covers who can create projects and how to remove service account keys.

## How does asset tiering decide how deep each control goes?

Asset tiering assigns each asset a criticality level, and the tier sets how often the team scans, reviews and monitors the asset. Tiering keeps a small team from spending the same effort on a network switch as on a production database.

At one SaaS company of 15 to 20 people preparing for SOC 2, the team first planned weekly scanning on every system. The plan would have generated noise and consumed time on low-risk assets. The team moved to three tiers:
TierExample assetsControl depthTier 1Production systems and anything internet-facingWeekly automated scans, full CIS benchmark baselines, automated alerts on configuration changesTier 2Hypervisors, storage systems, internal management serversQuarterly manual reviews with documented checklistsTier 3Network switches, phones, other infrastructureDefault credentials changed, baseline documented in the asset inventory, annual manual check

SOC 2 CC7.1 and CIS Controls v8 ask for monitoring of vulnerabilities and configuration drift, and neither specifies weekly scans for every asset. A documented tier model shows a risk-based method an auditor can test. The [bare-metal configuration baselines guide](/blog/soc2-configuration-baselines-bare-metal) covers the scanning side of the same model for on-prem servers.

Key insight

**Asset tier and data classification change together.**

A Tier 3 asset that starts holding Confidential data moves up a tier, and the inventory record is where the team catches the change.

## How do you keep an IT asset inventory current?

Keep the IT asset inventory current by refreshing the API pulls on a schedule and checking the inventory against other systems that see assets. Examples of checks in my approach:

- **Scanner coverage:** compare the list of scanned hosts to the inventory every quarter. Hosts on one list and missing from the other need a decision.
- **Enabled services with no resources:** in one Google Cloud organization with 796 resources across 41 resource types, 15 enabled APIs had no resources at all. An enabled API with no resources is either unused (turn the API off) or holds something the inventory cannot see.
- **Stale entries:** assets past the last-seen threshold get confirmed with the owner, then retired.
- **Ownerless assets:** leavers' assets get a new owner as part of the offboarding checklist.
- **New asset intake:** new projects, SaaS apps and domains go through a request that creates the inventory record.

In the same organization, 4 of the 41 resource types were types no scanner tested, and those 4 types went on the manual review list. The inventory also made the assessment faster, because the team skipped checks for services that were not turned on.

## What evidence does an IT asset inventory give for SOC 2 and ISO 27001?

An IT asset inventory built from APIs gives SOC 2 and ISO 27001 evidence as a byproduct, because each refresh is a dated record with an owner and a source. Common mappings:
FrameworkRequirementEvidence from the asset inventoryCIS Controls v8Control 1 Inventory and Control of Enterprise Assets, Control 2 Inventory and Control of Software AssetsDated inventory exports, unmanaged asset decisionsISO/IEC 27001:2022[Annex A 5.9](https://www.iso.org/standard/27001) Inventory of information and other associated assetsInventory with owners, review recordsSOC 2CC6.1, point of focus Identifies and Manages the Inventory of Information Assets ([AICPA Trust Services Criteria](https://www.aicpa.org/resources/download/trust-services-criteria))System inventory with owner, classification and in-scope flagSOC 2CC7.1 vulnerability and configuration monitoringTier model, scan coverage reconciliation

Auditors tend to sample from the inventory. A server missing from the list is a server with no access review, no scan and no baseline in the evidence.

## How does the inventory fit the asset management capability?

Truvo Cyber treats asset management as one of the roughly 19 security capabilities in an effective security program. In a [security capability assessment](/services/security-capability-assessment), Truvo scores where the asset inventory stands today and sequences the fixes. For teams that want the inventory pulled from APIs and kept current automatically, see [GRC engineering services](/services/grc-engineering-services).

### Know every system you need to protect

Truvo builds asset management into an effective security program, with an inventory that stays current.[Book Your Strategy Call](/contact-us)

## Frequently asked questions

### What is an IT asset inventory?

An IT asset inventory is a list of every system a company runs, including hardware, cloud resources, SaaS apps, identities, data stores, code repositories and domains. For security use, each entry carries an owner, a risk tier, a data classification, an environment and the source the record came from, so the team can protect and audit each asset.

### What is the difference between an IT asset inventory and a cyber asset inventory?

An IT asset inventory traditionally tracks hardware and software for cost and support. A cyber asset inventory, or security asset inventory, adds the assets attackers use: cloud resources, service accounts, API keys, API endpoints, domains and SaaS apps. A security program needs the second kind, with owner, tier and data classification on every entry.

### Does SOC 2 require an asset inventory?

SOC 2 CC6.1 includes the point of focus Identifies and Manages the Inventory of Information Assets, and auditors expect a system inventory with owners and an in-scope flag. The inventory also defines which systems the auditor samples for access reviews, scanning and configuration baselines, so gaps in the inventory become gaps in the evidence.

### What does ISO 27001 require for asset inventory?

ISO/IEC 27001:2022 Annex A 5.9, Inventory of information and other associated assets, requires an inventory of information and associated assets, including owners, that is kept up to date. Certification auditors look for named owners, a review record and consistency between the inventory and the systems in use.

### How often should an IT asset inventory be updated?

Pull API-based sources at least weekly and reconcile the inventory against scanner coverage at least quarterly. Assets created through intake requests get a record on day one. Stale entries past the last-seen threshold are confirmed with the owner and retired, so the inventory stays close to the systems the company runs.

### Which assets do teams most often miss in an asset inventory?

Teams often miss legacy systems built before the security process existed, API endpoints, service accounts and API keys, cloud projects created automatically by tools, and SaaS apps bought outside procurement. In one Google Cloud review, 8 of 15 projects were stale and 4 of those still held working API keys.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is an IT asset inventory?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "An IT asset inventory is a list of every system a company runs, including hardware, cloud resources, SaaS apps, identities, data stores, code repositories and domains. For security use, each entry carries an owner, a risk tier, a data classification, an environment and the source the record came from, so the team can protect and audit each asset."
      }
    },
    {
      "@type": "Question",
      "name": "What is the difference between an IT asset inventory and a cyber asset inventory?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "An IT asset inventory traditionally tracks hardware and software for cost and support. A cyber asset inventory, or security asset inventory, adds the assets attackers use: cloud resources, service accounts, API keys, API endpoints, domains and SaaS apps. A security program needs the second kind, with owner, tier and data classification on every entry."
      }
    },
    {
      "@type": "Question",
      "name": "Does SOC 2 require an asset inventory?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "SOC 2 CC6.1 includes the point of focus Identifies and Manages the Inventory of Information Assets, and auditors expect a system inventory with owners and an in-scope flag. The inventory also defines which systems the auditor samples for access reviews, scanning and configuration baselines, so gaps in the inventory become gaps in the evidence."
      }
    },
    {
      "@type": "Question",
      "name": "What does ISO 27001 require for asset inventory?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "ISO/IEC 27001:2022 Annex A 5.9, Inventory of information and other associated assets, requires an inventory of information and associated assets, including owners, that is kept up to date. Certification auditors look for named owners, a review record and consistency between the inventory and the systems in use."
      }
    },
    {
      "@type": "Question",
      "name": "How often should an IT asset inventory be updated?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Pull API-based sources at least weekly and reconcile the inventory against scanner coverage at least quarterly. Assets created through intake requests get a record on day one. Stale entries past the last-seen threshold are confirmed with the owner and retired, so the inventory stays close to the systems the company runs."
      }
    },
    {
      "@type": "Question",
      "name": "Which assets do teams most often miss in an asset inventory?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Teams often miss legacy systems built before the security process existed, API endpoints, service accounts and API keys, cloud projects created automatically by tools, and SaaS apps bought outside procurement. In one Google Cloud review, 8 of 15 projects were stale and 4 of those still held working API keys."
      }
    }
  ]
}
