Asset Object

Assets are stored at the client level, and only the single doc_type value of "client_asset" exists in the database. An asset can exist as a standalone file added for a client through the Clients module or associated with a finding referred to as an affected asset.

An affected asset refers to a client_asset object with extra properties stored on the finding object. Although it doesn't have its own type or location in the database, it can still be considered a real object since it is technically distinct and exists within the finding object.

Asset Table

The following table explains the fields and data types stored for an asset. Fields are presented in alphabetical order by object field name.

The only required field when creating an asset is the asset name.

Client Asset Structure

Client assets are lower-level objects containing information about an asset or application. They contain some finding information in the form of a vulnerability[link].

Client assets contain the data related to the specific physical machine or web application represented and relational information about which findings they are affected by.

Every client asset object has the findings field. For each finding affecting the client asset, an object in that field's list contains information about the finding in a specific report and additional metadata showing how the client asset relates to the finding.

Objects stored in findings contain additional relational metadata for vulnerability objects.

Child Asset Structure

The child asset contains a subset of the related client asset's information.

Affected Asset Structure

Affected assets are not objects with their own database type but a value stored in the affected_assets field of a finding object. It contains information about a client asset being affected and relational metadata about the finding and client asset.

An affected asset object on a finding will have a subset of fields compared to the client asset with the same ID. Some additional fields exist that only make sense when the finding and client asset are viewed together, such as the date the finding started affecting the client asset, the affected ports, location access to vulnerability, vulnerable parameters, and evidence of the affection.

Affected assets are very similar to Vulnerabilities, but the rules and validations defining them differ.

Last updated

© 2024 PlexTrac, Inc. All rights reserved.