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

[FR] SentinelOne PowerQuery Performance #110

Open
2 of 10 tasks
rc-csmith opened this issue Jun 22, 2023 · 0 comments
Open
2 of 10 tasks

[FR] SentinelOne PowerQuery Performance #110

rc-csmith opened this issue Jun 22, 2023 · 0 comments
Labels

Comments

@rc-csmith
Copy link
Contributor

Which category is the feature part of?

  • Definition File
  • Code/Logic Feature
  • Other (please explain)

Which product is the feature part of?

  • All Products
  • Carbon Black Response
  • Carbon Black Threat Hunter
  • Defender for Endpoints
  • SentinelOne
  • Cortex
  • Other

Use Cases

Proposal

When using a definition file, each individual entry is treated as a single query. For example, the following definition file will generate three individual queries that will require at least three separate API calls. Instead, it could all be merged into a single query and reduce the number of API calls.

Example definition file:

{
  "programA":{
    "process_name":["cmd.exe"],
    "cmdline":["/c powershell.exe"],
    "filemod":["powershell_log.exe"]
  }
}

Current queries that get generated

tgt.process.name in ("cmd.exe")
tgt.process.command_line in ("/c powershell.exe")
tgt.file.path in ("powershell_log.exe")

Proposed change

tgt.process.name in ("cmd.exe") or tgt.process.command_line in ("/c powershell.exe") or tgt.file.path in ("powershell_log.exe")

Additional Context

N/A

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

No branches or pull requests

1 participant