# SDLC Inventory Modern software complexity demands an equally sophisticated build and deployment infrastructure. Software is typically built and deployed in production environments using pipeline commands. A **build/deploy pipeline** is based on a set of automated processes and tools, involving source control, build tools, continuous integration, testing automation (unit, integration and regression testing), validation, reporting, and distribution. The build/deploy pipeline assets, known as **SDLC assets**, are automatically discovered in the Xygeni platform. This creates an **inventory of SDLC assets** for the pipelines used within an organization. An SDLC Asset may present misconfigurations, leaked secrets, and other security issues which could be abused in software supply chain attacks. Common assets are code repositories, dependency graphs, package managers, build files, security tools, CI/CD workflows or IaC templates and provisioning scripts, along with the infrastructure, tools and extensions (such as plugins) used in the build / deploy pipelines. Security issues and unusual activity events are mapped to the target SDLC assets. The Inventory allows to reveal unknown, misconfigured and vulnerable SDLC systems and infrastructure, and perform *impact analysis*: dependencies between assets may be exploited by attackers to propagate the attack payloads. {% hint style="info" %} Read more about [SDLC Inventory](/xygeni-products/application-security-posture-management-aspm/inventory.md). {% endhint %} --- # Agent Instructions: 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: ``` GET https://docs.xygeni.io/introduction-to-xygeni/key-concepts/sdlc-inventory.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.