Identify and investigate gap

Cortex Cloud exposes lineage gaps and coverage metrics across multiple operational surfaces. A typical investigation flows down this list: start at the Coverage dashboard to find the business units and providers with the largest gaps, deep-link into the UAI to isolate the affected assets, then open the Code-to-Cloud tab on an individual asset to see why it is untraced and trigger the fix.

• The Coverage dashboard (organization level): Assess overall lineage maturity and find which business units or providers have the largest gaps. Use the dashboard toggles to include/exclude non-onboarded repositories or change your target destination to either the registry or runtime environment. For more information refer to The Coverage dashboard
• Unified Asset Inventory (asset inventory level): Filter code and cloud assets by their development cycle stages to identify traced and untraced lineage paths. For more information refer to C2C in Unified Asset Inventory
• The Code-to-Cloud tab (asset level) Located on individual asset side panels, this tab visualizes an asset's specific trace broken down by phases (Code → Build → Deploy →Runtime). For more information refer to C2C tab (asset level)
• Topology graph (application level): Located in the Business Applications view, this visualizes the interconnected path to production for a grouped set of application assets. For more information refer to C2C tab (app level)
• AI copilot integrations: AppSec Agentix and Cloud Posture Agentix answer natural-language questions about coverage percentages, application scopes, and provider-specific traces. For more information refer to Agentix for C2C
• Issue investigation (issue level): Side panels include a trace from the specific defect in the code to the impacted runtime resource, helping verify if a specific flaw is live in production. For more information refer to Investigate issues with C2C
• ASPM command center: Found in the Business Applications view, this graph visualizes the interconnected path to production for a grouped set of application assets. For more information refer to C2C in ASPM Command Center
• Policy enforcement (action level): Configure policies with runtime conditions derived from Code-to-Cloud lineage, such as blocking a build if it is destined for an internet-facing environment. For more information refer to Enforce policies with C2C