> 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/application-security/code-security/code-security-scanners/infrastructure-as-code-iac-misconfiguration-scanner/understand-the-iac-misconfigurations-table.md). # Understand the IaC misconfigurations table The **IaC Misconfigurations** page combines triage widgets with a detailed issue table. Use the widgets to identify priority work. Use the table to investigate and remediate specific IaC misconfiguration issues. Navigate to **Application Security > Issues > IaC Misconfigurations**. ## Widgets Use the widgets to identify and prioritize the most urgent issues before opening the detailed table. Selecting a widget value filters the table to matching issues. #### Urgency Breakdown The **Urgency** widget charts the count of open issues per Urgency level. Read the proportions rather than the absolute counts. Urgency for an IaC misconfiguration issue incorporates whether the template is deployed, how many resources the template provisioned, and whether those resources are internet-exposed. For more information, refer to [Urgency](/application-security/application-security-posture-management-aspm/urgency.md). #### SLA Status The **SLA Status** widget groups issues by SLA compliance status. #### Insights Each insight card pairs an Urgency level with another risk dimension and shows the number of issues matching both conditions. Dimensions include SLA status, deployment status, internet exposure, affected asset count, business criticality, and traceability completeness. ## IaC Misconfigurations table The **IaC Misconfigurations** table provides a consolidated view of misconfiguration issues. Each row represents an issue created when a scanner finding matches a unified policy. Each row links the misconfigured resource block to the detection rule that identified the misconfiguration, the template file and line range, the repository, the cloud resources the template deployed, and the triggering policy. The columns in this table are documented in a shared reference. For descriptions of every available column, the attributes common to all code scan issue tables and the attributes specific to this issue type, see [Issue table attributes reference](/application-security/code-security/code-security-scanners/issue-table-attributes-reference.md). ## Filter and sort the table Use the filter bar at the top of the IaC Misconfigurations table to narrow results by any filterable column. Common filtering strategies include: * **By severity**: Filter to Critical and High severity to focus on the most impactful misconfigurations * **By framework**: Filter to a specific IaC framework (such as Terraform) to scope remediation to a single technology stack * **By branch**: Filter to the main or production branch to focus on misconfigurations that affect production-bound code * **By resolution status**: Filter to New to identify untriaged misconfigurations, or to In Progress to monitor active remediation * **By Is Fixable**: Filter to True to identify misconfigurations with available automated fix pull requests ## Manage issues Right-click a row in the **IaC Misconfigurations** table to access the following actions. | Action | Description | | ------------------------------------------ | ----------------------------------------------------------------------------- | | **Change Status** | Modify the resolution status of the issue. Values: New, In Progress, Resolved | | **Change Severity** | Modify the severity level of the issue. Values: Critical, High, Medium, Low | | **Change Assignee** | Change the user or identity assigned to address the issue | | **Copy text to clipboard** | Copy the selected cell text | | **Copy entire row** | Copy the full row of data | | **Copy issue URL** | Copy the URL of the issue, to share or reference the issue | | **Show/hide rows with the severity level** | Show or hide all rows matching the severity level of the selected row | > **Note:** Correcting the template resolves the issue at the source. Correcting the deployed resource without correcting the template leaves the misconfiguration in place, and the next apply reintroduces the misconfiguration as drift. --- # 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/application-security/code-security/code-security-scanners/infrastructure-as-code-iac-misconfiguration-scanner/understand-the-iac-misconfigurations-table.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.