Skip to content
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

[Deprecate] LaunchDaemon Creation or Modification and Immediate Loading #4547

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

DefSecSentinel
Copy link
Contributor

Summary

In my tuning PR (#4546) I updated the LaunchAgent Creation or Modification and Immediate Loading rule to encompass both Launch Daemons and Launch Agents using our newer Persistence event eliminating the need for this rule. The new rule name is Launch Service Creation and Immediate Loading.

Copy link
Contributor

Rule: Deprecation - Guidelines

These guidelines serve as a reminder set of considerations when recommending the deprecation of a rule.

Documentation and Context

  • Description of the reason for deprecation.
  • Include any context or historical data supporting the deprecation decision.

Rule Metadata Checks

  • deprecated = true added to the rule metadata.
  • updated_date should be the date of the PR.

Testing and Validation

  • A prior rule tuning occurred for the rule where Deprecated - is prepended to the rule name, and the rule has already been released.
  • Rule has be moved to the _deprecated directory.
  • Double check gaps potentially or inadvertently introduced.
  • Provide evidence that the rule is no longer needed or has been replaced (e.g., alternative rules, updated detection methods).

@tradebot-elastic
Copy link

tradebot-elastic commented Mar 19, 2025

⛔️ Tests failed:

  • ❌ LaunchDaemon Creation or Modification and Immediate Loading (eql)
    • coverage_issue: deprecated_with_rta
    • stack_validation_failed: no_alerts - 0 alerts

integration = ["endpoint"]
maturity = "production"
updated_date = "2025/02/04"
deprecation_date = "2025/03/19"
Copy link
Contributor

Choose a reason for hiding this comment

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

We need to change the name of the rule in the current releae, push and then wait for release cycle before we deprecate. Sample #4537

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.

Pending name change to include Deprecate - suffix and remove final deprecation stages.

@tradebot-elastic
Copy link

tradebot-elastic commented Mar 21, 2025

⛔️ Tests failed:

  • ❌ LaunchDaemon Creation or Modification and Immediate Loading (eql)
    • coverage_issue: deprecated_with_rta
    • stack_validation_failed: no_alerts - 0 alerts

@tradebot-elastic
Copy link

tradebot-elastic commented Mar 26, 2025

⛔️ Test failed

Results
  • ❌ LaunchDaemon Creation or Modification and Immediate Loading (eql)
    • coverage_issue: deprecated_with_rta
    • stack_validation_failed: no_alerts - 0 alerts

@tradebot-elastic
Copy link

tradebot-elastic commented Mar 28, 2025

⛔️ Test failed

Results
  • ❌ LaunchDaemon Creation or Modification and Immediate Loading (eql)
    • coverage_issue: deprecated_with_rta
    • stack_validation_failed: no_alerts - 0 alerts

@tradebot-elastic
Copy link

tradebot-elastic commented Apr 1, 2025

⛔️ Test failed

Results
  • ❌ LaunchDaemon Creation or Modification and Immediate Loading (eql)
    • coverage_issue: deprecated_with_rta
    • stack_validation_failed: no_alerts - 0 alerts

Copy link
Contributor

@w0rk3r w0rk3r left a comment

Choose a reason for hiding this comment

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

Pending changes to the rule before the real deprecation. ref

@tradebot-elastic
Copy link

tradebot-elastic commented Apr 3, 2025

⛔️ Test failed

Results
  • ❌ LaunchDaemon Creation or Modification and Immediate Loading (eql)
    • coverage_issue: deprecated_with_rta
    • stack_validation_failed: no_alerts - 0 alerts

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

Successfully merging this pull request may close these issues.

5 participants