From Google Chrome Current Windows STIG
Part of DTBC-0062 - Developer Tools
Associated with: CCI-000381
: If this policy is set to ”DeveloperToolsDisallowedForForceInstalledExtensions” (value 0, which is the default for enterprise users), the Developer Tools and the JavaScript console can be accessed in general, but they cannot be accessed in the context of extensions installed by enterprise policy. If this policy is set to ”DeveloperToolsAllowed” (value 1, which is the default for unmanaged users), the Developer Tools and the JavaScript console can be accessed and used in all contexts, including the context of extensions installed by enterprise policy. If this policy is set to ”DeveloperToolsDisallowed” (value 2), the Developer Tools cannot be accessed and web-site elements cannot be inspected anymore. Any keyboard shortcuts and any menu or context menu entries to open the Developer Tools or the JavaScript Console will be disabled.
Universal method: 1. In the omnibox (address bar) type chrome://policy 2. If "DeveloperToolsAvailability" is not displayed under the "Policy Name" column or it 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 "DeveloperToolsAvailability" value name does not exist or its value data is not set to "2", this is a finding.
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: 2
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer