-
Notifications
You must be signed in to change notification settings - Fork 612
[New] React2Shell Network Security Alert #5445
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
base: main
Are you sure you want to change the base?
Conversation
KQL query that reports network security signatures for React2Shell from 4 integrations (Suricata, Fortigate, Cisco FTD and PANW).
Rule: New - GuidelinesThese guidelines serve as a reminder set of considerations when proposing a new rule. Documentation and Context
Rule Metadata Checks
New BBR Rules
Testing and Validation
|
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
build-schemas -i cisco_ftd
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
Mikaayenson
left a comment
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.
nit: could add to the description that it combines signature/NGFW/IDS alert aggregation across Suricata/Forti/PANW/FTD, and complements the HTTP payload detections.
Co-authored-by: Mika Ayenson, PhD <[email protected]>
This reverts commit c97cf58.
…detection-rules into react_network_detection
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
they can see specifics in the tags or integrations, description states network security alerts. |
…detection-rules into react_network_detection
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
KQL query that reports network security signatures for React2Shell from 4 integrations (Suricata, Fortigate, Cisco FTD and PANW).