Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
Academy · Running cloud security

Cloud asset inventory

A cloud asset inventory is a continuously updated list of everything that exists in your cloud environments, such as users, devices, apps, virtual machines, storage and databases, together with their key properties and relationships. It matters because you cannot secure, patch or pay for what you do not know exists, and unknown or forgotten resources are where weak settings usually hide.

How it works

An inventory is built by reading the management interface of each cloud, saving what comes back, and keeping it fresh. The records are only useful if they carry properties you care about, such as whether a storage account accepts public access, who owns a group, or when an app secret expires, and the links between objects.

What each platform offers

  • Microsoft 365: the directory behind it holds users, guests, groups, devices, enterprise apps (service principals) and app registrations, and Microsoft Graph is the interface for reading them. Mailboxes, SharePoint sites, policies and licences sit in their own services.
  • Azure: Azure Resource Graph lets you query resources across many subscriptions at once.
  • Google Cloud: Cloud Asset Inventory is a metadata service to view, search and export assets across projects, folders and an organization. Google documents that asset history is kept for up to 35 days.
  • AWS: AWS Config records resource configurations and their history, and an aggregator can combine the data from several accounts into one view.

These native tools are strong inside their own cloud. The harder part is one picture across all of them, with the same fields and the same questions.

Why it matters

Inventory comes first in the CIS Critical Security Controls: Control 1 is the inventory and control of enterprise assets, because every other control assumes you know what you are protecting. A check for weak settings cannot run on a resource nobody listed.

In practice the risks are plain. A guest account from a finished project still has access. A disk or virtual machine from a test lives on, unpatched. An app registration holds a secret that expired or will soon. A subscription, project or account was created by a team that never told IT. None of these is exotic, but each is invisible without a list.

How it compares

TermWhat it answersDifference
Cloud asset inventoryWhat exists, and how is it connected?The foundation: a list with properties and relationships
CSPMWhich settings fall short of a standard?Evaluates configuration against rules, using the inventory as input
CMDBWhat do we manage, and who owns it for IT service purposes?A service-management record, often maintained by hand and rarely complete for cloud resources
CIEMWho can do what?Focuses on permissions and entitlements rather than every resource
Configuration driftWhat changed since last time?Needs a baseline inventory to compare against

Getting started

  1. Write down your scope: every Microsoft 365 tenant, Azure subscription, Google Cloud project and AWS account, including ones owned by subsidiaries or created by other teams.
  2. Use each cloud's own listing tool to get a first count, then compare it with what your team believes exists. The gaps are your first findings.
  3. Decide what to record for each item: owner, purpose and the few security properties that matter, such as public exposure or credential expiry.
  4. Start with the easy risk lists: users inactive for 90 days, guests who never signed in, groups without an owner, unattached disks.
  5. Assign an owner to every orphaned item and set a date to remove it or justify it. Then repeat the review on a schedule.

How ConfigCobra fits

ConfigCobra's Inventory module gives one inventory across clouds, with a per-cloud view and an "All clouds" view. It is available on Microsoft 365, Azure, Google Cloud and AWS.

  • Microsoft 365: users, guests, admins, groups, devices, enterprise apps, app registrations, mailboxes, SharePoint sites, Conditional Access and other policies, domains, licences and directory roles.
  • Azure: resources across subscriptions with security properties such as public network access and minimum TLS.
  • Google Cloud and AWS: resources across the projects or accounts in scope, with their security properties.

Built-in risk views include users inactive 90 days, groups without an owner and unattached disks. A relation graph shows how objects connect, findings link to the objects they concern, and you can export to CSV. Access is read-only, so ConfigCobra never changes your environment.

See where your cloud stands

ConfigCobra checks Microsoft 365, Azure, Google Cloud and AWS against the CIS benchmarks, read-only, with evidence for every finding.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial