TruRisk™ Eliminate Release 4.2

Key Benefits

• Stop known faulty or high-risk patches from being deployed across your environment.
• Maintain deployment continuity without modifying or pausing existing patch jobs.
• Improve governance with a record of why each patch was blocked and who blocked it.
• Reduce troubleshooting effort with clear visibility into blocked patches and the rules affecting them.
• Save patch controls to specific asset tags or all assets, as per platforms, as required.
• Record a reason for every blocking rule to support auditability and future review.
• Validate patches on pilot systems before broader production rollout.

Navigate to Configuration > Patch Blocking Rules to create a blocking rule.

Improved Visibility into Blocked Patches

Blocked patches are now clearly identified in your deployment job results, so you always know which patches were held back and why. On the Patches tab, you can filter the blocked patches using the search filters.

In the patch list for a deployment job, a blocked patch is reported with the status Skipped and the following reason: Blocked by patch blocking rule "Feature update block rule". The patch applies to this asset but was not installed. Here, Feature update block rule is the name of the patch blocking rule.

Because the reason includes the rule name, you can identify which rule blocked the patch and review or update that rule directly.

The following are the benefits of the visibility of the job progress:

• Understand why a patch was skipped, without investigating the job configuration.
• Identify the specific rule responsible for blocking a patch.
• Review all blocked patches in one place and release them when they are ready for deployment.

Patch Blocking Rule Limits
- You can create a maximum of 10 blocking rules for each platform: Windows, Linux, and Mac. When the limit is reached, the Create Rule option is not available until you delete an existing rule.
- A rule blocks a maximum of 500 most recently published patches that match your criteria.
- You can select a maximum of five tags for each rule.

Key Benefits

• Reduce Deployment Risk

  Require a second reviewer to validate assets, patches, schedules, and deployment actions before jobs run. Help reduce deployment errors and strengthen patch governance.

• Strengthen Change Control

  Ensure critical deployment actions are reviewed and approved before reaching production.

• Track Every Decision

  View a complete approval history for each job, including approvals, rejections, comments, users, and time stamps. This helps to maintain a clear audit trail for compliance and operational reviews.

• Increase Accountability

  Clearly identify who requested, approved, rejected, or modified deployment actions.

Turn On the Job Approval Workflow

The Job Approval Workflow is optional and disabled by default. A Super Admin can enable or disable it in Configuration > Setup using the Job Approval Workflow toggle.

• Off (default): Jobs run through the existing process with no changes.
• On: All new jobs must be approved before they can be enabled and run.

Two roles and respective permissions control the workflow. You must have the Eliminate Job Approver role to approve or reject the job, and the Eliminate Manage Job Approval Config role to enable or disable the Job Approval Workflow.

• Enable Job Approval Workflow: The Eliminate Manage Job Approval permissions allow Super Admins or authorized users to turn the workflow on or off.
• Job Approval Permission: The Eliminate Job Approver permission allows designated reviewers to approve or reject submitted jobs.

The existing permissions are required to use this feature. For example, Approvers must also have View Any Job permission for the corresponding job type. A user cannot approve a mitigation job unless they can view mitigation jobs.

Submit, Review, and Track Job Approvals

Gain controlled job approvals, clear review feedback, and a complete audit trail for every deployment decision.

• Save &   Enable submits the job for approval and sets its status to Pending Approval. Save creates the job in a disabled state and lets you submit it later.
• Job owners and co-authors can submit, withdraw, edit, and resubmit approval requests.
• Approvers can review complete job details before choosing to Approve or Reject.
• The Job Approval History tab records all approval actions, comments, and status changes for audit purposes.
• Approvers can quickly find pending requests using the Approval Status filter.