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 custom MISP warninglist #7

Closed
cudeso opened this issue Feb 15, 2023 · 0 comments
Closed

Create a custom MISP warninglist #7

cudeso opened this issue Feb 15, 2023 · 0 comments
Assignees
Labels
needs triage This issue has been automatically labelled and needs further triage 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 custom MISP warninglist

Purpose of the playbook

This playbook creates a custom MISP warninglist with a set of entries provided by the analyst as input. A check is done if the warninglist already exists. If the warninglist already exists then the entries are added to the existing warninglist. When the warninglist is created the MISP events are queried for matches. The playbook also queries Shodan and VirusTotal for matches with entries in the warninglist. The result of the creation of the warninglist as well as the matches is summarised at the end of the playbook and sent to Mattermost or Slack or added as an alert in TheHive or DFIR-IRIS (to be discussed for implementation). A typical use case is adding company internal assets (IPs, domains) to a warninglist.

External resources used by this playbook

Shodan, VirusTotal, Mattermost (or Slack), TheHive (optional), DFIR-IRIS (optional)

Target audience

SOC, CSIRT, CTI

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 18, 2023
@cudeso cudeso closed this as completed in 5177d67 Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage This issue has been automatically labelled and needs further triage 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