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
The Open Asset Model is an effort to uniformly describe assets
that belong to both organizations and individuals.
Asset specifications have traditionally focused upon the technical,
infrastructure-specific things that can be discovered on the internet.
While this represents a potentially significant portion of an organization's
assets, it is also limiting. The Open Asset Model seeks to expand on
this and cover the breadth and depth of both physical and digital assets
so that an organization can realize their full Attack Surface.
Open Asset Model defines not just the assets themselves, but also the
relationships within and across types of assets. This allows the model
to express the real-world interconnectedness that exists between assets.
Open Asset Model also seeks to provide models to support the discovery path
to understand how assets were discovered / exposed.
When it comes to asset discovery, it is sometimes a bit of a mystery as to
how an asset was discovered. For this reason, we believe it is necessary to
to record the order of events, including the source,
that lead to the discovery of an asset.
The source of the data is useful in a number of different ways:
It can help understand the trustworthiness and/or accuracy of the data provided.
Data sourced from less trusted sources may need to go through additional
validation steps before it can be used.
It can inform whether the data can be transferred with other parties,
which is especially important in meeting modern data privacy requirements.
It explain how a disputed asset was discovered during an investigation.
| serial_number | string | false | The serial number of the certificate |
| version | int | false | The version of the certificate |
| key_usage | []string | false | The key usage of the certificate |
| extended_key_usage | []string | false | The extended key usage of the certificate |
| crl_distribution_points | []string | false | The CRL distribution points of the certificate |
| issuer_urls | []string | false | The issuer URLs of the certificate |
| oscp_server | string | false | The OCSP server of the certificate |
| policies | []string | false | The policies of the certificate |
| subject_key_id | string | false | The subject key id of the certificate |
| authority_key_id | string | false | The authority key id of the certificate |
In order to understand how assets have been discovered,
the Open Asset Model provides a specification that allows
an operator to trace the path of how an asset was discovered.
As an example, the following log event could be used to determine how 108.162.193.247
was associated with the owasp.org domain.
Source Asset {"id":1,"name":"owasp.org","tld":"org"} generated a [DNS A Record Request] that was serviced by [source] on [timestamp] and exposed Asset {id:2,"address":"108.162.193.247","type":"v4"}
or in the negative case
Source Asset [] generated [request type] on [timestamp] that had no sources that could fulfill the request
source_asset: the id of the asset that was used to generate the
request that found the asset.
asset: the id of the asset discovered.
timestamp: the timestamp in which the asset was discovered.
source: - The source that the asset was derived from.
name - The name of the source
In the future, source can be extended to capture additional information
about the nature of the collection that was performed.