From 0d1e167915781804901776a08fa411608ab748ce Mon Sep 17 00:00:00 2001
From: mdueltgen <148897369+mdueltgen@users.noreply.github.com>
Date: Wed, 24 Jul 2024 16:22:31 -0400
Subject: [PATCH] updated rationale statement for 3.1

---
 ...nd Docs Minimum Viable Secure Configuration Baseline v0.2.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/baselines/Google Drive and Docs Minimum Viable Secure Configuration Baseline v0.2.md b/baselines/Google Drive and Docs Minimum Viable Secure Configuration Baseline v0.2.md
index 1a6af460..27b361e0 100644
--- a/baselines/Google Drive and Docs Minimum Viable Secure Configuration Baseline v0.2.md	
+++ b/baselines/Google Drive and Docs Minimum Viable Secure Configuration Baseline v0.2.md	
@@ -262,7 +262,7 @@ This section covers whether a security update issued by Google will be applied t
 #### GWS.DRIVEDOCS.3.1v0.2
 Agencies SHALL enable the security update for Drive files.
 
-- _Rationale:_ By not enabling the resource key security update it creates the potential for an unauthorized access to files. Enabling this security update mitigates the risk by ensuring access is controlled properly.
+- _Rationale:_ By not enabling the update to the resource key security update a user could potentially gain unauthorized access to files. Enabling this security update decreases risk of unauthorized access and data spillage by controlling access to files in Google Drive.
 - _Last modified:_ July 10, 2023
 
 - MITRE ATT&CK TTP Mapping