"Newly Noncompliant" Report should include Specific Drifted Account or Setting
T
Thomas ONeal
When receiving a newly-noncompliant escalation for a control, the escalation page lists the steps to resolve but nothing about which account or setting triggered the escalation. For example, if we receive a notification that an administrative account now has an application license, the escalation should highlight which account that was (and Ideally the variable before/after that changed in order to trigger the escalation).
It seems like the data is already there based on the escalation text "Huntress detected a compliant security control becoming noncompliant", and this change would save technicians from needing to hunt down whatever account may have caused the alert.