What changed in Google Chrome Current Windows Security Technical Implementation Guide V2R5V2R5 changes

Google Chrome Current Windows Security Technical Implementation Guide V2R5 (2021-11-19) replaced V2R4 (2021-07-13): 1 rule added, 1 updated. It has 39 rules, against 38 in V2R4.

V2R5 benchmarkV2R4 benchmark Compare V2R4 and V2R5 in SCAP Compare

  • 1 added
  • 0 removed
  • 1 updated

Updated fields: Check text 1

Added in V2R5 (1)

  • V-234701CAT IChrome must be configured to allow only TLS.

Updated in V2R5 (1)

V-245538CAT IIUse of the QUIC protocol must be disabled.Check text

Check text

AND - Use of the QUIC protocol is disabled registry_test (check: all, existence: at_least_one_exists) object registry_object: hive equals "HKEY_LOCAL_MACHINE"; name equals "QuicAllowed"; key equals "SOFTWARE\\Policies\\Google\\Chrome" state registry_state: type equals "reg_dword"; value equals "0" Universal method: 1. In the omnibox (address bar), type chrome://policy. 2. If QuicAllowed is not displayed under the Policy Name column or it is not set to 1False under the Policy Value column, this is a finding. Windows method: 1. Start regedit. 2. Navigate to HKLM\Software\Policies\Google\Chrome\. 3. If the QuicAllowed value name does not exist or its value data is not set to 0, this is a finding.

V-245538 in V2R5

How these changes are found

Rules are matched across the two benchmark releases by their STIG V-number. A rule counts as updated when its rule id changed and its title, severity, discussion, fix text or OVAL check logic changed — the same comparison SCAP Compare makes.

Comparing other releases, or this one against an older release? Pick any two in SCAP Compare.