Addressing missing patches by creating remediation tasks is crucial for maintaining the security and stability of IT infrastructure. Saner CSRM provides a wizard-based approach to creating a remediation task for the missing patches.
Pre-requisite to Initiate the Remediation Task
- Navigate directly to the Top 10 Missing Patches block in the CSRM dashboard
- Choose the relevant tool: CSPM, CIEM, or CSPA to see the corresponding missing patches
- Click the Remediation Id link to initiate the process of creating a remediation task
The Create Patching Task window opens.
Step1: Select Resources
- From the list of Affected Services, choose the ones you want to remediate
- Use the checkbox to select or deselect resources as needed
- Click Next Step to proceed
Step2: Choose the Remediation Template to Apply
- Select the appropriate option to Review or configure the remediation settings for your patching task
- Once satisfied with the configuration, click Next Step
Step3: Schedule Job
- Enter the Task Name and Description in the required fields
- Use the dropdown to select one of the Remediation schedules:
- Immediate – To apply the remediation immediately
- Select Date & Time – To schedule the remediation for a specific time
- After entering the schedule details, click Next Step
Step4: Review and Consent
- Carefully review the patching task settings and configurations
- Provide your consent by selecting the checkbox that confirms settings have been reviewed and aligned with security and operational requirements
- Click Create Task to finalize and submit the patching task
Step5: Monitor Remediation Task
- Once created, the patch remediation task appears in the Remediation Status block on the CSRM (Cloud Security Remediation Management) dashboard
- Use this section to observe the progress and status(such as Pending Approval, Not Initiated, In Progress, Success, Failed, or Completed) of your patch remediation task
What do the different stages of patch remediation status mean?
— Pending Approval: The remediation job requires approval before execution. This stage ensures that all necessary stakeholders review the job and its impact before proceeding, reducing the risk of unintended consequences.
— Not Initiated: The remediation job is created but not yet started. This status indicates that prerequisites are not met, or the job is scheduled to start at a later time.
— In Progress: The remediation job is currently being executed. The system is actively applying fixes or patches to address the identified vulnerabilities or issues.
— Success: The remediation job has been completed successfully, and all targeted issues have been resolved as expected. No further action is required for this job.
— Failed: The remediation job did not complete due to errors or issues during execution. This status requires investigation to determine the root cause and potentially retry or escalate the job.
— Completed: status typically indicates that the remediation job has completed While “Completed” may overlap with “Success,” it could also include scenarios where the job ended with partial success or manual interventions.
What to do when you encounter an error message when creating a patching task?
You encounter the error message during patch task creation, typically when the target resources are invalid or inactive in the system, remediation template is not configured correctly, or schedule details are incorrectly specified.
As a precursory step, go ahead and revisit the previous steps:
- Select Resources: Ensure the target resources are valid and active in the syst
- Rem Template: Verify the selected remediation template is configured correctly
- Schedule Job: Double-check if the scheduling details, such as time, are correctly filled and conflict-free
If the issue still persists, click “Contact Support” in the interface to directly notify SecPod’s support team. Provide them with:
- A detailed description of the steps leading to the error
- Affected resources and templates used
- Logs or screenshots, including this error screen
- Any specific error codes or IDs visible in the logs
See Also