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

URL remediation #16

Open
cudeso opened this issue Feb 16, 2023 · 1 comment
Open

URL remediation #16

cudeso opened this issue Feb 16, 2023 · 1 comment
Assignees
Labels
needs triage This issue has been automatically labelled and needs further triage playbook:activity=5 Playbooks for activity 5 playbook:state=proposal A 'proposal' for a new playbook

Comments

@cudeso
Copy link
Collaborator

cudeso commented Feb 16, 2023

The title of the playbook

URL remediation

Purpose of the playbook

This playbook uses a domain as input information from the analysts. It queries the domain reputation feeds, verifies with URLscan and Lookyloo. The analyst can then add the URL (as attribute and as an object) to a new or existing MISP event. The playbook then sends the URL to external providers such as Google, Microsoft and Phishtank. The URL is added to a Watchlist in Azure Sentinel and added to an Elasticsearch index. It then provides a summary of results and shares the results via Mattermost or Slack or as an alert in TheHive or DFIR-IRIS (to be discussed for implementation). This playbook is similar to the playbook on creating a MISP event for a phishing case (#1) , except that the focus is here only on a URL.

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, 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 16, 2023
@cudeso cudeso self-assigned this Feb 16, 2023
@cudeso cudeso added the playbook:activity=5 Playbooks for activity 5 label Dec 7, 2023
@cudeso
Copy link
Collaborator Author

cudeso commented Oct 11, 2024

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=5 Playbooks for activity 5 playbook:state=proposal A 'proposal' for a new playbook
Projects
None yet
Development

No branches or pull requests

1 participant