Notifications need to state what type of scan triggered the incident

The way we handle incidents with SCS had a workflow where, if auto protect caught the problem the machine was looked at but with less urgency. If a machine detected a trojan via a scheduled scan, we took it that the machine was comprimised and the machine needed to be removed from the network and looked at immediately.

The alerts with SEP do not state which type of scan triggered the notification:
realtime
startup
scheduled
manual
...

The SEP notificaitons need to be able to state what type of scan triggered the notification