> 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/cortex-cloud-posture-management/cloud-inventory-and-environment/asset-classes/code-and-ci-cd-assets.md). # Code and CI/CD assets The Code asset class provides visibility into your Software Development Lifecycle (SDLC), helping you identify and mitigate risks introduced during the build and deployment processes. ### Code and CI/CD categories The inventory tracks several distinct asset categories to help secure your software supply chain. You can view an aggregated summary of All Code Assets, or filter by the following specific categories: * **IaC Resources:** Tracks Infrastructure-as-Code resources to manage misconfigurations and ensure compliance with security standards. * **Repositories:** Tracks version control repositories (e.g., GitHub, GitLab) where source code is hosted. * **VCS Organizations:** The top-level structures within VCS platforms that contain your repositories, code, and configurations. * **CI/CD Pipelines:** Tracks the automated workflows that build, test, and deploy your software. * **CI/CD Instances:** Tracks the pipeline tool instances (like Jenkins or GitHub Actions) that execute your automated workflows. * **Software Packages:** Tracks open-source software packages to manage vulnerabilities (CVEs), package operational risks, and license misconfigurations. ### Code to cloud traceability A key feature of code security assets is the code to cloud tab available on asset side cards. Code to cloud context is a correlation engine that maps the full lineage of assets across the SDLC. By deterministically connecting repositories, pipelines, images, and runtime resources (including VMs and IaC-defined infrastructure) back to their originating code, it provides end-to-end bidirectional traceability. This allows analysts to trace runtime issues back to the specific line of code, developer, or pipeline that introduced them/ ### Code security issue visibility Code Security issues are organized into dedicated issue tables based on the scanner type (such as Secrets, SCA, CI/CD Risks, and IaC misconfigurations). However, these dedicated tables are filtered to only display issues generated from findings detected during periodic scans. If you need to view issues detected during pull request (PR) or continuous integration (CI) scans, you must navigate to the Issues page, which unifies all issues regardless of their detection source. --- # 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/cortex-cloud-posture-management/cloud-inventory-and-environment/asset-classes/code-and-ci-cd-assets.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.