PUT /admin/audit/anomalies/{anomaly_id}/status

Update audit anomaly status (open/acknowledged/investigating/resolved/dismissed), supports simultaneous assignment of analyst. References: ISO 27001:2022 Annex A.12.4 (Event Logging), PCI DSS v4.0 Req 10 (Log & Monitor).

Request Parameters

Name	In	Type	Required	Default	Example	Constraints	Description
id	path	string	Yes				Anomaly ID

Request Body

Schema: dto.UpdateAnomalyStatusRequest

Field	Type	Required	Example	Constraints	Description
status	string	Yes	investigating		Status
assignee	string	No	usr_analyst001		Analyst

Responses

Status	Description	Schema
200	Updated anomaly	dto.AnomalyDetailResponse
400	Invalid status value	dto.Problem
401	Unauthenticated	dto.Problem
404	Anomaly not found	dto.Problem
500	Internal server error	dto.Problem

Referenced Schemas

dto.AnomalyCommentResponse

Anomaly investigation comment

Field	Type	Required	Example	Constraints	Description
author_id	string	No	usr_analyst001		Commenter ID
author_name	string	No	Zhang San		Commenter name
content	string	No	Confirmed as false positive after investigation		Content
created_at	integer	No	1713175800		Timestamp
id	string	No	cmt_abc123		Comment ID

dto.AnomalyDetailResponse

Field	Type	Required	Example	Constraints	Description
code	integer	No
data	dto.AnomalyResponse	No
message	string	No
timestamp	string	No

dto.AnomalyResponse

Audit anomaly record

Field	Type	Required	Example	Constraints	Description
assignee	string	No	usr_analyst001		Analyst
comments	array of See dto.AnomalyCommentResponse	No			Comment
created_at	integer	No	1713175800		Creation timestamp
description	string	No	Detected 5 consecutive login failures		Description
detected_at	integer	No	1713175800		Detection timestamp
event_ids	array of string	No			Related event ID
id	string	No	ano_abc123		Anomaly ID
mitre_tactic	string	No	T1110		MITRE tactic
related_case_id	string	No			Related case ID
resolved_at	integer	No			Resolution timestamp
resolved_by	string	No			Resolver
severity	string	No	high		Severity
status	string	No	open		Status
tenant_id	string	No	tnt_abc123		Tenant ID
type	string	No	brute_force		Type
updated_at	integer	No			Update timestamp
user_id	string	No	usr_abc123		User ID

dto.FieldViolation

Field	Type	Required	Example	Constraints	Description
code	string	No			Code is the error code (optional) Used by programs to identify error types, e.g., "required", "format", "range"
description	string	No			Description is a human-readable error description Should explain what rule was violated, e.g., "Must be a valid email address"
field	string	No			Field is the path to the error field Uses dot notation for nested fields, e.g., "user.email" or "addresses[0].city"
value	object	No			Value is the value that caused the error (optional, used in development mode) May not be returned in production to avoid leaking sensitive information

dto.Problem

Field	Type	Required	Example	Constraints	Description
code	integer	No			Code is the business error code Used by programs to handle specific error scenarios Example: 30101001
detail	string	No			Detail is a human-readable explanation for this specific error instance Can contain specific error details, e.g., "Field 'email' is required"
errors	array of See dto.FieldViolation	No			Errors is a list of field-level validation errors (extension field) Follows Web API standard practices, each error contains field name and error message
i18n_args	object	No			I18nArgs are internationalization parameters Used to dynamically fill translation templates
i18n_key	string	No			I18nKey is the internationalization key Used for client-side localization of error messages Example: "error.user_not_found"
instance	string	No			Instance is the specific URI reference where the problem occurred Usually the request URL, may include query parameters Example: "/api/v1/users?limit=invalid"
request_id	string	No			RequestID is the unique request identifier Used for log correlation and issue tracking Example: "req_550e8400-e29b-41d4-a716-446655440000"
retry_after	integer	No			RetryAfter is used for 429 Too Many Requests responses Indicates the number of seconds the client should wait before retrying (RFC 6585)
service	string	No			Service is the service name Used in microservice architecture to locate the error source Example: "auth-service"
span_id	string	No			SpanID is the current span identifier Used to precisely locate the current node in a distributed trace
status	integer	No			Status is the HTTP status code generated Used by clients to distinguish problem types, does not change with Accept-Language Example: 400, 401, 403, 404, 500
timestamp	string	No			Timestamp is the error occurrence time ISO 8601 format Example: "2026-04-03T12:00:00Z"
title	string	No			Title is a short, human-readable summary of the problem type The same Type should always have the same Title (does not change per instance) Example: "Invalid Request Parameters"
trace_id	string	No			TraceID is the distributed tracing identifier Follows W3C Trace Context standard Example: "00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-01"
type	string	No			Type is a URI reference identifying the problem type When dereferenced, should provide human-readable documentation Example: "https://api.example.com/errors/invalid-request"