> 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/application-security/visibility.md). # Visibility Today’s engineering ecosystem consists of multiple teams and developers creating diverse applications using various technologies, operating at different stages of the development life cycle. These complexities create challenges, as organizations lack the visibility required to protect sensitive data, leaving it vulnerable to accidental leakage and intentional exfiltration by careless or malicious insiders. The Application Security module addresses these challenges by providing comprehensive visibility into your engineering environment across code repositories, contributors, technologies and connected pipelines. With this insight you can identify specific code risks and issues, allowing you to understand and prioritize remediation, and safeguard your engineering environment. | **What do you want to do?** | **Start here** | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | | View your entire engineering technical stack from repository to deployment in a repository-based view, which provides a map of your organization’s security posture. | [Repositories](/content-collections/application-security/visibility/repositories.md) | | View an inventory of technologies in use across your organization, including technologies that exist but are not integrated, or suspected traces of technologies that remain after technologies have been removed. This provides a comprehensive understanding of your technology landscape and allows you to remove unused assets, thereby enhancing security | [Technologies Overview](/content-collections/application-security/visibility/technologies/technology-overview.md) | | View an inventory of third party applications and webhooks detected in your VCS to gain insights into their usage across the organization, to remove unused instances, and to review and remove excessive permissions where not required | [VCS 3rd Parties](/content-collections/application-security/visibility/technologies/vcs-third-parties.md) | | View an inventory of Jenkins plugins across your organization’s Jenkins servers, allowing you to remove unused plugins and to assess, prioritize and remediate CVE vulnerabilities | [Jenkins Plugins](/content-collections/application-security/visibility/technologies/jenkins-plugins.md) | | View your SBOM in order to identify, analyze and remediate vulnerabilities and risks detected in dependencies | [SBOM](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/application-security/visibility/sbom/sbom.md) | | View artificial intelligence/ machine learning (AI/ML) open-source packages used in your codebase | [SBOM](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/application-security/visibility/sbom/sbom.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://docs.prismacloud.io/content-collections/application-security/visibility.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.