> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-api/cortex-platform/analytics-rules-abiocs.md).

# Analytics Rules (ABIOCs)

APIs for managing analytics (ABIOC) detection rules

## Override analytics rule severities

> Create a severity override for one or more severity variations of an analytics (ABIOC) detection rule.\
> \
> An analytics rule can raise alerts at more than one severity. Each distinct severity path through the rule is a severity variation, identified by its own variation ID. This endpoint sets an explicit severity for the variations you list, replacing the severity defined by the rule content.\
> \
> Override a severity to lower it for a rule that produces suspected false positives and reduce the number of issues raised, to raise it so that a specific behavior reliably generates issues, or to pin it so that the variation keeps your value regardless of later changes to the default.\
> \
> \- Send either every variation or only the variations you are changing. Variations you omit keep their existing override.\
> \- To override the base severity of the rule, use the \`global\_rule\_id\` value itself as a key in \`severities\_override\`.\
> \- Sending a variation with the severity that the rule content already defines resets that variation: the stored override is removed and the variation reverts to its default severity.\
> \- An override is immune to content updates. Default severities are maintained by content updates, but a variation that carries an override keeps the severity you set. A content update can therefore bring a default into line with an override you set earlier, in which case resetting that variation produces no change.\
> \- The rule identified by \`global\_rule\_id\` must be active and non-silent.\
> \- All overrides in a single request are applied as one transaction.\
> \
> \*\*Warning:\*\* Overriding the severity of a detection rule can prevent issues from being raised, or cause an excessive number of issues to be raised. Assess the effect of each override before you apply it.\
> \
> Validation failures are returned with HTTP 200 and \`reply.success\` set to \`false\`. Inspect \`reply.success\` rather than the status code to confirm that the override was applied.\
> \
> \*\*Required license:\*\* Cortex Cloud Runtime Security or Cortex Cloud Posture Management.\
> \
> \*\*Required permission:\*\* Detections > Rules > View/Edit

```json
{"openapi":"3.0.0","info":{"title":"Cortex Cloud Platform APIs","version":"Cortex Cloud 2.3"},"tags":[{"name":"Analytics Rules (ABIOCs)","description":"APIs for managing analytics (ABIOC) detection rules"}],"servers":[{"url":"https://api-yourfqdn"}],"paths":{"/public_api/v1/abioc/override":{"post":{"tags":["Analytics Rules (ABIOCs)"],"summary":"Override analytics rule severities","operationId":"post-public_api-v1-abioc-override","description":"Create a severity override for one or more severity variations of an analytics (ABIOC) detection rule.\n\nAn analytics rule can raise alerts at more than one severity. Each distinct severity path through the rule is a severity variation, identified by its own variation ID. This endpoint sets an explicit severity for the variations you list, replacing the severity defined by the rule content.\n\nOverride a severity to lower it for a rule that produces suspected false positives and reduce the number of issues raised, to raise it so that a specific behavior reliably generates issues, or to pin it so that the variation keeps your value regardless of later changes to the default.\n\n- Send either every variation or only the variations you are changing. Variations you omit keep their existing override.\n- To override the base severity of the rule, use the `global_rule_id` value itself as a key in `severities_override`.\n- Sending a variation with the severity that the rule content already defines resets that variation: the stored override is removed and the variation reverts to its default severity.\n- An override is immune to content updates. Default severities are maintained by content updates, but a variation that carries an override keeps the severity you set. A content update can therefore bring a default into line with an override you set earlier, in which case resetting that variation produces no change.\n- The rule identified by `global_rule_id` must be active and non-silent.\n- All overrides in a single request are applied as one transaction.\n\n**Warning:** Overriding the severity of a detection rule can prevent issues from being raised, or cause an excessive number of issues to be raised. Assess the effect of each override before you apply it.\n\nValidation failures are returned with HTTP 200 and `reply.success` set to `false`. Inspect `reply.success` rather than the status code to confirm that the override was applied.\n\n**Required license:** Cortex Cloud Runtime Security or Cortex Cloud Posture Management.\n\n**Required permission:** Detections > Rules > View/Edit","parameters":[{"schema":{"type":"string"},"in":"header","name":"Authorization","description":"{api_key}","required":true},{"schema":{"type":"string"},"in":"header","name":"x-xdr-auth-id","description":"{api_key_id}","required":true}],"requestBody":{"required":true,"content":{"application/json":{"schema":{"type":"object","required":["update_data"],"properties":{"update_data":{"type":"object","description":"Identifies the analytics rule to update and the severity overrides to apply to its variations.","required":["global_rule_id","severities_override"],"properties":{"global_rule_id":{"type":"string","description":"Global rule ID of the analytics rule to update. The rule must be active and non-silent."},"severities_override":{"type":"object","description":"Maps each severity variation ID to the severity that variation must raise. Use the `global_rule_id` value as a key to override the base severity of the rule. A variation sent with the severity already defined by the rule content is reset to its default.","additionalProperties":{"type":"string","description":"Severity that the variation must raise.","enum":["SEV_010_INFO","SEV_020_LOW","SEV_030_MEDIUM","SEV_040_HIGH","SEV_050_CRITICAL","SEV_090_UNKNOWN"]}}}}}}}}},"responses":{"200":{"description":"OK. Inspect `reply.success` to confirm that the override was applied: validation failures are also returned with HTTP 200.","content":{"application/json":{"schema":{"type":"object","properties":{"reply":{"type":"object","description":"Outcome of the override.","properties":{"success":{"type":"boolean","description":"Whether the severity overrides were applied."},"reason":{"type":"string","description":"Explanation of why the request was rejected. Returned only when `success` is `false`."}}}}}}}},"400":{"description":"Bad Request. Got invalid JSON.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/reply"}}}},"401":{"description":"Unauthorized access. An issue occurred during authentication. This can indicate an incorrect key, id, or other invalid authentication parameters.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/reply"}}}},"402":{"description":"Unauthorized access. User does not have the required license type to run this API.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/reply"}}}},"403":{"description":"Forbidden access. The provided API Key does not have the required RBAC permissions to run this API.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/reply"}}}},"500":{"description":"Internal server error. A unified status for API communication type errors. Also returned when no active non-silent analytics rule matches `global_rule_id`.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/reply"}}}}}}}},"components":{"schemas":{"reply":{"type":"object","title":"reply","description":"The query result upon error.","properties":{"err_code":{"type":"string","description":"HTTP response code."},"err_msg":{"type":"string","description":"Error message."},"err_extra":{"type":"string","description":"Additional information describing the error."}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-api/cortex-platform/analytics-rules-abiocs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
