> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/integrations/integrating-security-scanning-tools/ai-bom-scan.md). # AI-BOM Scan AIBOM scan tool automatically analyzes a codebase, container, or cloud environment to generate an AI Bill of Materials — a structured inventory of the AI models, agents, datasets, and related components used in an application, primarily for security and compliance visibility. ### Usage of AI-BOM Scan in SSD * Delivery Shield uses AIBOM scanning to automatically detect AI inventory models, datasets, and AI agents referenced in your source code, containers, and pipelines. * Detected components are compiled into an AI Bill of Materials, giving visibility into the AI supply chain alongside your existing SBOM. * Findings from the AIBOM scan are correlated with your application's overall security posture and factored into the security score, extending risk visibility to AI-specific assets. ## To Integrate AI-BOM Scan * Navigate to Setup > Integrations. * In the Source panel, select AI-BOM. * The AI-BOM integration page is displayed. Click +New Account. * In the popup that appears, enter the details for the following fields. * Account Name - Enter a name for your account. * Enable the AI-BOM Scan toggle button. * Select the Teams and the corresponding Environments from the dropdown for which you want the integration to be available. The integration will be available for the selected teams and environment only. * You can select up to 5 teams for the integration to be displayed. * A sample is given below for reference: * In the example above, * If Team 1, Team 2, and Team 3 are selected, only applications associated with these teams can access the integration. Any applications belonging to other teams, such as Team 4, will not have access to this account. * Even if the user who created this account is also an admin for Team 4, the integration account remains restricted and is not available for Team 4. * Access to the account is strictly limited to the specified Teams and Environments selected during account creation. * For Organization Admins: * When an Organization Admin creates an account without selecting specific Teams and Environments, the account will be universally applicable, granting access to all teams and all environments by default. * For Team Admins with Multiple Teams: * If a Team Admin who manages multiple teams creates an account without specifying particular Teams and Environments, the account will only be accessible to the teams for which the logged-in user holds admin privileges. * Click Save. The tool is connected.