Fix 18.10.89.2.2 and 18.10.89.1.3

Signed-off-by: Stephen Williams <[email protected]>

defaults/main.yml

@@ -476,17 +476,16 @@ win19cis_rule_18_10_87_2: true
 # Setting win_skip_for_test: true -- will skip the controls here even if they are set to true.
 # win19cis_rule_18_10_89_1_1
 # win19cis_rule_18_10_89_1_2
+# win19cis_rule_18_10_89_1_3
 # win19cis_rule_18_10_89_2_1
 # win19cis_rule_18_10_89_2_2
 # win19cis_rule_18_10_89_2_3
 win19cis_rule_18_10_89_1_1: true
 win19cis_rule_18_10_89_1_2: true
+win19cis_rule_18_10_89_1_3: true
 win19cis_rule_18_10_89_2_1: true
-win19cis_rule_18_10_89_2_2: true
+win19cis_rule_18_10_89_2_2: true # This control will have to be set to Enabled (1) to allow for continued remote management via Ansible following machine restart. We have it set to skip for testing.
 win19cis_rule_18_10_89_2_3: true
-# This control will have to be set to Enabled (1) to allow for continued remote management via Ansible following
-# machine restart. The CIS standard calls for 0 but doing so will break all remote connections to the system.
-win19cis_rule_18_10_89_1_3: true
 win19cis_rule_18_10_89_2_4: true
 win19cis_rule_18_10_90_1: true
 # WINRM CONTROLS END #