Asset Views enable you to segregate your assets at a granular level. The following are the options that are available using which you can create views.
- Asset Exposure
- Asset Name
- Asset Type
- Business Sensitivity
- Cloud Account ID
- Cloud Provider
- Cloud Region
- Created By
- Created On
- IP Address
- Imported By
- Imported Using
- MAC Address
- Port Number
- Resource ID
- Software Installed
- Software Package
Apart from the above options, whatever custom fields you have added will also be available. More about custom fields here.
You can find a complete list of the options available with filters that you can apply, along with their descriptions here.
You can segregate your assets in any combination that you require. The following are some of the common use cases that can be achieved quickly.
- Segregating Assets based on Business Sensitivity
- Segregating Assets based on Exposure
- Segregating Network Assets
- Segregating Web Assets
- Segregating Assets based on Operating System
- Segregating Assets based on Geographical Location (achievable using custom fields)
- Segregating Assets based on the Asset Owner (achievable using custom fields)
- Segregating Assets based on Compliance Requirements (achievable using custom fields)
There are certain views which will be available by default. They are:
- Critical Business impact assets
- High Business impact assets
- Private assets
- Public assets
- Archived assets
Creating Asset Views
For the sake of demonstration, a custom field named 'Compliance Scope' has been defined for the assets and now we are going to apply filters which will retrieve the assets which fall under the PCI compliance scope.
- Navigate to 'Assets'.
- Click on 'Advanced Filters'.
- Click on 'Add Rule'
- Select the option as 'COMPLIANCE SCOPE'.
- Choose the value as 'PCI'.
- Click on 'Apply' and the assets which have a value of 'PCI' assigned to their 'COMPLIANCE SCOPE' field will get retrieved.
- You can also save this view by clicking on 'Save as new view'.
NOTE: If any custom fields get deleted, then all the views which use those custom fields will also get deleted.