A reversed fix no longer waits for the next audit
- Monday
SMBv1 is found enabled
A collection cycle reads the setting on a file server by PowerShell, without an agent. The check fails and a finding is raised.
- Monday
The remediation is documented
The asset’s Security page opens a drawer showing the expected value, the fix text and reference material on why the setting matters.
- Tuesday
The team applies the fix
SMBv1 is disabled with the team’s existing tools, and the next collection resolves the finding.
- Weeks later
The setting reverts
An older Group Policy undoes the change. The next collection reopens the same finding with its history intact.
- Next review
The cause is addressed
The reopened finding is on the Security page, so the team corrects the Group Policy itself. The finding’s history shows the full sequence for any later audit.
A composite example based on product behaviour.