Creating and Managing Patching Tasks in SanerCVEM

Modified on Sun, 22 Jun at 4:16 PM

Purpose:
This article provides a step-by-step guide on how to create, manage, and monitor patching tasks using the Patch Management module in SanerCVEM. This is useful for automating remediation and ensuring systems are up to date.

Issues:

Need to patch vulnerable systems.
Need to manage scheduled or immediate patch deployments.
Monitoring patch deployment status.

Steps to Create and Manage Patching Tasks

Step 1: Log into the SanerNow Console
Go to https://saner.secpod.com and log in with your administrator credentials.

Step 2: Navigate to Patch Management Module
From the dashboard, click on Patch Management.

Step 3: Select Vulnerable Assets or Patches
Choose either:

Assets tab to select devices you want to patch.
Patches tab to apply a specific patch across devices.

Use filters to narrow down severity, KB numbers, or OS type.

Step 4: Create a New Patching Task
Click on Create Patching Task. Choose from the following task types:

Install(create installtion task)
Test and Deploy (for pre-production testing)

Enter a unique task name for easy tracking.

Step 5: Configure Patching Criteria
Define:

Execution Type: Immediate or Scheduled.
Reboot Options: Allow reboot, suppress reboot, or notify users.
Test and Deploy: If selected, you can define both test and production environments.

Click Next after configuring.

Step 6: Review and Submit
Verify all selections in the summary window.

Click Submit to deploy the patching task.

Step 7: Monitor the Task
Go to Patch Management > Status tab.

Here, you can track:

Success and failure rates
Reboot pending systems
Patch history by device or patch

Click on any task name to view logs and detailed asset-wise status.

Additional Notes:

Patch jobs can be paused or deleted from the Status tab if needed.
Always check device connectivity and agent status before scheduling a patch.
Ensure reboot policies align with business hours to avoid disruptions.
Use Test and Deploy for mission-critical systems to validate patches before rollout.