Mitigation Overview
Qualys Mitigation provides a way to fix those vulnerabilities for which a patch may not be a viable option. The Mitigation application reduces the risk of data loss and prevents the isolation of the affected asset until a patch is available to fix the threat. This enhances the data security without disconnecting the asset from the network and allows the customer to continue his business without interruption.
Although we have a robust solution of Patch management available to address the vulnerabilities, a patch may not always be a feasible option due to:
- Some vulnerabilities may need registry key changes that a patch deployment cannot update.
- Some end-of-life software (EOL) cannot be patched, and the only option is to uninstall the software.
- A high business risk with potential downtime impacting the business and customers
- Release of workarounds from vendors just a few weeks before a patch becomes available.
The mitigation application reduces the vulnerability effect's on the assets, resulting in a reduction of the impact factor. The Qualys Detection Score (QDS) score is reduced when the impact factor is reduced. The Mitigation job runs on Windows and Linux assets.
Introduction to Mitigation
Watch the following video to get an introduction to Mitigation.
Mitigation Script Signing in Qualys TruRisk Eliminate
All mitigation scripts authored by Qualys and distributed through TruRisk Eliminate are digitally signed by Qualys. The signature establishes that a script was published by Qualys and has not been modified since signing.
Mitigation scripts execute with elevated privileges and modify system configuration. Signature verification provides assurance of origin and integrity before execution on production assets.
Purpose of Script Signing
Mitigation scripts perform actions such as disabling services, modifying registry keys, editing configuration files, and blocking ports. Code with this level of access requires verifiable authenticity.
| Property | Description |
|---|---|
| Authenticity | The script carries the publisher's identity. The host confirms the script originated from Qualys. |
| Integrity | Any modification after signing invalidates the signature. Altered code is detected before execution. |
| Policy enforcement | Hosts configured to run signed code only can execute Qualys scripts without a policy change. |
| Accountability | Each execution is traceable to a named publisher, supporting audit and change-control requirements. |
| Reduced exceptions | Trust is granted to a single publisher certificate rather than to individual scripts or broad exclusions. |
Risks of Unsigned Script Execution
A host cannot distinguish legitimate unsigned code from altered unsigned code. This results in the following exposures:
- Tampering in transit or at rest. A script modified on the network, in a repository or on disk executes identically to the original.
- Supply-chain compromise. Management tools are a target because they already execute privileged code on every asset.
- Weakened host policy. Running unsigned scripts typically requires a PowerShell execution policy of Unrestricted or Bypass, which lowers the control for all scripts on the host.
- Audit gaps. Without a publisher identity, the author of code that changed a production system cannot be demonstrated.
Signing and Delivery Process
- Authoring. Mitigation logic is developed by Qualys from vendor, CISA and Qualys Threat Research Unit recommendations and mapped to the applicable QIDs.
- Signing. The completed script is signed with the Qualys code-signing certificate before release.
- Delivery. TruRisk Eliminate delivers the script to the Qualys Cloud Agent as part of a customer-created and approved mitigation job.
- Verification. The signature is validated on the asset. A script that fails validation is not executed.
- Reporting. Job results are returned to the platform and the vulnerability status is updated in VMDR.
Customer Considerations
- Execution policy. Qualys mitigation scripts run under AllSigned or RemoteSigned. Unrestricted or Bypass is not required.
- Publisher trust. Adding the Qualys code-signing certificate to the Trusted Publishers store, typically through Group Policy, covers all current and future Qualys mitigation scripts.
- Application control. Publisher-based rules in AppLocker or WDAC can allow Qualys-signed scripts without per-file hashes.
- Change management. Verified publisher identity and script integrity can be supplied as evidence for change approval.
- Audit. Signature status and publisher identity are recorded attributes available for each execution.
Signature Verification
On Windows, the signature of a Qualys mitigation script can be validated with PowerShell:
Get-AuthenticodeSignature -FilePath .\<script>.ps1 | Format-List Status, StatusMessage, SignerCertificate
Status must return Valid, and the signer certificate subject should name Qualys. HashMismatch means the script changed after signing and must not be run.
The effective execution policy on a host can be reviewed with:
Get-ExecutionPolicy -List