> 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-runtime-security/cases-and-issues/create-an-initiative.md).

# Create an initiative

Create an initiative to track a long-term security program, and associate issues to it using a filter.

{% hint style="info" %}

#### Required licensing, scope, and permissions

* To create an initiative manually, you must have View/Edit permission for **Cases and Issues** selected under **Settings** → **Configurations** → **Access Management** → **Roles** → **Components** → **Cases & Issues**.
* Your access scope must include both the **Initiative** and the **Posture** case domains under **Settings** → **Configurations** → **Access Management** → **Scope** → **Case domain**. If either is missing, you can view initiatives but you cannot create them.
  {% endhint %}

An initiative is a type of case for tracking a long-term security program over weeks or months. Unlike standard cases, initiatives include only Posture issues that match a filter you define, limited to your access scope. Before you start, decide which issues represent the risk you want to address, and confirm that they fall within your access scope. For more information, see [Case initiatives](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cases-and-issues/overview-of-cases/case-initiatives.md).

#### How to create an initiative

1. On the **Cases** page, click **Create case**.
2. On the **Details** step, set **Domain** to **Initiative**, and enter the **Name**, **Description**, and **Severity**.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h4>Note</h4><p>You can assign a case to a single domain only, and you cannot change the assigned domain after creation.</p></div>
3. In **Initiative ETA**, select the target completion date.

   The ETA is required and must be tomorrow or later. Cortex Cloud creates a Resolution SLA rule for this initiative only, named **Initiative \<case ID>**, and uses it to track whether the initiative is on schedule.
4. Optionally, click **Add field** to add custom case fields.
5. Click **Next**. On the **Scope** step, filter the issues grid to define which issues belong to the initiative.

   As you build the filter, the grid shows the issues that currently match. You cannot filter by status or resolution.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h4>Note</h4><p>Filtering is the only way to associate issues with an initiative. The <strong>Create an issue</strong> and <strong>Select from existing issues</strong> options used for standard cases are not offered, and you cannot link or unlink issues manually after the initiative is created.</p></div>

   #### **How your access scope controls the issues shown**

   The issues displayed in the table are prefiltered by domain and your access scope. Therefore, you may not see the full set of Posture issues in the tenant. To see which asset groups your scope includes, hover over the **Access scope applied (SBAC)** note under the issues table.

   In practice, this means the following:

   * **The domain is fixed.** Every initiative filter is evaluated against the Posture domain.
   * **Your asset groups are applied.** The filter is limited to the asset groups in your scope.
   * **Your scope is captured at save time.** The scope that applies to the initiative is the one you had when you saved it. If your scope is widened or narrowed later, the initiative continues to use the scope captured at save time, and its issue membership does not change as a result. However, after creation, if you (or another user) edit the filter initiative is rescoped to match the updated scope. For more information, see [Edit an initiative](#edit-an-initiative).
   * **Scope is reapplied on every snapshot.** Because the captured scope is part of the stored filter, each snapshot matches issues against the same scope, so the initiative cannot drift outside it.

   Two users who build an identical filter can therefore end up with different initiatives, because each initiative is scoped to the user who saved it.

   An initiative can track up to 10,000 issues. If the filter matches more, the grid shows **Issues exceed the 10K limit**. Cortex Cloud still lets you save, but the first snapshot fails. Narrow the filter before you save, for example by restricting the severity, the asset group, or the issue subcategory.

   Only open issues are associated when the initiative is created. Issues that were already resolved are excluded.
6. Click **Next**. On the **Summary** step, review your entries.

   The summary is read-only. To change an entry, click **Back**.
7. Click **Save**.

   Cortex Cloud creates the initiative, associates the matching open issues, and starts the first snapshot in the background.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h4>Note</h4><p>An initiative can be created with zero associated issues. If that is not what you intended, edit the filter to broaden the match.</p></div>

A tenant supports up to 500 open initiatives. If the limit is reached, saving fails with the message **Initiative limit exceeded**. Resolve an existing initiative, or contribute to one that is already running, before creating another.

After the initiative is created, Cortex Cloud takes a snapshot every 12 hours, adding newly matching issues and removing issues that no longer match. To review progress, take a snapshot on demand, or troubleshoot a failed snapshot, see [Review an initiative](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cases-and-issues/create-an-initiative/review-an-initiative.md).

#### Edit an initiative

To edit an initiative, open it and select **Edit case** from the header menu. If the last snapshot failed, you can also click **Edit Filter** in the snapshot status line.

In the **Edit case** wizard, you can change the following:

* On the **Details** step: The name, description, and severity, and whether the initiative is starred (**Star case**).
* On the **Scope** step: The filter. You cannot edit the filter when you view a child tenant from an MSSP parent tenant.

Note the following before you change the filter:

* Saving a filter change triggers an immediate snapshot, which re-evaluates all issues against the new criteria and updates issue membership. Issues can be both added and removed as a result.
* If a snapshot is already running, the change is rejected, not queued. Wait for the running snapshot to finish, and then save again.
* Your current access scope is applied when you save the edited filter. If you are not the user who created the initiative and your scope differs, the initiative is rescoped to your scope.
* Saving a filter change resets the resolution cutoff to the time of the edit. Issues that were resolved before the edit are removed from the initiative, so the resolved count and progress drop. Earlier snapshots are not changed.

**Change the initiative ETA**

The **Initiative ETA** field is read-only in the **Edit case** wizard. To change the date, click **Edit** next to the field. Cortex Cloud opens the initiative's Resolution SLA rule on the **SLA Rules** page in a new browser tab.

{% hint style="info" %}

#### Note

Editing the Resolution SLA rule requires Object Setup permissions.
{% endhint %}


---

# 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-runtime-security/cases-and-issues/create-an-initiative.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.
