# Asset Register

The **Asset Register** in Sprinto serves as the central repository for all assets relevant to an organisation's security and compliance posture. It consolidates both automatically discovered assets from integrated systems and manually added assets, enabling complete visibility and tracking of infrastructure, endpoints, codebases, and people across your organisation.

The register is structured into two main categories:

* **Auto-discovered assets:** Retrieved through integrations configured in the Security Hub. These include Infrastructure, Staff Devices, Code Repositories, and People.
* **Custom assets:** Manually added assets that Sprinto cannot fetch due to integration limitations, such as on-premise servers, CCTV systems, or backup generators.

Together, these asset types support a unified approach to asset-based risk evaluation, compliance monitoring, and evidence collection.

***

### Key Benefits

* **Centralised Asset Inventory:** View all assets across cloud, device, human, and software domains in a single interface.
* **Compliance Alignment:** Tag assets as *In Scope* or *Out of Scope* to map them to relevant compliance requirements.
* **Risk Assessment Foundation:** Supports Asset-Based Risk Assessment (ABRA) by identifying risks tied to each asset category.
* **Ownership and Traceability:** Assign owners and metadata to each asset to ensure accountability.
* **Bulk Upload Capabilities:** Quickly onboard custom assets using a CSV-based upload template.

***

### Sections Within the Asset Register

<table><thead><tr><th width="173.49609375">Section</th><th>Description</th></tr></thead><tbody><tr><td><strong>Auto-discovered</strong></td><td>Displays assets retrieved automatically via integrations. Tabs include:</td></tr><tr><td></td><td>• <em>Infrastructure</em>: e.g., EC2, S3, Lambda (from AWS/Azure)</td></tr><tr><td></td><td>• <em>Staff Devices</em>: e.g., employee laptops, enrolled via Dr. Sprinto/Rippling</td></tr><tr><td></td><td>• <em>Code Repos</em>: GitLab, GitHub, Bitbucket, Azure DevOps repositories</td></tr><tr><td></td><td>• <em>People</em>: Staff members with compliance status and roles</td></tr><tr><td><strong>Custom assets</strong></td><td>Includes manually uploaded assets not supported via integrations.</td></tr><tr><td></td><td>• Add assets individually or in bulk</td></tr><tr><td></td><td>• Organise by asset groups</td></tr><tr><td></td><td>• Add metadata: owner, scope, notes, and classification</td></tr></tbody></table>

***

### Use Cases

<table><thead><tr><th width="297.76953125">Scenario</th><th>Description</th></tr></thead><tbody><tr><td>Compliance audit preparation</td><td>Retrieve a full list of production assets for SOC 2, ISO 27001, or GDPR audits</td></tr><tr><td>Device scope classification</td><td>Tag employee devices as <em>In Scope</em> or <em>Out of Scope</em> for onboarding and offboarding checks</td></tr><tr><td>Code repository tracking</td><td>View classification and ownership of repos across integrated Git providers</td></tr><tr><td>Manual asset tracking</td><td>Register on-prem systems, backup generators, and legacy infrastructure manually</td></tr><tr><td>Asset-based risk evaluation (ABRA)</td><td>Use asset-level visibility to evaluate exposure and prioritise remediation</td></tr><tr><td>Bulk onboarding of unmapped assets</td><td>Upload multiple assets at once using the bulk CSV template</td></tr><tr><td>Ownership visibility for audit trails</td><td>Identify asset owners to assign responsibility and streamline incident response</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sprinto.com/data-library/asset-register.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.