-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add attack_pattern_kql field to MISP threat indicators #14470
Conversation
Pinging @elastic/siem (Team:SIEM) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice idea
evt.Put("source.ip", ip); | ||
break; | ||
case "link": | ||
attackPattern = '[' + 'url.full = ' + '\'' + v + '\'' + ']'; | ||
attackPattern = '[' + 'url:full = ' + '\'' + v + '\'' + ']'; | ||
attackPatternKQL = 'url.full: ' + '"' + v + '"'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might also want to search the http.request.referrer
URL?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The http record, that has the referrer URL as the url.full field, should have already matched the query. So this might not be needed. Otherwise, we will have duplicates.
Just a note: For the "AND" query, I will keep the relevant fields set; but for "OR" query, I will not set the fields since it will be taken as "AND". |
jenkins, test this |
* Add attack_pattern_kql field to MISP threat indicators (#14470)
Add attack_pattern_kql field to MISP threat indicators, so that detection engine can use it as threat indicator rules.