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

JARM verification #19

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

JARM verification #19

cudeso opened this issue Feb 23, 2023 · 0 comments
Assignees
Labels
needs triage This issue has been automatically labelled and needs further triage playbook:activity=4 Playbooks for activity 4 playbook:state=proposal A 'proposal' for a new playbook

Comments

@cudeso
Copy link
Collaborator

cudeso commented Feb 23, 2023

The title of the playbook

JARM verification

Purpose of the playbook

This playbook takes a list of JARM fingerprints. The local MISP events and the enabled OSINT feeds are queried for matches and reported in the playbook. It then creates a new MISP event with the JARM fingerprints. The playbook then queries Shodan and Censys for these matches and collects the hostname and the information in the common name field found in the certificates. These attributes are added to the MISP event. It then queries the local MISP events and the enabled OSINT feeds for matches with these hostnames/domains. These matches are reported in the playbook. A final summary is added at the end of the playbook and shared via Mattermost or Slack or as an alert in TheHive or DFIR-IRIS (to be discussed for implementation).

External resources used by this playbook

Shodan, Censys, 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 23, 2023
@cudeso cudeso self-assigned this Feb 23, 2023
@cudeso cudeso added the playbook:activity=4 Playbooks for activity 4 label Nov 2, 2023
@cudeso cudeso closed this as completed in 20bad91 Jul 12, 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=4 Playbooks for activity 4 playbook:state=proposal A 'proposal' for a new playbook
Projects
None yet
Development

No branches or pull requests

1 participant