Skip to content

m365_defender: use windows-specific command line analyser - #9812

Merged
efd6 merged 1 commit into
elastic:mainfrom
efd6:s4675-m365_defender
May 16, 2024
Merged

m365_defender: use windows-specific command line analyser#9812
efd6 merged 1 commit into
elastic:mainfrom
efd6:s4675-m365_defender

Conversation

@efd6

@efd6 efd6 commented May 8, 2024

Copy link
Copy Markdown
Contributor

Proposed commit message

The previous analyser was not quote aware and so resulted in mis-constructed argument lists, resulting in missed detection rule.

The inputs to the integration are likely to be entirely from windows hosts, so use the windows-specific analyser from the crowdstrike fdr data stream.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

@efd6 efd6 added enhancement New feature or request Integration:m365_defender Microsoft Defender XDR Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] labels May 8, 2024
@efd6 efd6 self-assigned this May 8, 2024
@efd6
efd6 force-pushed the s4675-m365_defender branch from 9ca3d3e to 39b15e0 Compare May 8, 2024 00:10
@elasticmachine

Copy link
Copy Markdown

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@efd6
efd6 marked this pull request as ready for review May 8, 2024 00:38
@efd6
efd6 requested a review from a team as a code owner May 8, 2024 00:38
@elasticmachine

Copy link
Copy Markdown

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

The previous analyser was not quote aware and so resulted in
mis-constructed argument lists, resulting in missed detection rule.

The inputs to the integration are likely to be entirely from windows
hosts, so use the windows-specific analyser from the crowdstrike fdr
data stream.
@efd6
efd6 force-pushed the s4675-m365_defender branch from 39b15e0 to aa66aa5 Compare May 16, 2024 10:01
@elasticmachine

Copy link
Copy Markdown

💚 Build Succeeded

History

  • 💚 Build #11237 succeeded 39b15e0e2b56b1f595d6107a8a046a18f24ba8fd

cc @efd6

@chrisberkhout chrisberkhout left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Good.

The weirdest case is msoia.exe" scan upload turning into msoia.exe scan upload. The double quote starts a double quoted block even though that block isn't closed. So it's not a literal and it isn't in the result.

@efd6

efd6 commented May 16, 2024

Copy link
Copy Markdown
Contributor Author

I'm wondering if that isn't a corrupted hand-crafted test input.

@efd6
efd6 merged commit 7ffbffc into elastic:main May 16, 2024
@chrisberkhout

chrisberkhout commented May 16, 2024

Copy link
Copy Markdown
Contributor

Correction to my earlier commit: the result is a single argument, not 3.

I'm wondering if that isn't a corrupted hand-crafted test input.

Could be.

@elasticmachine

Copy link
Copy Markdown

Package m365_defender - 2.9.0 containing this change is available at https://epr.elastic.co/search?package=m365_defender

@efd6
efd6 deleted the s4675-m365_defender branch February 5, 2025 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request Integration:m365_defender Microsoft Defender XDR Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

3 participants