> 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/aspm-command-center/operational-workflows.md).

# Operational workflows

The following workflows define the recommended operating procedures for maintaining and improving your Application Security posture.

## Workflow 1: Coverage management and gap resolution

**Context:** Coverage measures the gap between discovered entities and active security oversight. coverage is tracked across four critical dimensions:

* **Onboarding**: Ensuring all repositories and infrastructure are discovered and integrated
* **Scanner enablement**: Verifying that security tools are actively scanning all onboarded assets
* **Code to cloud**: Maintaining visibility across the entire lifecycle, from source code to runtime environments
* **Application mapping**: Linking technical assets to their specific business applications for context

Incomplete coverage creates blind spots and reduces the accuracy of prioritization.

**Posture review (AppSec manager):** Use the **Coverage** page to identify blind spots. Ensure Providers are at 100% to confirm all repositories are onboarded, and verify that scanners reach 100% to ensure those onboarded assets are being properly monitored.

**Execution (AppSec practitioner):** Select **Increase Coverage** to remediate identified gaps. From here, you can enable missing scanners for existing assets. To integrate unmonitored repositories into the platform, launch the onboarding wizard.

For more information about Coverage refer to [Coverage](/application-security/application-security-posture-management-aspm/coverage.md).

## Workflow 2: Posture hardening

**Strategy (AppSec manager):** Review the **Open After Guardrails** section of the **Prioritization and Aggregation** funnel to identify where issues bypass automated gates. Approve AI guardrails to harden the posture.

**Execution (AppSec practitioner):** Apply recommended guardrails. Each applied recommendation becomes a prevention policy. The policy enforces automatically at the configured triggers (PR scan, CI/CD build scan, and periodic scan), blocking matching findings before they progress through the pipeline.

For more information about Application Security policies, refer to [Unified Application Security policies](/application-security/application-security-posture-management-aspm/unified-application-security-policies.md).

## Workflow 3: Issue remediation

**Prioritization (AppSec manager):** Analyze prioritized issues and SLA violations to determine the highest risk based on business impact, breach impact, and breach probability.

**Execution (AppSec practitioner):** Use the **Issues and Cases** view to assign and track delegated items according to the urgency ranking.

**Validation (AppSec manager):** Verify that no **Urgent** or **Top Urgent** issues have exceeded your organization's defined SLAs.

## Workflow 4: SLA and MTTR tracking

**Monitoring (AppSec practitioner):** Review SLA and MTTR metrics to ensure remediation aligns with internal SLA targets. Select **SLA Violations** to drill into overdue cases.

**Escalation (AppSec practitioner):** Escalate persistent SLA violations with specific remediation deadlines and priority overrides.

**Validation (AppSec practitioner):** Confirm that SLA violation counts are decreasing over time.

For more information on Application Security SLA, refer to [Service Lead Agreements (SLA)](/application-security/application-security-posture-management-aspm/service-lead-agreements-sla.md).


---

# 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/aspm-command-center/operational-workflows.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.