Open
Description
Context
In many security programs, validation efforts are limited to assets where an agent is deployed. Until now, OpenBAS followed this model — matching detection expectations with the endpoint’s agent ID. However, this approach does not reflect how real-world attacks unfold.
Use case
When I'm running a CVE scan or exploit from an OpenBAS agent to a remote host without OpenBAS, the expectation results will not raised alerts.
Current Workaround
Have OpenBAS on every endpoints but need to adapted the collected to match the target hostname and not the source one.
Proposed Solution
One idea could be to add a payload argument type with a specific key like "remote_ip", and then specify that we can create a KQL query in Sentinel to retrieve alerts where the IP matches the "remote_ip" value.
To discuss.