You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Severity should be effected by how sensitive a system is. For example a Mimikatz infection is much more serious when found on a domain controller than it is found on a normal user's workstation that contains little to no sensitive information.
So I would like to add an option to read in a list of hostnames considered sensitive (ex: DCs, file servers, domain admin machines, etc...) and bump up the alert severity level for each alert. (info will still stay the same, but low alerts will become medium, etc.. I am wondering what to do after critical though, -> fatal?)
I think most people won't know which machines are sensitive so it would be nice to automate this. Certain events only happen on DCs, file servers, etc.. so we could first scan for these events and then automatically generate a list of DCs and file servers.
The text was updated successfully, but these errors were encountered:
Severity should be effected by how sensitive a system is. For example a Mimikatz infection is much more serious when found on a domain controller than it is found on a normal user's workstation that contains little to no sensitive information.
So I would like to add an option to read in a list of hostnames considered sensitive (ex: DCs, file servers, domain admin machines, etc...) and bump up the alert severity level for each alert. (
info
will still stay the same, butlow
alerts will becomemedium
, etc.. I am wondering what to do aftercritical
though, ->fatal
?)I think most people won't know which machines are sensitive so it would be nice to automate this. Certain events only happen on DCs, file servers, etc.. so we could first scan for these events and then automatically generate a list of DCs and file servers.
The text was updated successfully, but these errors were encountered: