Metadata
Request Metadata
Dashboard users may add arbitrary metadata to their Guard API requests to enable more detailed analysis of requests in the Dashboard.
Metadata use cases
Metadata can be configured for any request associated with a Project or as part of each individual request. This provides flexibility to combine session-specific metadata with more general application metadata for each request.
The context that this metadata provides in your Dashboard can help identify suspicious activity patterns and users or even identify specific attacks as they are happening. Eventually, you'll be able to export logs from Guard that include this metadata to your Security Information and Event Management (SIEM) system of choice for further analysis.
Project metadata
Common use cases for Project metadata include:
Environment: Attach the environment name to the metadata. This can help identify suspicious activity in specific environments or allow you to compare performance between production and testing environments.
Application ID: Attach the application ID to the metadata. This can help identify suspicious activity in specific applications in your ecosystem or allow you to compare performance between different applications.
To connect Project metadata to a request, you must include the project_id
as part of the request's metadata.
Request metadata
Common use cases for request metadata include:
User ID: Attach the user ID of the user making the request to the metadata. This can help identify suspicious users or patterns of behavior.
Session ID: Attach the session ID of the user making the request to the metadata. This can help identify suspicious sessions or patterns of behavior.
Attaching metadata to requests
Metadata can be attached to requests using the metadata
property in the request body. The metadata
property is an object that can contain any arbitrary key-value pairs.
Examples
Python
Last updated