Skip to content

[New] Suricata and Elastic Defend Network Correlation #5443

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
Samirbous wants to merge 19 commits into
base: main
Choose a base branch
from
Open

[New] Suricata and Elastic Defend Network Correlation #5443

Samirbous wants to merge 19 commits into from

Conversation

@Samirbous
Copy link
Contributor

@Samirbous Samirbous commented Dec 10, 2025

This detection correlates Suricata alerts and events with Elastic Defend network events to identify the source process performing the network activity.

@Samirbous
[New] Suricata and Elastic Defend - Command and Control Correlation
e749279 
This detection correlates Suricata alerts and events with Elastic Defend network events to identify the source process
performing the network activity.
@Samirbous
Update command_and_control_suricata_elastic_defend_c2.toml
e5eee69
@Samirbous Samirbous self-assigned this Dec 10, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 10, 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 Dec 10, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Suricata and Elastic Defend - Command and Control Correlation (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@Samirbous Samirbous changed the title [New] Suricata and Elastic Defend - Command and Control Correlation [New] Suricata and Elastic Defend Network Correlation Dec 10, 2025
@tradebot-elastic
Copy link

tradebot-elastic commented Dec 10, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Suricata and Elastic Defend Network Correlation (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Dec 10, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Suricata and Elastic Defend Network Correlation (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Dec 10, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Suricata and Elastic Defend Network Correlation (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Dec 10, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Suricata and Elastic Defend Network Correlation (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Dec 10, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Suricata and Elastic Defend Network Correlation (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

w0rk3r
w0rk3r reviewed Dec 10, 2025
View reviewed changes
@tradebot-elastic
Copy link

tradebot-elastic commented Dec 10, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Suricata and Elastic Defend Network Correlation (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Dec 10, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Suricata and Elastic Defend Network Correlation (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Dec 10, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Suricata and Elastic Defend Network Correlation (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Dec 10, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Suricata and Elastic Defend Network Correlation (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Dec 10, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Suricata and Elastic Defend Network Correlation (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Dec 17, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Suricata and Elastic Defend Network Correlation (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link

tradebot-elastic commented Dec 17, 2025 •
edited
Loading

⛔️ Test failed

Results
  • ❌ Suricata and Elastic Defend Network Correlation (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

Mikaayenson
Mikaayenson approved these changes Dec 17, 2025
View reviewed changes
rules/cross-platform/command_and_control_suricata_elastic_defend_c2.toml
type = "eql"
query = '''
sequence by source.port, source.ip, destination.ip with maxspan=1m
[network where event.module == "suricata" and event.kind == "alert" and event.severity != 3 and source.ip != null and destination.ip != null]
Copy link
Contributor

@Mikaayenson Mikaayenson Dec 17, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

Suggested change
[network where event.module == "suricata" and event.kind == "alert" and event.severity != 3 and source.ip != null and destination.ip != null]
[network where event.dataset == "suricata.eve" and event.kind == "alert" and event.severity != 3 and source.ip != null and destination.ip != null]

Unfortunately needed for repo specific tests to pass. Also not sure if event.kind should be signal for suricata.

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

Reviewers

@Mikaayenson Mikaayenson Mikaayenson approved these changes

@w0rk3r w0rk3r w0rk3r approved these changes

@eric-forte-elastic eric-forte-elastic Awaiting requested review from eric-forte-elastic

@traut traut Awaiting requested review from traut

Assignees

@Samirbous Samirbous

Labels

backport: auto Domain: Endpoint Domain: Network patch Rule: New Proposal for new rule

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@Samirbous @tradebot-elastic @Mikaayenson @w0rk3r