Skip to content

Asset Management


The Asset Management page provides a comprehensive interface to view and manage your asset relationships and data, allowing you to manage data for archived repositories, define and manage monorepository structures, and clean up residual findings for scanning technologies you may have removed or replaced.


Asset Management Grouping


All assets can be grouped by their Organization or the Scanner that has contributed data to the asset. The primary benefits of Organization grouping are that it allows the user to define Monorepository assets and find and clean up any orphaned assets within Boost. The primary benefit of Scanner grouping is that it allows the user to clean up any orphaned findings within Boost.

An Orphaned Asset is defined as any asset previously created via connection to a user’s 3rd party system but is no longer visible to Boost due to removal from within that 3rd party system or to permission changes that prevent the Boost application from seeing that asset anymore. The data is retained by default in Boost in case the lapse in visibility is due to an unexpected or temporary problem, but if the user is certain the asset is legitimately gone, all data associated with that repository can be easily cleaned up by using the Asset Management page.

An Orphaned Finding is any finding associated with an asset originating from a scanner that is no longer provisioned against that asset. In other words, a finding that can never be automatically closed due to resolution because the source of the finding’s detection is no longer able to report information to Boost.


By Organization


Group by Organization


By Scanner


Group by Scanner


Asset Management Filters


To refine your view and manage orphaned assets more effectively, the asset management page offers advanced filtering options:

  1. Orphaned Data: Filter assets based on the resources they are associated with.
  2. Mono Repositories: Filter to show only assets within mono repositories, aiding in managing large, consolidated codebases.
  3. Provider: Filter assets by the providers, such as GitLab, BitBucket, etc., enabling focused management based on the source of your repositories.
  4. Organizations: Focus on findings based on the organizations they belong to.

These filters ensure you can efficiently navigate and manage your assets, keeping your security posture robust and up-to-date.