From 9a5933c86132060544bcc08ef4be695d3ce69b06 Mon Sep 17 00:00:00 2001 From: Beth Levin Date: Fri, 10 Jul 2020 19:40:10 -0700 Subject: [PATCH] better explanation --- .../microsoft-defender-atp/tvm-security-recommendation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/tvm-security-recommendation.md b/windows/security/threat-protection/microsoft-defender-atp/tvm-security-recommendation.md index c6b5159b9a..1169a50661 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/tvm-security-recommendation.md +++ b/windows/security/threat-protection/microsoft-defender-atp/tvm-security-recommendation.md @@ -145,9 +145,9 @@ When an exception is created for a recommendation, the recommendation is no long The following list details the justifications behind the exception options: - **Third party control** - A third party product or software already addresses this recommendation - - This justification type will give you point for completing the recommendation, which affects your exposure score and secure score + - Choosing this justification type will lower your exposure score and increase you secure score because your risk is reduced - **Alternate mitigation** - An internal tool already addresses this recommendation - - This justification type will give you point for completing the recommendation, which affects your exposure score and secure score + - Choosing this justification type will lower your exposure score and increase you secure score because your risk is reduced - **Risk accepted** - Poses low risk and/or implementing the recommendation is too expensive - **Planned remediation (grace)** - Already planned but is awaiting execution or authorization