Create, apply, and remove Veza tags
For the examples below, BASEURL should be the address of your Veza instance, such as https://<org>.vezacloud.com
.
Use Get Query Spec Nodes
to find Snowflake tables reachable by federated Okta users belonging to the Finance
department:
The response will include the table id
:
Apply a tag by specifying a key and optional value:
Remove a tag by providing the entity id and the tag key to delete:
is a product capability allowing organizations to add additional metadata to the entities (such as users, roles, tables, or any other resource/identity) discovered by Veza.
You can filter results for entities with a given tag, create based on tags, or use them to add context and notes that other users can view and search by.
To apply a tag, you will need the ID of the node to modify. Calling will return IDs as part of the search result. You can also retrieve this value by clicking Show Details
for the entity in Authorization Graph, or checking the ID
column from Identity Data Entities or the Query Builder.
Generate a bearer token from .
Create, apply, and remove Veza tags
New in 2022.3.2: Tagging operations are now available as part of the
v1/
API set.
Post {VezaURL}/api/v1/graph/tags
Define a new tag that can be applied to any discovered entity, as a key:value pair. The tag value
is optional.
tag
body
Contains a single key:value pair
key
body
Max length 255 characters (alphanumeric and _
)
value
body
Max length 4096 characters (alphanumeric, _
and ,
).
A successful response will be empty ({}
).
Post {VezaURL}/api/v1/graph/nodes/tags
Apply one or more tags to an entity by providing an entity ID. A new Tag will be created if one doesn't already exist.
node_id
body
Veza entity ID
tags
body
Array of tags to add
To retrieve an entity ID, you can use the Query Builder API, or browse the Identity Data Entities catalog.
Post {VezaURL}/api/v1/graph/nodes/tags:remove
Remove a tag from an entity.
node_id
body
ID of the entity to modify
tag_key
body
Must contain a single tag to remove
A successful response will be empty ({}
).
Operations for adding, removing, and listing tags for entity enrichment.
Tag promotion for Access Reviews is currently available in Early Access. Please contact our support team to enable this capability.
Use these APIs to define the tags Veza should treat as customer-defined properties. Access Reviews that involve these entity types will include columns showing the tag name and value.
For example, in AWS, you may automatically tag identities with a 3rd-party security tool, or use tags to label S3 buckets containing sensitive data. When a tag is promoted, Veza Access Reviews will treat the tag as a built-in entity attribute, and show this information for reviewers in an optional column.
Add a promotion rule by specifying its type and key, and the entity types it applies to:
include_entity_types
: if true, promote tags for the listed type(s).
exclude_entity_type
: if true, promotes tags for all entities except the listed type(s).
AWSTag
CookieTag
(Veza Tag)
GoogleCloudLabel
Entity types for tag promotion should be concrete types. You can confirm the format by viewing details for any graph node, and checking the Type attribute, for example:
OAA.PagerDuty.User
ActiveDirectoryUser
OAA.custom_idp.IDPUser
Remove a promotion rule for the specified tag key and type. Demotions apply on the next data source parse.
Get all promotion rules for all entity types.
You can promote tags for any integration that supports them, such as Snowflake or Google Cloud. Use for integrations that do not support vendor-native tags or when built-in tagging is unavailable. Example tag types:
Adds a promoted tag. If a promoted tag with the same tag_key and tag_type already
exists, a unique constraint error will be returned without modifying the existing
promoted tag.
tag_key and tag_type specify the tag to be promoted
Only one or the other makes sense to be set. include_entity_types indicates promote only for the listed type exclude_entity_type indicates promote for any type except for the listed types The types should be concrete types, and OAA types should be supplied with their native types name, ie "OAA.ApplicationName.Type".