You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/open_asset_model/assets/index.md
+10-12Lines changed: 10 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
-
# :simple-owasp: `Assets`
1
+
# :simple-owasp: Assets
2
2
3
3
In the [OWASP](https://owasp.org)[Open Asset Model](https://github.com/owasp-amass/open-asset-model), an asset represents any discrete, observable element in the external environment of an organization that holds security or operational relevance. Assets can range from technical resources like domain names and IP addresses to organizational constructs such as legal entities and brand names. What makes assets central to the model is that they serve as the primary objects of analysis—entities that can be discovered, attributed, linked, enriched, and ultimately assessed for risk. Each asset is uniquely identified, carries contextual metadata such as confidence and source of discovery, and participates in a web of typed relationships that form a dynamic, queryable graph of an organization's external footprint.
4
4
5
-
## Why *Assets* Are the First‑Class Citizens
5
+
## :material-graph-outline: Why *Assets* Are the First‑Class Citizens
6
6
7
7
In the **Open Asset Model (OAM)**, *assets* are the atomic units of knowledge that describe an organization’s externally observable footprint. Every other class in the model—attributes, properties, relations—exists to enrich or contextualize an asset. By treating *everything discoverable* (from a DNS name to a cloud storage bucket) as an asset, we gain three strategic advantages:
8
8
9
9
1.**Uniform Vocabulary** – Analysts, tools, and automation pipelines can exchange data without bespoke translation layers.
10
10
2.**Composable Reasoning** – Graph analytics, enrichment, and risk scoring can be applied consistently because every node shares a common set of metadata fields (`id`, `confidence`, `source` …).
11
11
3.**Auditability** – Each asset retains a pointer to discovery provenance, making it trivial to reproduce findings or trace errors.
12
12
13
-
## Asset Definition
13
+
## :material-graph-outline: Asset Definition
14
14
15
15
> **Asset**: *An identifiable object—digital, network, or legal—that an organization owns, operates, or relies on and that can be observed from outside the security perimeter.*
16
16
@@ -23,7 +23,7 @@ An asset is **not** just a label; it is a self‑contained document that answers
23
23
3.**How certain are we?**\
24
24
A *confidence* score that downstream pipelines can use to gate actions.
@@ -35,20 +35,19 @@ An asset is **not** just a label; it is a self‑contained document that answers
35
35
36
36
*This list is intentionally open‑ended; community pull requests routinely add new asset types as technology evolves.*
37
37
38
-
## Core Asset Attributes
38
+
## :material-graph-outline: Core Asset Attributes
39
39
40
40
Every asset embeds a minimal yet powerful set of metadata:
41
41
42
42
```json
43
43
type: "FQDN"
44
-
value: "login.example.com"
45
44
created_at: "2025-06-11"
46
45
last_seen: "2025-06-27"
47
46
```
48
47
49
48
Additional attributes are type‑specific—for instance, an `IPAddress` has the **address** field, while an `Organization` stores jurisdiction and registration numbers.
50
49
51
-
## Relationships: Building the Graph
50
+
## :material-graph-outline: Relationships: Building the Graph
52
51
53
52
Assets rarely exist in isolation. The model expresses **typed, directed edges** such as:
54
53
@@ -59,7 +58,7 @@ Assets rarely exist in isolation. The model expresses **typed, directed edges**
59
58
60
59
These links turn the asset collection into a searchable **property graph**, enabling path‑finding queries like *“Which IP ranges host domains that roll up to Acme Corp’s legal entities?”*
61
60
62
-
## Lifecycle in the Discovery Pipeline
61
+
## :material-graph-outline: Lifecycle in the Discovery Pipeline
63
62
64
63
```mermaid
65
64
flowchart LR
@@ -77,7 +76,7 @@ flowchart LR
77
76
4.**Enrichment** – Plugins append properties, such as alternative names, vulnerabilities, etc.
78
77
5.**Analytics & Export** – Downstream tools run path queries, generate reports, or feed alerting pipelines.
79
78
80
-
## Quick Example: From Evidence to Asset
79
+
## :material-graph-outline: Quick Example: From Evidence to Asset
81
80
82
81
Imagine Amass extracts the email address *security@example.com* from the footer of *www.example.com*:
83
82
@@ -91,16 +90,15 @@ The *web scraper* module produces:
91
90
```json
92
91
type: "ContactRecord"
93
92
discovered_at: "http://www.example.com"
94
-
value: "security@example.com"
95
93
created_at: "2025-06-28"
96
94
last_seen: "2025-06-28"
97
95
```
98
96
99
97
An edge will be created between the **ContactRecord** and **Identifier** containing the email address (security@example.com). Future encounters with the same email address will reference the same asset in the graph.
100
98
101
-
## Where to Go Next
99
+
## :material-graph-outline: Where to Go Next
102
100
103
-
Take a look at the pages with details for every asset type.
101
+
Take a look at the pages where details are provided for each asset type.
104
102
105
103
-[Relations](../relations/index.md) – Overview of Relations in the Open Asset Model.
106
104
-[Properties](../properties/index.md) - Overview of a Property in the Open Asset Model.
0 commit comments