> 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-xdr/insights-and-tips-cortex-xdr/detection-engineering-and-threat-intelligence/detection-rule-change-management.md).

# Detection rule change management

Learn how to safely test, version, export, and audit detection rule changes in Cortex XDR.

Use the following practices to manage changes to detection logic safely.

| Content                                                              | How changes are tracked                                                                                                                                      |
| -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Rules, playbooks, and parsers delivered in Marketplace content packs | Versioned with the content pack. You can update or revert to a different pack version.                                                                       |
| Custom BIOC and correlation rules                                    | Changes are recorded in the management audit log. Before you make a significant edit, duplicate the rule or export it so you can restore the previous logic. |

### Recommended practice

1. **Duplicate before editing.** Keep a disabled copy of the original rule until the new version is validated.
2. **Export rules.** Export correlation rules and keep them in your own source control.
3. **Test in a dataset.** Set a modified correlation rule to **Save data to a dataset** first, compare the results with the original, then switch it to raise issues.
4. **Review the audit log.** Use [Monitor administrative activity](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/onboard-cortex-xdr/post-deployment-steps/set-up-your-environment/data-and-log-forwarding/forward-logs-and-data-from-cortex-xdr-to-external-services/monitor-administrative-activity) to see who changed which rule, and when.

See [Create a correlation rule](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/threat-management/detection-rules/whats-a-correlation-rule/create-a-correlation-rule) and [Create a BIOC rule](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/threat-management/detection-rules/whats-a-bioc/create-a-bioc-rule).


---

# 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-xdr/insights-and-tips-cortex-xdr/detection-engineering-and-threat-intelligence/detection-rule-change-management.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.