> 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/technologies/technology-overview.md).
# Technology Overview
**Technology Overview** provides an inventory of technologies in use across an organization’s software development delivery lifecycle such as AWS EC2, GitHub, Jenkins and so on. In addition, Technologies lists technologies that exist but that are not integrated into the environment, or suspected traces of technologies that remain after technologies have been removed. This information provides valuable insights and allows you to identify both known and unknown technologies in the organization, monitor the transition between technologies, and reduce the attack surface of the organization by removing unused assets and integrating technologies with Prisma Cloud. In addition, 'Technologies' enhances coverage by allowing you to properly onboard un-managed technologies that have been identified.
Integrating technologies in your environment not currently connected with the Prisma Cloud platform enhances your technology coverage, thereby improving your overall security posture.
To access 'Technologies', in **Application Security** select > **Home** > **Technologies**. The Technologies **Overview** page opens as the default view, displaying an inventory of technologies detected in the organization.
The Technology inventory table includes the following details.
* **Technology**: The detected technology
* **Category**: The category that the technology is assigned to, such as VCS, CI/CD and production
* **Source**: A list of data sources such as webhooks and applications detected in the organization, which provide evidence of the technology. See 'Source' in the the resource explorer below for more details
* **First Detected**: When the technology was first detected
You can search for data in the table through the search bar.
Selecting a technology in the inventory opens the **resource explorer** displaying additional information about the selected artifact.
* The **Overview** tab opens as the default view, providing metadata of the technology in your organization including a description, the category that the technology is classified as, when first and last detected, as well as the most recent evidence of the existence of the technology, or when evidence of a technology was removed
* The **Source** tab provides the integration with Prisma Cloud, integration status, the location and details of the evidence that the technology exists or may exist, or the remnants of the technology exist in your organization, divided by category that the evidence is classified as, such as CI Credentials, CI Plugins and so on. In addition, you can see the whether the technology is connected to Prisma Cloud. This will allow you to know whether your technology is protected
## Filters
You can apply the following filters to narrow a search for a technology.
* **Technology**: Filter by technology detected in the organization’s engineering environment
* **Category**: Filter by the environment in which the technology was detected such as CI/CD pipeline, VCS such as GitHub, production
* **Source**: Filter by data sources which provide evidence of the technology
* **First Detected**: Filter by date that the technology was first detected
---
# 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://docs.prismacloud.io/content-collections/application-security/visibility/technologies/technology-overview.md?ask=&goal=
```
`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.