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

# Business applications

Build and manage applications as holistic entities. Gain centralized visibility across the SDLC to monitor assets and remediate threats based on business risk.

Business applications (applications) provide a unified business view of code, open-source components, infrastructure, and runtime assets. They connect security findings to ownership and business context across the software development lifecycle (SDLC).

## Core capabilities

* **Creation methods**: You can build applications [manually](/application-security/application-security-posture-management-aspm/applications/manually-build-an-application.md), [programmatically via AP](/application-security/application-security-posture-management-aspm/applications/manage-applications-via-public-apis.md)I, or dynamically using **code** or **cloud** [Criteria](/application-security/application-security-posture-management-aspm/applications/defining-business-applications.md)
* **Risk management**: Use applications to define boundaries, assess risk, and prioritize remediation for your critical services
* **Access control**: [Application Scope-Based Access Control (SBAC)](/application-security/application-security-posture-management-aspm/applications/scope-user-access-to-applications-application-sbac.md) limits user access to assigned applications, supporting least-privilege access across data, issues, and policies

## View and manage applications

To review and maintain your existing applications, refer to [View and manage applications (UI)](/application-security/application-security-posture-management-aspm/applications/application-management-and-visibility.md).

## Business application assets

To visually explore asset relationships and gain deeper risk context across your environment, refer to [Business application assets](/application-security/application-security-posture-management-aspm/applications/business-application-assets.md).

## Related topics

* [Define business applications by Criteria](/application-security/application-security-posture-management-aspm/applications/defining-business-applications.md)
* [Manually build an application](/application-security/application-security-posture-management-aspm/applications/manually-build-an-application.md)
* [View and manage applications (UI)](/application-security/application-security-posture-management-aspm/applications/application-management-and-visibility.md)
* [Manage applications via public APIs](/application-security/application-security-posture-management-aspm/applications/manage-applications-via-public-apis.md)
* [Scope user access to applications (Application SBAC)](/application-security/application-security-posture-management-aspm/applications/scope-user-access-to-applications-application-sbac.md)
* [Business application assets](/application-security/application-security-posture-management-aspm/applications/business-application-assets.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/applications.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.