> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/jira/policies/detection_rules.md).
# Select Detection Rules in Nightfall for JIRA
Learn how you can select the required detection rules while creating a policy in Nightfall for JIRA.
Now you must create the detection rules that define the types of sensitive data that Nightfall scans and capture any violations.
A detection rule can be one detector or a combination of detectors and confidence levels/findings that will define a violation or finding and record it. The following table defines the rules for detectors.
To learn more about Detection Rules and how to set them up, refer [Detection Rules](https://app.nightfall.ai/detection-engine/detection-rules).
Nightfall recommends configuring a simple detection rule to start as shown below.
| Detector | Minimum Confidence | Minimum Count |
| ------------------------- | ------------------ | ------------- |
| Credit Card Number | Likely | 1 |
| US Social Security Number | Likely | 1 |
| API Key | Likely | 1 |
To select detection rules, select a detection rule from the list of rules that are displayed and then select one of the following options.
* **All Detection Rules**: Select this option to include all the detection rules in the policy.
* **Selected Detection Rules**: Select this option to include only that detection rule in the policy that you selected above.
* **Unselected Detection Rules**: Select this option to include all the other detection rules in the policy, that you did not select above.
Click **Next**.
---
# 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://help.nightfall.ai/jira/policies/detection_rules.md?ask=&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.
