V2R11 changes
Google Chrome Current Windows STIG V2R11 (2025-07-02) replaced V2R10 (2024-10-24): 6 checks added, 2 removed, 1 updated. It has 46 checks, against 42 in V2R10.
V2R11 checklistV2R10 checklist Compare V2R10 and V2R11 in STIG Compare
- 6 added
- 2 removed
- 1 updated
Updated fields: Check text 1Fix text 1Discussion 1
Added in V2R11 (6)
- V-275780CAT IICreate Themes with AI must be disabled.
- V-275781CAT IIDevTools Generative AI features must be disabled.
- V-275782CAT IIGenAI local foundational model must be disabled.
- V-275783CAT IIHelp Me Write must be disabled.
- V-275784CAT IIAI-powered History Search must be disabled.
- V-275785CAT IITab Compare Settings must be disabled.
Removed since V2R10 (2)
Updated in V2R11 (1)
V-221588CAT IIDownload restrictions must be configured.Check text, Fix text, Discussion
Check text
If the system is on the SIPRNet, this requirement is NANot Applicable.
Universal method:
1. In the omnibox (address bar) type "chrome:// policy".
2. If "DownloadRestrictions" is not displayed under the "Policy Name" column or it is not set to "10" or "2" under the "Policy Value" column, then this is a finding.
Windows method:
1. Start "regedit".
2. Navigate to "HKLM1Software1Policies1Google1Chrome1".
3. If the "DownloadRestrictions" value name does not exist or its value data is not set to "10" or "2", then this is a finding.
Fix text
If the system is on the SIPRNet, this requirement is NANot Applicable.
Windows group policy:
1. Open the group policy editor tool with gpedit.msc.
2. Navigate to Policy Path: Computer Configuration1Administrative Templates1Google1Google Chrome1
Policy Name: Allow download restrictions
Policy State: 1, 2, or 24
Policy Value: N/A
Discussion
ConfigureSetting the typepolicy ofmeans downloads that Google Chrome will completely block, without letting users overridecannot thebypass download security decisiondecisions. IfThere youare setmany this policy, Google Chrome will prevent certain types of downloads,download andwarnings willwithin notChrome, letwhich userroughly bypassbreak thedown securityinto warnings.these Whencategories:
- theMalicious, "Blockas dangerousflagged downloads"by optionthe isSafe chosen,Browsing allserver.
- downloadsUncommon areor allowedunwanted, exceptas forflagged thoseby thatthe carrySafe SafeBrowsingBrowsing warningsserver.
- WhenA the "Block potentially dangerous downloads"file optiontype is chosen(e.g., all SWF downloads allowed,and exceptmany forEXE those that carry SafeBrowsing warnings of potentially dangerous downloads).
Setting When the "Blockpolicy allblocks downloads"different optionsubsets isof chosenthese, alldepending downloadson areits blocked. Whenvalue:
0 this= policy is not set, (or the "No special restrictions". optionDefault.
1 is= chosen),Block themalicious downloads willand godangerous throughfile the usual security restrictions based on SafeBrowsing analysis resultstypes.
Note2 that= theseBlock restrictionsmalicious apply to downloads triggered from web page content, asuncommon wellor asunwanted the 'download link...' context menu option. These restrictions do not apply to the save / download of the currently displayed pagedownloads, norand doesdangerous itfile apply to saving as PDF from the printing optionstypes. See https://developers.google.com/safe-browsing for more info on SafeBrowsing.
03 = No special restrictions
1 = Block dangerousall downloads.
24 = Block potentiallymalicious dangerous downloads
3. = Block all downloadsRecommended.
How these changes are found
Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V2R11 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.