> 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/manually-build-an-application.md).

# Manually build an application

You can build your application by adding assets, starting from either the code or run side. This process covers your entire code-to-cloud journey: Code, Build, Deploy, Run. Your application is then automatically built from the assets you select on your chosen starting side, and other assets are added automatically based on their connections.

## Prerequisites

Before you begin, ensure you have connected the necessary data sources. Refer to [Onboard data sources](/application-security/application-security/onboard-data-sources.md) for more information.

## Steps

1. Under **Modules**, select **Application Security** → **Business Applications (under Application Management)** → **New Application** → **New Application**.
2. In the **Add a New Application** dialog box:
   1. Provide the required details:
      * **Application name** (required): A user-provided name
      * **Category** (required): Default - **Business Application**
      * **Description**: A description of the application. Provides context for users interacting with the application
      * **Business Criticality** (required): The level of importance of the application to your organization. This helps prioritize resources and attention based on the application's impact to your business objectives
      * **Business owner**: The individual or team responsible for the application from a business perspective
   2. Click **Create**.
3. On the **Applications** page, add assets to your application, starting with either code or cloud assets:

{% tabs %}
{% tab title="Code pane" %}

1. Select a version control system (VCS) from the list that is displayed.
2. Choose one or more of the following from their respective dropdown lists (multiple selections allowed): a specific VCS instance, an organization, or a repository.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>These filters are represented by icons displayed on the <strong>Code</strong> pane after selecting a VCS.</p></div>
3. Click **Done** (on the Code pane).

   After connecting your VCS, Prisma: Cortex automatically identifies and associates all build-time (such as source code, build scripts, Dockerfiles, CI tools), deploy (such as Kubernetes manifests, Helm charts, Terraform scripts), and runtime assets (such as running containers, virtual machines, cloud instances).
   {% endtab %}

{% tab title="Run pane" %}

1. Select an option:
   * Click **Add Assets by Provider** to select a cloud service provider
   * Click **Add Assets by Tag** or optionally select **Kubernetes Namespace**, **Kubernetes Cluster**, **VPC**, **Organization** or **Resource tag** to automatically populate the application with runtime assets associated with those entities. These filters are represented by an icon displayed under **Run** (after selecting a cloud provider)

2. Select an instance of your connected provider from the list that is displayed.

3. Click **Done** (on the Run pane).

   After connecting your cloud service provider, Cortex Cloud automatically identifies, associates and displays all Code (VCS repositories), build-time (such as source code, build scripts, Dockerfiles, CI/CD pipelines) and deploy assets (such as Kubernetes manifests, Helm charts, Terraform scripts).
   {% endtab %}
   {% endtabs %}

4. Click **Finish** to create the application.

   The application is displayed on both the All Applications and its dedicated asset page (business).

{% hint style="info" %}

### Note

To edit application assets, click the **Clear All** icon before clicking **Finish**. This clears all application data, allowing you to restart the application building process from the beginning.
{% 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 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/manually-build-an-application.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.