Saner Container Orchestration Remediation Management (CORM) tool presents a centralized platform for automating, monitoring, and optimizing remediation efforts across container orchestration systems. It allows administrators to evaluate the effectiveness of patching initiatives through intuitive charts, helping them prioritize tasks that provide the greatest security impact. By utilizing Patch Aging, older or high-risk vulnerabilities are highlighted to ensure that critical issues are addressed promptly. The Patching Impact analysis enables teams to focus on patches that affect the largest number of systems, maximizing operational efficiency.

Saner CORM also provides real-time oversight of remediation activities by monitoring and analyzing job statuses across multiple tools. Users can identify and prioritize the Top 10 Missing Patches, track the workflow status of remediation tasks, and review patch distribution by resource type. Additionally, insights into patch distribution across various tools allow administrators to assess coverage gaps and optimize patch deployment strategies, ensuring strong security and compliance throughout the cloud infrastructure.

Use Charts to Evaluate Effectiveness and Prioritize Patches

The Patch Aging and Patching Impact charts offer a thorough overview of the effectiveness of patch management.

The Patch Aging chart is a time-based line graph that illustrates the relationship between the number of pending patches and their age in days. This helps teams prioritize addressing older, high-risk vulnerabilities first. The chart visually indicates how long patches remain unapplied within an IT environment; upward trends suggest delays that increase exposure to security risks. Creative icons along the timeline represent different stages of patch aging, including growth, decline, and resurgence, enabling organizations to manage and track deployment timelines more effectively.

The Patching Impact chart emphasizes the success of remediation efforts by plotting the number of security rules fixed against the number of patches applied. The X-axis represents the number of patches applied, while the Y-axis displays the number of affected rules. Hovering over points on the chart reveals the direct impact of patching on reducing vulnerabilities or misconfigurations, assisting teams in prioritizing patches that provide the highest security benefits.

Prioritize and Address Older or High-Risk Anomalies with Patch Aging

A time-based line plot shows the correlation between the number of pending patches and their age in days, helping teams address older, high-risk vulnerabilities first.

The Patch Aging chart visually represents the duration during which patches remain unapplied in an IT environment. It illustrates the relationship between the number of pending patches and the number of days they have been outstanding.

This chart assists organizations in tracking and managing their patch deployment timelines. An upward trend indicates delays in patch deployment, which increases the organization’s exposure to vulnerabilities over an extended period. The creative visual employs characters or icons along the timeline to depict different stages of patch aging, including growth, decline, and subsequent resurgence.

From the Saner CORM dashboard, just go down to the “Patching Aging” block for further analysis.

Prioritize Patches Having Maximum Impact with Patching Impact

The Patching Impact chart helps you prioritize patches that have the maximum impact, ensuring critical misconfigurations are addressed first. The graph also illustrates the relationship between the number of patches applied and the reduction in the number of rules.   X-Axis indicates the number of patches applied Y-axis indicates the number of rules affected.

The point that you highlight by moving your cursor indicates the impact of patching on reducing vulnerabilities or misconfigurations.

Monitor and Analyze Job Status Across Tools

The Job Status dashboard block allows users to select a specific tool, COPM, COEM, or COPA, and view the status of its jobs in a structured table format.

The table includes important columns such as Name, Description, Overall Status, Type, Owner, and Resource Count, providing a clear overview of each job’s details and progress.

This setup enables teams to quickly assess operational health, track ongoing processes, and identify jobs that may require attention or intervention.

You have an option to sort the “Owner”column in both ascending and descending order, use the search box to quickly find specific entries, and export the data in CSV format for reporting purposes. Additionally, you can adjust the number of records shown, making navigation easier.

Identify and Prioritize the Top 10 Missing Patches

The Top 10 Missing Patches dashboard view allows users to select a tool: COPM, COEM, or COPA, and display the most critical missing patches in a table format.

This table includes essential columns such as Patch Name, Description, Severity, Affected Systems, Release Date, and Status, providing a clear overview of high-priority patches that require attention.

This feature helps teams swiftly identify vulnerabilities, prioritize remediation efforts, and reduce security risks across the environment.

Patch Count by Namespace

The Patch Count by Namespace radar chart in the CORM dashboard provides a clear, namespace-level view of patch distribution across the Kubernetes environment, helping teams quickly identify where remediation efforts are most needed. Each axis represents a namespace, and the distance from the center indicates the number of patches, allowing easy comparison of patch concentration across workloads. In this case the chart illustrates the default namespace has the highest patch count, signaling a priority for remediation, while others like prometheus and kube-system show moderate activity and some namespaces have minimal or no patches.

This visualization allows risk-based prioritization, targeted remediation, and improved visibility, ensuring efficient management of vulnerabilities without impacting the entire cluster.

View the Top Patch Count by Resource Type

The Top Patch Count by Resource Type dashboard block presents a bar graph that displays the number of patches associated with various resource types.

The x-axis represents the different resource types, while the y-axis indicates the corresponding patch counts.

Move your cursor over the bar to see the exact patch count for a specific resource type. Additionally, the data can be exported to a CSV file for further analysis or reporting.

Assess Patch-wise Distribution Across Tools

The Product-wise patch count chart allows for quick assessment of patch distribution across various container orchestration tools, namely COPM, COEM, and COPA, each represented by a unique color. Move your cursor over the chart to see the count for each tool.

This helps with focused investigation into areas or resources that have not been scanned or are missing patches, allowing users to prioritize patching based on the severity of misconfigurations.

The chart visually displays the patch counts for each tool, using the following color coding: Red for COPM, Gray for COPA, and Orange for COEM. Move your cursor over the different tools in the chart to see the count.

Additionally, you have the option to export detailed data to a CSV file for further analysis or reporting.