Skip to content

[New] Elastic Defend and Network Security Alerts Correlation #5332

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 13 commits into
base: main
Choose a base branch
from
Open

[New] Elastic Defend and Network Security Alerts Correlation #5332

wants to merge 13 commits into from
+103 −0

Conversation

@Samirbous
Copy link
Contributor

@Samirbous Samirbous commented Nov 18, 2025

This rule correlate any Elastic Defend alert with a set of suspicious events from Next-Gen Firewall like PAN and Fortigate by host.ip. This may indicate that this host is compromised and triggering multi-datasource alerts.

@Samirbous
[New] Elastic Defend and NG-Firewall Alerts Correlation
10b7b6e 
This rule correlate any Elastic Defend alert with a set of suspicious events from Next-Gen Firewall like PAN and Fortigate by host.ip. This may indicate that this host is compromised and triggering multi-datasource alerts.
@Samirbous Samirbous self-assigned this Nov 18, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 18, 2025

Rule: New - Guidelines

These guidelines serve as a reminder set of considerations when proposing a new rule.

Documentation and Context

  • Detailed description of the rule.
  • List any new fields required in ECS/data sources.
  • Link related issues or PRs.
  • Include references.

Rule Metadata Checks

  • creation_date matches the date of creation PR initially merged.
  • min_stack_version should support the widest stack versions.
  • name and description should be descriptive and not include typos.
  • query should be inclusive, not overly exclusive, considering performance for diverse environments. Non ecs fields should be added to non-ecs-schema.json if not available in an integration.
  • min_stack_comments and min_stack_version should be included if the rule is only compatible starting from a specific stack version.
  • index pattern should be neither too specific nor too vague, ensuring it accurately matches the relevant data stream (e.g., use logs-endpoint.process-* for process data).
  • integration should align with the index. If the integration is newly introduced, ensure the manifest, schemas, and new_rule.yaml template are updated.
  • setup should include the necessary steps to configure the integration.
  • note should include any additional information (e.g. Triage and analysis investigation guides, timeline templates).
  • tags should be relevant to the threat and align/added to the EXPECTED_RULE_TAGS in the definitions.py file.
  • threat, techniques, and subtechniques should map to ATT&CK always if possible.

New BBR Rules

  • building_block_type should be included if the rule is a building block and the rule should be located in the rules_building_block folder.
  • bypass_bbr_timing should be included if adding custom lookback timing to the rule.

Testing and Validation

  • Provide evidence of testing and detecting the expected threat.
  • Check for existence of coverage to prevent duplication.

@tradebot-elastic
Copy link

tradebot-elastic commented Nov 18, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Elastic Defend and NG-Firewall Alerts Correlation (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Nov 18, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Elastic Defend and NG-Firewall Alerts Correlation (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Nov 18, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Elastic Defend and NG-Firewall Alerts Correlation (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Nov 18, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Elastic Defend and NG-Firewall Alerts Correlation (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Nov 18, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Elastic Defend and NG-Firewall Alerts Correlation (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Nov 18, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Elastic Defend and NG-Firewall Alerts Correlation (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Nov 18, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Elastic Defend and NG-Firewall Alerts Correlation (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Nov 18, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Elastic Defend and NG-Firewall Alerts Correlation (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Nov 18, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Elastic Defend and NG-Firewall Alerts Correlation (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Nov 19, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Elastic Defend and NG-Firewall Alerts Correlation (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Nov 21, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Elastic Defend and Network Security Alerts Correlation (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@Samirbous Samirbous changed the title [New] Elastic Defend and NG-Firewall Alerts Correlation [New] Elastic Defend and Network Security Alerts Correlation Nov 21, 2025
@tradebot-elastic
Copy link

tradebot-elastic commented Nov 21, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Elastic Defend and Network Security Alerts Correlation (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Nov 21, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Elastic Defend and Network Security Alerts Correlation (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

w0rk3r
w0rk3r reviewed Nov 23, 2025
View reviewed changes
rules/cross-platform/multiple_alerts_elastic_defend_netsecurity_by_host.toml
@@ -0,0 +1,103 @@
[metadata]
creation_date = "2025/11/18"
Copy link
Contributor

@w0rk3r w0rk3r Nov 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add the integrations to the metadata

rules/cross-platform/multiple_alerts_elastic_defend_netsecurity_by_host.toml
type = "esql"

query = '''
FROM logs-* metadata _id
Copy link
Contributor

@w0rk3r w0rk3r Nov 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add the specific indexes? logs-* should be expensive

rules/cross-platform/multiple_alerts_elastic_defend_netsecurity_by_host.toml

query = '''
FROM logs-* metadata _id
| WHERE
Copy link
Contributor

@w0rk3r w0rk3r Nov 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| WHERE
| WHERE event.kind == "alert" and

rules/cross-platform/multiple_alerts_elastic_defend_netsecurity_by_host.toml
Comment on lines +57 to +65
Esql.event_module_distinct_count = COUNT_DISTINCT(event.module),
Esql.event_module_values = VALUES(event.module),
Esql.message_values = VALUES(message),
Esql.event_action_values = VALUES(event.action),
Esql.process_executable_values = VALUES(process.executable),
Esql.host_id_values = VALUES(host.id),
Esql.user_name_values = VALUES(user.name),
Esql.destination_ip_values = VALUES(destination.ip)
by Esql.source_ip
Copy link
Contributor

@w0rk3r w0rk3r Nov 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks expensive 👀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@w0rk3r w0rk3r w0rk3r left review comments

@Mikaayenson Mikaayenson Awaiting requested review from Mikaayenson Mikaayenson is a code owner

@eric-forte-elastic eric-forte-elastic Awaiting requested review from eric-forte-elastic eric-forte-elastic is a code owner

At least 2 approving reviews are required to merge this pull request.

Assignees

@Samirbous Samirbous

Labels

backport: auto Integration: Endpoint Elastic Endpoint Security integration: Fortinet Fortigate integration: PANW Rule: New Proposal for new rule

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@Samirbous @tradebot-elastic @w0rk3r @eric-forte-elastic