> 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/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues.md).

# Manage dynamic application testing (DAST) issues

Dynamic application security testing (DAST) attacks a running web application, including the APIs it exposes, and reports the weaknesses that the application's responses prove, such as SQL injection or cross-site scripting. When Bright reports a CWE for a finding, Cortex Cloud classifies the finding by CWE and by OWASP Top 10 category.

Cortex Cloud ingests DAST findings from **Bright Security** (Bright). Each finding is attached to the business application that its Bright project is mapped to. Cortex Cloud also creates API endpoint assets and an API specification from the entry points of each Bright project; see [Reference D: API endpoint inventory built from Bright data](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues/references/reference-d-api-endpoint-inventory-built-from-bright-data.md).

**Scope**: This guide covers connecting Bright, mapping Bright projects to business applications, creating policies for DAST findings, and investigating, prioritizing, and remediating DAST issues. Running scans, configuring scan targets, and choosing which tests Bright performs all happen in Bright, and are not covered here.

**Limitations**: Before setting up the integration, review the system constraints detailed in [Reference C: Limitations](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues/references/reference-c-limitations.md).

### Connect Bright Security

For **prerequisites** and **connection** steps, see [Bright Security](https://cortex-docs.paloaltonetworks.com/application-security/application-security/onboard-data-sources/ingest-third-party-data-sources/bright-security.md).

### Core achievements

* **Policy decides what enters the backlog**. An AppSec Policy turns only the DAST findings that match its conditions into DAST issues, and can override the issue severity. Findings that no policy matches do not create an issue
* **Urgency ranks issues by context, not severity alone**. Each DAST issue gets an Urgency level from the business criticality of its application, whether the affected assets are deployed and exposed, and whether its CWE is in the CWE Top 25 or OWASP Top 10
* **Every issue has an owner and a deadline**. You assign DAST issues, change their resolution status, and escalate them to a Case, as with other AppSec issues. A DAST issue carries an SLA when an SLA is defined
* **One backlog per application**. DAST issues appear beside the code, secrets, and supply chain issues of the same business application, so the application owner reviews all of them in one place

For how Cortex Cloud processes Bright results, see [Reference A: How Cortex Cloud processes Bright results](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues/references/reference-a-how-cortex-cloud-processes-bright-results.md) and [Reference B: Which Bright results Cortex Cloud ingests](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues/references/reference-b-which-bright-results-cortex-cloud-ingests.md).

### Next steps

* [Onboard Bright Security](https://cortex-docs.paloaltonetworks.com/application-security/application-security/onboard-data-sources/ingest-third-party-data-sources/bright-security.md)
* [Understand the DAST issues and findings tables](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues/understand-the-dast-issues-and-findings-tables.md)
* [Investigate, prioritize, and remediate DAST issues](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues/investigate-prioritize-and-remediate-dast-issues.md)
* [Create a policy for DAST findings](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues/create-a-policy-for-dast-findings.md)
* [Troubleshooting](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues/troubleshooting.md)
* [Reference A: How Cortex Cloud processes Bright results](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues/references/reference-a-how-cortex-cloud-processes-bright-results.md)
* [Reference B: Which Bright results Cortex Cloud ingests](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues/references/reference-b-which-bright-results-cortex-cloud-ingests.md)
* [Reference C: Limitations](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues/references/reference-c-limitations.md)
* [Reference D: API endpoint inventory built from Bright data](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues/references/reference-d-api-endpoint-inventory-built-from-bright-data.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 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/application-security/application-security-posture-management-aspm/manage-the-third-party-data-lifecycle/manage-dynamic-application-testing-dast-issues.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.
