Overview
Adds or updates tags for one or multiple alerts. Tags can categorize alerts, help in filtering, and optionally trigger automatic rules based on tag creation. Supports auditing for traceability.Authorization Required: Include a valid Bearer Token in the Authorization header.
Endpoint Details
POST /api/utm-alerts/tags
Method: POST
Content-Type: application/json
Authentication: Bearer Token required
Response: HTTP 200 OK (no body)
Content-Type: application/json
Authentication: Bearer Token required
Response: HTTP 200 OK (no body)
Request Body
Array of alert UUIDs to update with tags
Array of tag strings to assign to the alerts (can be empty to remove tags)
Whether to automatically create a tag rule when assigning tags
JSON Schema
Request & Response Examples
Additional Code Examples
Response Details
Successful Update
- Success Response
- Error Response
The API returns HTTP 200 OK with no response body when tags are successfully updated.
Status Codes
Tags updated successfully
Invalid request payload or malformed JSON
Missing or invalid Bearer token
One or more alerts not found
Internal server error during tag update
Usage Examples
Add Investigation Tags
Mark as False Positive with Rule Creation
Remove All Tags
Bulk Tag Assignment
Tag Categories
Investigation Tags
Investigation Tags
Classification Tags
Classification Tags
Priority Tags
Priority Tags
Workflow Tags
Workflow Tags
Automatic Rule Creation
When
createRule
is set to true
, UTMStack automatically creates tag rules that will apply the same tags to future alerts matching similar criteria. This helps automate recurring tagging scenarios.Rule Creation Behavior
- Triggers: Based on alert patterns, source IPs, or rule names
- Scope: Applied to future alerts matching criteria
- Management: Rules can be viewed and modified in the UTMStack interface
- Audit: Rule creation is logged for compliance
Security Considerations
Security Notes:
- Requires Bearer token authentication
- All tag changes are audited for traceability
- Tag rules creation requires appropriate permissions
- Users without proper permissions will receive 401 Unauthorized
- Alert IDs must be valid UUIDs that exist in the system
Best Practices
Tag Naming Conventions
Tag Naming Conventions
Use consistent, descriptive tag names:
- Use title case: “False Positive” not “false positive”
- Be specific: “Network Scan” not “Scan”
- Use standard terminology: “Under Investigation” not “Looking at it”
Rule Creation Strategy
Rule Creation Strategy
Be selective with automatic rule creation:
- Use for repetitive, well-defined scenarios
- Avoid for one-off or complex cases
- Monitor rule effectiveness regularly
- Review and clean up unused rules
Tag Management
Tag Management
Maintain tag hygiene:
- Remove outdated or incorrect tags
- Standardize tag vocabulary across teams
- Use hierarchical tags when appropriate
- Document tag meanings and usage