SenseOn SOC Playbook: Phishing
This page gives the process that SenseOn recommends to managed providers of SenseOn, to extend the investigation of incidents in end customer estates. It also gives best practice guidance for additional manual threat hunting and containment.
Process Flowchart

Identification
Identify the phishing email(s)
Joint action for customer and provider of SenseOn MDR
It is crucial to find the phishing email that one or more users in the estate received. With this email, you can learn more about the threat potential and assess it.
Identify number of affected mailboxes
Action for customer
Attackers frequently send phishing emails to multiple users. Thus, multiple mailboxes can receive the same email. For the later eradication stage, it is important to find all instances of the potential phishing email.
Analyse the email
Action for provider of SenseOn MDR
When you find and correctly analyse the email that a user received, you can get information about the threat. This information includes important IOCs, for example:
- The sender of the email.
- The IP address that the email went through.
- Any suspicious links in the email.
- If the email contained malicious files.
- If the email was part of a targeted attack or a blanketed attack. A targeted attack is on a specific user or a subset of users.
This information helps you to assess the depth and breadth of the attack, the compromise, or both.
If you find that the email contains a malicious file, get the file for further analysis. Take a hash of the file. Then follow the malware playbook.
If you find that the email contains a suspicious link, analyse the link. Find the nature of the link and what the potential attackers tried to get. An example is the credentials of users. Also assess the domain of the link. Find if the domain is related to any other attacks.
To analyse the link, you can use threat intelligence tools such as:
- URL Scan: A website that shows you the content of a webpage. You do not visit the site, thus you do not put yourself or your device at risk.
- VirusTotal: A threat intelligence platform that is free to use. Security vendors use it to share intelligence about files and network sources / destinations.
Assessing the wider estate using hunt lab
Action for provider of SenseOn MDR
Use Hunt Lab to assess the estate. Find if the same threat affected other users and devices. One method is to assess DNS records. Another method is to look for the link or file name in the commands that ran on the device. The queries that follow are examples:
Checking DNS
SELECT _time_observed,
source_hostname,
query_name
FROM network_dns
WHERE query_name in ['IOC1','IOC2']
Checking if a link has been seen in process telemetry
SELECT _time_observed, _hostname, username, command
FROM endpoint_process
WHERE lower(command) LIKE lower(‘%<place_phishing_domain_name_here>%’) --this should look something like ‘%google%’
ORDER BY _time_observed ASC
Checking if a file has been seen in process telemetry
SELECT _time_observed, _hostname, username, command
FROM endpoint_process
WHERE (lower(command) LIKE lower('%<place_filename_here>%')
OR lower(name) LIKE lower('%<place_filename_here>%')
OR lower(parent_name) LIKE lower('%<place_filename_here>%'))
ORDER BY _time_observed ASC
User correspondence
Action for customer
After you assess the full estate, speak to the users who clicked links or accessed files from the malicious mail. Find what actions they took and what occurred. This information can be of high value when you assess the impact of the phishing attack.
Containment
After you make sure that the email is malicious, you can use the steps that follow to contain the threat. This section is for emails that contain malicious links. If you found malicious files in emails, follow ‘PLB-001 Malware Playbook’.
User account actions
Action for customer
Do the actions that follow on each user account that clicked a link in a phishing email. Do these actions as a precaution, even if the user says that they did not enter credentials and only clicked the link.
Reset the user credentials, because it is possible that attackers stole them.
- End all current sessions for the users. Then the users must log in again with new credentials. This step is necessary because it is possible that attackers already used stolen credentials.
- Revoke all two factor authentication codes that are valid now for the user account. You can also reset the two factor authentication methods, because it is possible that the attackers changed these settings.
Recurrence Prevention
Action for customer
If other users received the email but did not access it yet, block the malicious domain and the related IP addresses. Then attackers cannot phish the other users in the estate also. The two main levels for the block are the firewall and DNS.
- You can use DNS filtering to stop DNS answers for DNS lookups of any suspicious IP addresses or URLs. This is only effective if all devices in the estate use a locally managed DNS solution.
- You can also use firewall rules to block the destination IPs of the malicious domain(s). Then the firewall blocks devices that try to connect to the domain(s). Typically, you do this at the perimeter firewall level.
- You can also use email filtering to block the email address that sent the malicious email.
Eradication
Action for customer
- Delete the email from the mailboxes that you found it in. Then users cannot get to it or interact with it again by mistake.
- For malicious files in emails, refer to the playbook ‘PLB-001 Malware‘ for Identification, containment, eradication and recovery.
Recovery
Action for customer
- Speak to users to make sure that they did not receive more similar or related emails.
- Make sure that users reset their credentials and configured their two factor authentication methods / mechanisms again.