Skip to content

Commit 225d2ad

Browse files
Update _posts/2025-03-05-OpenSearch-as-a-SIEM-Solution.md
Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: DattellConsulting <[email protected]>
1 parent 2a531e5 commit 225d2ad

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/2025-03-05-OpenSearch-as-a-SIEM-Solution.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ When a detector's rule condition is met by incoming log data, the system generat
2929

3030
OpenSearch gives users the ability to define alerting conditions. When such conditions are met, OpenSearch sends an alert to the designated channel (email, Slack, PagerDuty, etc.). Alerts can be tailored to trigger on single-rule matches or only when multiple rules are detected.
3131

32-
### <u>Correlation of Events.</u>
32+
### <u>Correlation of events</u>
3333
A powerful feature of OpenSearch Security Analytics is its ability to correlate multiple signals across different log sources. The built-in correlation engine can link findings from different types of logs to identify complex attack patterns spanning multiple systems.[1](https://opensearch.org/docs/latest/security-analytics/#:~:text=Security%20Analytics%20is%20a%20security,responding%20effectively%20to%20potential%20threats)
3434

3535
For example, a sequence of events like a VPN login from a new location, followed by a privileged action in a server log, and an abnormal outbound network connection could be correlated into one incident.

0 commit comments

Comments
 (0)