> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/search-and-investigate/application-asset-queries.md). # Application Asset Queries Use **Application Asset** queries to view your software development life cycle (SLDC) as a graphical representation that allows you to explore assets and connections, including data collected by Prisma Cloud from system environments and subscriptions. This visibility allows you to perform an in-depth analysis of security issues across your entire engineering ecosystem. You can understand the assets in your environment and the relationships between them. You cannot save the Application Asset queries queries under **Saved Queries** or run **Background Jobs**. From the Investigate page, you can access the Package Dependency graph that is within the Application Asset graph. You can explore the package dependencies from code repositories using the Simple Mode query builder and query about packages, licenses, and vulnerabilities. If the package you are exploring is a transitive one, you can view the dependency tree by clicking on the *indirect* edge. Make sure you have registered with the Cloud Application Security SCA module. Use cases of the Supply Chain graph, such as Image Referencer and IaC Resources Exploration, are not yet integrated into the Application Asset Graph. --- # 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://docs.prismacloud.io/content-collections/search-and-investigate/application-asset-queries.md?ask=&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.