Detection states and actions

The detection is new or no action has been taken yet. 

The detection has been resolved.

No automatically scheduled actions will be executed for this detection. (Manual actions will still be executed.)

The detection was resolved, but the fix has been reverted putting the file back in its original state.

The detection has been resolved, because the file was changed (outside of Patchman) or has been removed. Most likely the end user has updated his CMS to a newer version.

Detection of malicious code occurred and clean scheduled, but pending review by Patchman.

Detection of malicious code occurred and clean scheduled, but unable to clean automatically. Review by website owner required.

Resolve the vulnerability by patching the file.

Resolve the malware detection by moving it to quarantine.

Resolve the malware detection by removing the file.

This action is permanent and cannot be reverted.

Revert the vulnerability fix by restoring the original file.

Revert the malware by fix restoring the original file.

Block all automatically scheduled tasks of the detection.

Resume all automatically schedule tasks of the detection.

Remove detected malicious code from the file, leaving the file in place.

Revert the removal of detected malicious code from the file.