From 1962ae96d4bab7508b4d69046a9d03dcfd794632 Mon Sep 17 00:00:00 2001 From: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> Date: Mon, 15 May 2023 11:25:05 -0500 Subject: [PATCH] Fix typo on correlation page (#4073) * Fix typo on correlation page Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> * Update correlation-config.md Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> --------- Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> --- _security-analytics/sec-analytics-config/correlation-config.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_security-analytics/sec-analytics-config/correlation-config.md b/_security-analytics/sec-analytics-config/correlation-config.md index da2a24db..243ce44b 100644 --- a/_security-analytics/sec-analytics-config/correlation-config.md +++ b/_security-analytics/sec-analytics-config/correlation-config.md @@ -10,7 +10,7 @@ nav_order: 16 The correlation engine is an experimental feature released in OpenSearch 2.7. Therefore, we do not recommend using the feature in a production environment at this time. For updates on the progress of the correlation engine, see [Security Analytics Correlation Engine](https://github.com/opensearch-project/security-analytics/issues/369) on GitHub. To share ideas and provide feedback, join the [Security Analytics forum](https://forum.opensearch.org/c/plugins/security-analytics/73). {: .warning } -Correlation rules allow you to define threat scenarios involving multiple systems in an infrastructure by matching the signatures of threat events occuring in different log types. Once a rule contains at least two different log sources and the preferred fields and field values that define an intended threat secenario, the correlation engine can query the indexes specified in the correlation rule and identify any correlations between the findings. +Correlation rules allow you to define threat scenarios involving multiple systems in an infrastructure by matching the signatures of threat events occurring in different log types. Once a rule contains at least two different log sources and the preferred fields and field values that define an intended threat scenario, the correlation engine can query the indexes specified in the correlation rule and identify any correlations between the findings. ## Configuring rules