> 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.md).

# Configure Policies in Nightfall for Jira

Learn how to configure policies in Nightfall for Jira.

DLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. These policies also enable you to remediate any leakage of sensitive information from within your organization.

* You can set up policies to scan data that is sent through some or all applications within your organization. 
* You can configure policies and choose to not apply them all the time.

Before you define a policy, or a set of policies, we recommend that you define the objectives of each policy, which can then be fulfilled when you configure the policy.

Here are a few important questions to ask before configuring your policies:

* What data do you plan to monitor?
* Where within the organization do you want to monitor?
* What should be the scope of each policy?
* What conditions must apply for the policy to match?
* What exceptions/exclusions can be allowed?
* What remediation actions should the policy take?

You can now configure policies on the Jira integration to determine which projects must be monitored, and which ones excluded. You can also automate the remediation actions that you want Nightfall to perform on a policy violation.

Configuring DLP policies on Jira involves the following steps:

{% content-ref url="/pages/RjzQqPKXTY0L8GL907Rn" %}
[Jira App Selection](/jira/policies/integration.md)
{% endcontent-ref %}

{% content-ref url="/pages/nR1jTLykftn1dNAAULiD" %}
[Configure Scope in Nightfall for JIRA](/jira/policies/scope.md)
{% endcontent-ref %}

{% content-ref url="/pages/WasLjQx2N75IWIfWg7aK" %}
[Select Detection Rules in Nightfall for JIRA](/jira/policies/detection_rules.md)
{% endcontent-ref %}

{% content-ref url="/pages/9F5IpAoG68qYzlE7mm61" %}
[Configuring Advanced Settings in Nightfall for JIRA](/jira/policies/advanced_settings.md)
{% endcontent-ref %}

{% content-ref url="/pages/kW6kAJt9KUcoYqhcBBGG" %}
[Configure Risk Score for Jira](/jira/policies/risk_score.md)
{% endcontent-ref %}

{% content-ref url="/pages/XdZfSEHx7rxDygIkRbdY" %}
[Manage Jira Events](/jira/policies/events.md)
{% endcontent-ref %}


---

# 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.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.