TMA-CHROME-2.32

Ensure 'Allow remote debugging' is set to 'Disabled'

HighLevel 1Automatedchrome

Description

This policy setting controls whether users may use remote debugging. This feature allows remote debugging of live content on a Windows 10 or later device from a Windows or macOS computer. The recommended state for this setting is: Disabled. Rationale: Disabling remote debugging enhances security and protects applications from unauthorized access. Some attack tools can exploit this feature to extract information, or to insert malicious code. Audit reads the Group Policy registry value and prints 'compliant', 'unset' (policy not configured, reported as FAIL) or the non-compliant value. Registry value: HKLM\Software\Policies\Google\Chrome:RemoteDebuggingAllowed (REG_DWORD); compliant when it is 0. Remediation writes 0 locally; in a domain set it through the ADMX so Group Policy does not revert it.

How it is checked

Audit method: Windows registry

registry

$v = (Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome' -Name 'RemoteDebuggingAllowed' -ErrorAction SilentlyContinue).'RemoteDebuggingAllowed'; if ($null -eq $v) { 'unset' } elseif (($null -ne $v -and @(0) -contains [int64]$v)) { 'compliant' } else { "non-compliant: $v" }

Expected output: compliant

How it is fixed

Fix method: Shell command

shell

$p = 'Registry::HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome'; if (-not (Test-Path -Path $p)) { New-Item -Path $p -Force | Out-Null }; New-ItemProperty -Path $p -Name 'RemoteDebuggingAllowed' -Value 0 -PropertyType DWord -Force | Out-Null

Properties

Operating systems: Any
Tags: chromebrowsercis-l1
Reference: CIS Google Chrome Benchmark v3.0.0 - 2.32 Ensure 'Allow remote debugging' is set to 'Disabled'

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

shell

tmaegis scan --target chrome