Browsers STIGs
CAT III 2
Any vulnerability, the existence of which degrades measures to protect against loss of confidentiality, availability or integrity.
-
Extensions that are approved for use must be allowlisted.
Maps to SC-18(4) via CCI-001170Check
Universal method: 1. In the omnibox (address bar) type chrome://policy 2. If ExtensionInstallAllowlist is not displayed under the Policy Name column or it is not set to oiigbmnaadbkfbmpbfijlflahbdbdgdf or a list of administrator approved extension IDs, then this is a finding. Windows method: 1. Start regedit 2. Navigate to the key HKLM\Software\Policies\Google\Chrome\ExtensionInstallAllowlist 3. If the ExtensionInstallAllowlist key is not set to 1 and oiigbmnaadbkfbmpbfijlflahbdbdgdf or a list of administrator-approved extension IDs, then this is a finding.
Fix
Windows group policy: 1. Open the group policy editor tool with gpedit.msc 2. Navigate to Policy Path: Computer Configuration\Administrative Templates\Google\Google Chrome\Extensions\ Policy Name: Configure extension installation allowlist Policy State: Enabled Policy Value: oiigbmnaadbkfbmpbfijlflahbdbdgdf Note: oiigbmnaadbkfbmpbfijlflahbdbdgdfis the extension ID for scriptno (a commonly used Chrome extension), other extension IDs may vary.
-
Chrome development tools must be disabled.
Maps to SI-11 via CCI-001312Check
Universal method: 1. In the omnibox (address bar) type chrome://policy 2. If the policy "DeveloperToolsAvailability" is not shown or is not set to "2", this is a finding. Windows method: 1. Start regedit 2. Navigate to HKLM\Software\Policies\Google\Chrome\ 3. If the key "DeveloperToolsAvailability" does not exist or is not set to "2", this is a finding.
Fix
Windows group policy: 1. Open the "group policy editor" tool with gpedit.msc 2. Navigate to Policy Path: Computer Configuration\Administrative Templates\Google\Google Chrome Policy Name: Control where Developer Tools can be used Policy State: Enabled Policy Value: Disallow usage of the Developer Tools