[New Rule] Destructive MongoDB Command

[eric-forte-elastic]

Pull Request

Issue link(s):

Related to https://github.com/elastic/ia-trade-team/issues/961

Summary - What I changed

Adds the Destructive MongoDB Command rule to expand network_traffic.mongodb protocol coverage.

The high-severity KQL rule identifies decoded MongoDB commands that drop databases, collections, indexes, users, or roles. These operations can indicate deliberate data destruction, application disruption, or wipe-and-extort activity against an exposed or compromised MongoDB service.

The query detects explicit destructive values in network_traffic.mongodb.method and inspects
network_traffic.mongodb.query for modern OP_MSG traffic that may report the generic msg method.

Note

This rule does require visibility into the plaintext Mongo DB commands, the primary purpose of this rule is to gauge customer interest in having MongoDB specific rules since we parse those fields (customer's may be having plaintext sensing behind Nginx and if so we can provide significant protection). Otherwise, there is little use to developing the Network traffic specific MongoDB rules.

How To Test

TRADE Stack or RTA

Checklist

• Added a label for the type of pr: bug, enhancement, schema, maintenance, Rule: New, Rule: Deprecation, Rule: Tuning, Hunt: New, or Hunt: Tuning so guidelines can be generated
• Added the meta:rapid-merge label if planning to merge within 24 hours
• Secret and sensitive material has been managed correctly
• Automated testing was updated or added to match the most common scenarios
• Documentation and comments were added for features that require explanation

Contributor checklist

• Have you signed the contributor license agreement?
• Have you followed the contributor guidelines?

[github-actions]

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.

[elastic-vault-github-plugin-prod]

⛔️ Test failed

Results

• ❌ Destructive MongoDB Command (kuery)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta

[Copilot]

Pull request overview

Adds a new Network Packet Capture detection rule to identify destructive MongoDB commands (drop DB/collection/index/users/roles) in decoded MongoDB protocol traffic, expanding network_traffic.mongodb coverage.

Changes:

• Introduces a new high-severity KQL query rule targeting destructive MongoDB commands via network_traffic.mongodb.method and decoded network_traffic.mongodb.query.
• Adds investigation guidance, false positive context, and setup requirements specific to MongoDB cleartext visibility.

[bryans3c]

The query had an error regarding wildcards and a filter that optimizes it. LGTM when changed!

[elastic-vault-github-plugin-prod]

⛔️ Test failed

Results

• ❌ Destructive MongoDB Command (kuery)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta

[elastic-vault-github-plugin-prod]

⛔️ Test failed

Results

• ❌ First-Time Destructive MongoDB Command from a Client IP (kuery)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta

[eric-forte-elastic]

New terms testing

[elastic-vault-github-plugin-prod]

⛔️ Test failed

Results

• ❌ First-Time Destructive MongoDB Command from a Client IP (kuery)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta

[elastic-vault-github-plugin-prod]

⛔️ Test failed

Results

• ❌ First-Time Destructive MongoDB Command from a Client IP (kuery)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta