SOC 2 Asset Inventory Template for SaaS Startups
Build a SOC 2 asset inventory for a small SaaS team. Use this example to list the right systems, services, vendors, and devices, then reconcile them to source records.

A SOC 2 asset inventory for a SaaS startup is a current, checked list of the systems, services, provider relationships, and important devices that support the service under review. Start with your SOC 2 scope, then record who owns each item, why it matters, where its facts come from, and when someone last checked them. The template below is a working example, not a required AICPA form.
What belongs in a SOC 2 asset inventory?
The NIST Cybersecurity Framework 2.0 Small Business Quick-Start Guide recommends maintaining an inventory of hardware, software, systems, and services. That is useful starting guidance, but NIST’s guide does not set the scope of your SOC 2 examination. The AICPA SOC 2 description criteria ask management to describe the system being examined, including its infrastructure, software, people, procedures, and data. Your inventory should support that description and the controls you actually operate.
For a small SaaS company, begin with four related sets of records:
| Record | Include when | Example |
|---|---|---|
| Bounded system | Management governs or plans to have the CPA firm examine the service | Customer-facing application and its operating boundary |
| Service component | A capability delivers that system, operates a control, or provides authoritative evidence | Production database, identity service, or deployment pipeline |
| Vendor | An external relationship materially supports the service or handles its information | Cloud hosting provider or customer support provider |
| Important asset | A device, medium, software item, or other item needs custody and lifecycle tracking | Engineer laptop with production access |
These are different jobs. A laptop is not a separate customer-facing system; a cloud provider relationship is not the same record as the database service it supplies. Keep the system description readable by linking to current inventory rather than copying every device into its narrative.
Copy this small-team inventory template
Use one row per material item in a working review sheet, or map these columns to records you already maintain. The sample names below are fictional.
| Item and kind | Owner | Scope reason | Source to check | Check to perform |
|---|---|---|---|---|
| Customer app (SYS-001), system | Engineering lead | Service named in the candidate SOC 2 scope | Architecture and service description | Confirm boundary and exclusions |
| Production database (CMP-001), component | Backend lead | Stores customer account data | Cloud resource export and deployment configuration | Confirm account, region, and data use |
| Identity service (CMP-002), component | Security owner | Grants production access and supplies access logs | Identity admin export | Confirm active integration and evidence access |
| Cloud host (VEN-001), vendor | Operations lead | Supplies the production environment | Contract, account list, and current vendor record | Confirm service and review owner |
| Assigned laptop (AST-001), asset | IT owner | Used by an engineer with production access | Device management export and assignment record | Confirm custodian and active status |
The table shows what to check. To make a working sheet, copy this CSV example and replace its fictional rows with your own. The review fields stay pending until someone checks the named source:
id,kind,name,owner,status,system_ids,supplying_vendor_id,related_component_ids,scope_reason,source_system,source_export_ref,source_export_date,last_checked,reviewer,review_decision,custodian,location,information_type_or_classification
SYS-001,system,Customer app,Engineering lead,active,,,,Service named in candidate SOC 2 scope,Architecture and service description,,,,,pending,,,
CMP-001,component,Production database,Backend lead,active,SYS-001,VEN-001,,Stores customer account data,Cloud resource inventory,,,,,pending,,,
CMP-002,component,Identity service,Security owner,active,SYS-001,,,Grants production access and supplies access logs,Identity admin export,,,,,pending,,,
VEN-001,vendor,Cloud host,Operations lead,active,,,,Supplies production environment,Contract and account list,,,,,pending,,,
AST-001,asset,Assigned laptop,IT owner,active,,,CMP-002,Used by engineer with production access,Device management export,,,,,pending,Assigned engineer,Remote,Internal
The Component rows link the database and identity service to the customer app.
The database also links to its cloud host. The Asset row links a laptop to the
identity service and records its custodian, location, and handling class.
Use system_ids for a Component’s bounded Systems,
supplying_vendor_id for its provider, and related_component_ids for an
Asset’s related Components. Leave a relationship cell blank when it does not
apply. These are working-sheet columns, not a FileGRC import format. Link
source_export_ref to the fixed export or approved evidence reference, then
fill in its date, the check date, reviewer, and decision. Record information
type or classification when it affects protection. Keep
serial numbers or sensitive details in an approved location; a working review
sheet does not need secrets or personal data copied into Git.
Do not turn this example into a list of every ephemeral container or every software package without asking what your controls need. Record the durable service component and preserve the complete, time-bounded source export when a control or the CPA firm needs the underlying resource population. The audit population guide explains how to keep that export complete and reviewable.
Reconcile the inventory to actual sources
A list written once during setup will drift. Check it against systems that show what exists and who uses it:
- Export the relevant cloud accounts, environments, and resources. Note the query, account and region coverage, export time, and owner.
- Compare identity and application admin lists with your service components and provider records. Investigate tools that grant access or hold customer data but have no owner.
- Compare endpoint management with assigned devices. Check lost, returned, retired, and unmanaged devices against access records. The SOC 2 endpoint security guide covers the settings each device should meet.
- Review procurement and expense records for new services that engineering or support adopted outside the initial architecture list.
- Record additions, exclusions, duplicates, and unresolved gaps. Keep the dated export and the review decision together.
An exclusion needs a reason. A test environment might be outside a proposed report boundary but still hold customer data or affect production access. The owner should examine that dependency before marking it out of scope. The vendor review guide covers the separate decision about provider risk and assurance material.
Keep the list current after the first review
Update the inventory when the team adds a service, changes an integration, assigns or retrieves a device, changes a provider, or retires a resource. Set a review interval based on the approved control and risk, then record what the reviewer compared and what changed. A Git diff can show a changed inventory record, while the cloud or device source still supplies the operating facts.
During a Type 2 examination, a current list alone may not show what existed throughout the period. Keep dated snapshots, change records, or source exports that let the CPA firm test the control over the specified period. Management prepares and reconciles that evidence; the CPA firm chooses its testing method and decides whether the evidence is sufficient.
Use FileGRC as the program record
FileGRC is a Git-native GRC workspace for SOC 2 work. JSON holds structured records, Markdown holds long-form work, and Git supplies the change history. FileGRC has separate System, Component, Vendor, and Asset records, so the bounded service, a technical dependency, a provider relationship, and a device do not have to share one loose spreadsheet row. Asset records cover owner, custodian, location, status, and related Components. Starter records are proposals until your team checks them against actual operations.
An agent can compare those records with exports you provide, draft corrections, and point out missing owners or links. Your team reviews the proposed change and the source facts. FileGRC does not collect an authoritative cloud or device inventory by itself, operate those systems, or perform the independent SOC 2 examination.
Run your SOC 2 program as files in Git.
Keep policies, controls, work, and evidence indexes in a repository your team and agents can inspect. Add optional FileGRC Autopilot email and Slack reminders to keep work moving.
Frequently asked questions
Does SOC 2 require a specific asset inventory template?
No single spreadsheet format fits every SOC 2 system. Management needs records that match the scoped service and the controls it operates. The CPA firm determines what inventory and supporting evidence it needs for the examination.
What should a SaaS startup put in its SOC 2 asset inventory?
Start with the bounded service, material infrastructure and software services, relevant provider relationships, important devices or media, and the information those items handle. Keep an owner, status, scope reason, and authoritative source for each entry. The exact population depends on your system and controls.
Is a cloud console screenshot a complete asset inventory?
Usually not. A screenshot shows a view at one point in time and may omit other accounts, regions, services, or deleted items. Preserve the source export or query, its scope and date, and a reconciliation to the inventory and approved exclusions.
How often should we review the inventory for SOC 2?
Use the cadence approved in your risk-based control, and update records when assets are acquired, reassigned, lost, or retired or when the service changes. Keep dated review results and source exports. There is no universal interval that replaces your actual control and the CPA firm's testing plan.
Can FileGRC discover assets from our cloud and device systems?
FileGRC does not replace cloud, identity, or endpoint inventory sources. It can record Systems, Components, Vendors, and important Assets as JSON, link supporting evidence, and track changes in Git. Your team checks those records against authoritative source exports.