Skip to content

Conversation

Aegrah
Copy link
Contributor

@Aegrah Aegrah commented Dec 17, 2024

Summary

This rule detects the creation of a simple HTTP web server using PHP or Python built-in modules. Adversaries may create simple HTTP web servers to establish persistence on a compromised system by uploading a reverse or command shell payload to the server web root, allowing them to regain remote access to the system if lost.

##Telemetry
0 hits in telemetry last 90d, only TPs in testing stack:
{415D2B16-6CCD-4DC8-9765-0EB4DC60B8FE}

@protectionsmachine
Copy link
Collaborator

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.
Copy link
Contributor

@terrancedejesus terrancedejesus left a comment

Choose a reason for hiding this comment

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

Added some thoughts on additional logic, but LTGM.

@Aegrah Aegrah merged commit e26e4e4 into main Jan 3, 2025
9 checks passed
@Aegrah Aegrah deleted the new-rule-simple-webserver-creation branch January 3, 2025 14:54
protectionsmachine pushed a commit that referenced this pull request Jan 3, 2025
protectionsmachine pushed a commit that referenced this pull request Jan 3, 2025
protectionsmachine pushed a commit that referenced this pull request Jan 3, 2025
protectionsmachine pushed a commit that referenced this pull request Jan 3, 2025
protectionsmachine pushed a commit that referenced this pull request Jan 3, 2025
protectionsmachine pushed a commit that referenced this pull request Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment