From 9a362f6cb9de8d7f3f6f5267905bb620da239b87 Mon Sep 17 00:00:00 2001 From: Michael Cretzman <58786311+michaelcretzman@users.noreply.github.com> Date: Mon, 28 Oct 2024 15:30:23 -0700 Subject: [PATCH] Update content/en/security/application_security/threats/security_signals.md Co-authored-by: Heston Hoffman --- .../security/application_security/threats/security_signals.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/security/application_security/threats/security_signals.md b/content/en/security/application_security/threats/security_signals.md index 506b062e9729c..eaac1c8dae070 100644 --- a/content/en/security/application_security/threats/security_signals.md +++ b/content/en/security/application_security/threats/security_signals.md @@ -28,7 +28,7 @@ The Signals Explorer displays signals using the following columns: There are five severity states: **Critical**, **High**, **Medium**, **Low**, and **Info**. -- **Critical:** A service is compromised. For example, a SQL injection. An immediate response is required. +- **Critical:** A service is compromised. For example, an SQL injection. An immediate response is required. - **High:** A service is vulnerable, but it is unclear whether the service is compromised at this time. An immediate response is required. - **Medium:** A service is running the stack and infrastructure that allows for an attack, but the service is not vulnerable at this time. If you get a medium, it does not require an immediate response and you can evaluate how you want to triage the issue. - **Low** and **Info**: Typically, these are signals used when experimenting or demonstrating an issue, like Log4Shell scanning.