> ## Documentation Index
> Fetch the complete documentation index at: https://docs.borghq.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Assets

> View and manage your organisation's external attack surface

Assets are your organisation's external attack surface — the domains, subdomains, and IPs that are visible from the internet. Everything Odin discovers via [Continuous Asset Discovery](/platform/continuous-asset-discovery), Mjolnir's reconnaissance phase, or that you add manually appears here.

Open the Assets page from **Attack Surface > Assets** in the sidebar.

## Asset types

| Type          | Description                                                 |
| ------------- | ----------------------------------------------------------- |
| **Domain**    | A root domain (e.g. `example.com`)                          |
| **Subdomain** | A subdomain under a root domain (e.g. `api.example.com`)    |
| **IP**        | An IPv4 or IPv6 address associated with your infrastructure |

HTTP routes and endpoints are tracked separately and attached to the asset that serves them — see the **Routes** tab below.

## Sources

Each asset is tagged with how Odin learned about it:

* **Manual**: added by a member of your team
* **Recon**: discovered by Continuous Asset Discovery
* **Import**: added via CSV/JSON import
* **Agent**: discovered by Mjolnir during a pentest run

## Adding assets

There are two ways to add assets manually:

* **Add asset**: click **Add Asset** in the page header, choose the type, and enter the value. You can also toggle Continuous Asset Discovery on at creation time.
* **Import assets**: click **Import** and upload a CSV or JSON file containing multiple assets

## Activating Continuous Asset Discovery

If your organisation has CAD enabled but hasn't yet activated a subscription, a banner on the Assets page prompts you to start. Once active, you can toggle CAD on a per-asset basis as you add or edit them. See [Continuous Asset Discovery](/platform/continuous-asset-discovery) for what CAD does and how it's billed.

## Asset detail

Click any asset in the list to open the detail panel. The panel has five tabs:

### Overview

Key metadata about the asset:

* **Type, source, status, and creation date**
* **DNS data**: A, AAAA, CNAME, and other resolved records (for domains and subdomains)
* **HTTP data**: response status, headers, redirects (for domains and subdomains)
* **TLS data**: certificate subject, issuer, expiry, and chain (for HTTPS endpoints)
* **Open ports and services** (for IPs): each open port Odin found, with its detected service, web server, frameworks, and whether it supports TLS. When an IP sits behind an edge provider with nothing useful to scan, a note explains why no ports are listed (see [Infrastructure providers](#infrastructure-providers))
* **Notes**: a free-text field your team can edit; useful for owner / on-call info
* **Monitoring toggle**: turn CAD on or off for this asset

### Tech

Technologies detected on the asset — web frameworks, CMSes, JavaScript libraries, analytics tools, server software, and so on. Useful for understanding your supply chain and tracking inventory of risky dependencies.

### Relation

A focused view of how this asset connects to other assets in your inventory:

* **Domain hierarchy**: parent and child relationships in your domain tree
* **Certificate sharing**: other assets that share the same TLS certificate
* **IP co-resolution**: domains and subdomains resolving to the same IP

See [Asset Relations](/platform/asset-relations) for more on how these connections are derived.

### Routes

HTTP routes (paths and endpoints) Odin knows about for this asset. Click a route to open it, or use **Add route** to capture additional paths Odin hasn't yet seen — useful when you know about an endpoint that's not linked from any crawled page.

### Findings

All findings that reference this asset, with the same filter, sort, and detail experience as the main [Findings](/platform/findings) page.

## Infrastructure providers

When Odin recognises that an IP belongs to a known cloud or edge provider, it marks the asset with a provider badge. The badge shows in the assets list, in the detail panel header, and on the [Attack Surface Map](/platform/attack-surface-map), so you can tell at a glance who owns an address range. Odin labels Cloudflare, Google Cloud, AWS, and Azure by name.

A provider badge marks who owns the range, not whether Odin scanned it:

* **Cloud compute** (AWS, Azure, and Google Cloud, including its global load balancers) is labelled and still fully port-scanned, so its open ports appear in the Overview tab as usual.
* **Front-end edge ranges** (such as Cloudflare, CloudFront, and Front Door) host many customers behind shared addresses, so a port scan reveals nothing about your asset. Odin labels these and skips the scan. When that happens, the Open ports section shows a note saying the IP is edge infrastructure rather than a port list.

<Info>
  A badge on its own never means scanning was skipped. The skipped-scan note appears only on an edge-provider IP that has no recorded open ports.
</Info>

## Filtering and search

Use the filters at the top of the Assets page to narrow your view:

* **Type**: show only domains, subdomains, or IPs
* **Status**: filter by active, inactive, or unverified
* **Source**: filter by Manual, Recon, Import, or Agent
* **Search**: free-text search across asset names and metadata
* **Sort**: order by value, last seen, or date added

<Tip>
  The URL updates as you filter, so any view can be bookmarked. Keyboard shortcuts: `j`/`k` navigate the list, `Enter` opens the focused asset, `x` toggles selection.
</Tip>

## Exporting

Click **Export** in the page header to download your assets in CSV, Markdown, or JSON. The export respects your current filters, so narrow the list first if you want a focused report.