Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a MISP event on a phishing incident with a link #1

Closed
cudeso opened this issue Feb 15, 2023 · 1 comment
Closed

Create a MISP event on a phishing incident with a link #1

cudeso opened this issue Feb 15, 2023 · 1 comment
Assignees
Labels
playbook:activity=1 Playbooks for activity 1 playbook:state=proposal A 'proposal' for a new playbook

Comments

@cudeso
Copy link
Collaborator

cudeso commented Feb 15, 2023

The title of the playbook

Create a MISP event on a phishing incident with a link

Purpose of the playbook

This playbook creates a MISP event for a phishing incident. The playbook sets default tags (taxonomies) and clusters on event and attributes. The playbook asks the analysts for the typical elements (e-mail headers, e-mail body, phishing URL) found in phishing cases and encodes these as attributes and objects in the event. The playbook creates relationships between the objects. The attributes are tagged with PAP and course-of-action matrix. The playbook queries MISP events and the enabled OSINT feeds for matches. If there is a phishing URL in the e-mail then URLscan is queried and the historical scan results and screenshots are collected. The URL is then submitted to Lookyloo for analysis. Where possible, the phishing URL is also reported to organisations such as Google, Microsoft and Phishtank. A final report with a list of indicators is summarised in the playbook and sent to Mattermost or Slack. The results can also be added as an alert to TheHive or as a case to DFIR-IRIS (to be discussed for implementation).

External resources used by this playbook

URLscan, Lookyloo, Mattermost (or Slack), TheHive (optional), DFIR-IRIS (optional), Google Safe Browsing, Microsoft Security Intelligence, Phishtank

Target audience

SOC, CSIRT

Breefly list the execution steps or workflow

No response

@cudeso cudeso added playbook:state=proposal A 'proposal' for a new playbook needs triage This issue has been automatically labelled and needs further triage labels Feb 15, 2023
@cudeso cudeso self-assigned this Feb 15, 2023
@cudeso cudeso added the playbook:activity=1 Playbooks for activity 1 label Mar 8, 2023
@cudeso cudeso removed the needs triage This issue has been automatically labelled and needs further triage label Mar 30, 2023
@cudeso
Copy link
Collaborator Author

cudeso commented Apr 18, 2023

Published with fd86309

@cudeso cudeso closed this as completed Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
playbook:activity=1 Playbooks for activity 1 playbook:state=proposal A 'proposal' for a new playbook
Projects
None yet
Development

No branches or pull requests

1 participant