About Asset Tags
An Asset Tag is an essential piece of information in a tag (#) form attached to an asset. Asset Tags allow you to organize your assets based on dynamically applied rules. An Asset tag can represent a business or technical info associated with the asset, for example,
#https-server. There are two types of Asset Tags:
Imported Asset Tags (Connector's Tags)
Manually Created Asset Tags (Vulcan Tags)
For more context about Asset Tags and Business Groups, click here.
Accessing Asset Tags
To access asset tags in the Vulcan Platform:
Go to Assets
Open the Tags pane on the right.
Scroll through the tags and categories, or search for a specific tag.
Imported Asset Tags
The Vulcan Platform automatically imports tags from connectors and attaches them to the relevant assets. This saves you from having to re-tag thousands of assets. Instead, you can keep using the tags you’ve been using until now and import them into the Vulcan Platform.
Identifying Imported Asset Tags
This is what imported tags look like in the Vulcan Platform Tag Management:
Creating Asset Tag (Vulcan Tag)
Go to Assets > Open the Tags pane on the right.
Click on Add > Asset Tag
Give your tag a meaningful and unique name.
Set Impact score – high, low, medium, or leave it unassigned. This will allow Vulcan’s risk algorithm to rank asset vulnerabilities with a business impact in mind.
Select the conditioning method:
Match All (the "and" condition): Only results that match all filters
Match Any (the "or" condition): Results that match at least one of the filters
Select how to match the tag:
Naming convention: Enter a text string to match an asset's name. Any asset whose name contains the string will be tagged.
Subnet: Enter a subnet formatted as an IP address and a CIDR. Any asset with IP in that subnet will be tagged.
Follow other tags: Choose an existing tag or tags. Assets with the selected tags will be tagged.
Follow a saved search
Specific assets: define specific assets
External facing: External facing assets are usually recognized automatically by the Vulcan platform and tagged as "External Facing". You can also manually define the asset that can be accessed from outside the organization. Read all about it here.
Optional: You can manually include Code Project or Website assets to these matches. This allows you to create a unified, hybrid tag comprised of infrastructure and AppSec assets.
After creating your conditions, look at the preview section to see if the results match your created conditions.
Optional: Check the “Use as Dynamic Property” checkbox to use this tag as a dynamic property.
Before enabling the "Use as an Dynamic Property" setting, learn about the Dynamic Properties feature and its impact.
When Ready, click "Save".
The created tag dynamically updates any new/existing assets that match the conditions.
Identifying Manually Created Asset Tags (Vulcan Tags)
The Vulcan Tags appear under the "Vulcan Tags" category in the Asset Tags management pane.
Managing and Editing Asset Tag
Click on an Asset Tag.
If this is an Imported Asset Tag, you can only review the associated assets to decide on the impact of the tag. The conditions box will not be available.
If this is a Vulcan Asset Tag (manually created), you can also modify the associated assets by playing with the matching conditions.
Review and edit the asset tag name if relevant.
Review and set the Impact to prioritize the assets associated with the tag (recommended).
When ready, click "Save".
Asset Tags across the Vulcan Platform
What’s the difference between managing Vulcan tags vs. imported asset tags?
You can edit and change the conditions, name, and impact of Vulcan tags (i.e., manually created asset tags).
As for imported tags, you can only edit the name and modify the impact.