> 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/application-security/application-security-posture-management-aspm/unified-application-security-policies/reference-e-grace-period-logic-and-configuration.md).

# Reference E: Grace period logic and configuration

The grace period provides a buffer between the discovery of a vulnerability and the enforcement of blocking policies.

Configuration steps

1. Select **Vulnerabilities** as the finding type.
2. Enable the **Grace Period** filter.
3. Enter the duration in days (**1–365**).

**Calculation logic**

* **Fix Date available**: `Expiry = Fix Date + Grace Period Days`
* **No Fix Date**: `Expiry = Publish Date + Grace Period Days`

**Behavioral matrix**

| Scenario                                | System behavior                                                                                                |
| --------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| **Grace period active + Block action**  | The match is recorded, but the block is suspended. A note is added to the PR/CLI indicating the remaining days |
| **Grace period expired + Block action** | The block action executes normally                                                                             |
| **Grace period active + Create Issue**  | The issue is created immediately with a Grace Period status indicator                                          |
| **Multiple matching grace periods**     | The system enforces the policy with the closest (soonest) expiry date                                          |

**Common SLA alignment patterns**

Use these durations to align security enforcement with your business unit’s Service Level Agreements (SLAs).

| Grace period | Recommended use case                       | SLA alignment |
| ------------ | ------------------------------------------ | ------------- |
| **7 days**   | Critical CVEs with a fix available         | Top Urgent    |
| **30 days**  | High severity CVEs (standard sprint cycle) | Urgent        |
| **90 days**  | Medium severity or CVEs without a fix      | Not Urgent    |

**Strategic Alignment**

Match grace period durations to the organization's SLA targets by Urgency tier Shorter grace periods for higher-Urgency findings enforce faster remediation; longer grace periods for lower-Urgency findings reduce developer friction without compromising security posture.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/unified-application-security-policies/reference-e-grace-period-logic-and-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.