22.06.2016 Views

CIS Microsoft Windows 10 Enterprise RTM (Release 1507) Benchmark

CIS_Microsoft_Windows_10_Enterprise_RTM_Release_1507_Benchmark_v1.0.0

CIS_Microsoft_Windows_10_Enterprise_RTM_Release_1507_Benchmark_v1.0.0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

2.3.15 System objects<br />

This section contains recommendations related to system objects.<br />

2.3.15.1 (L1) Set 'System objects: Require case insensitivity for non-<br />

<strong>Windows</strong> subsystems' to 'Enabled' (Scored)<br />

Profile Applicability:<br />

Level 1<br />

Level 1 + BitLocker<br />

Description:<br />

This policy setting determines whether case insensitivity is enforced for all subsystems.<br />

The <strong>Microsoft</strong> Win32' subsystem is case insensitive. However, the kernel supports case<br />

sensitivity for other subsystems, such as the Portable Operating System Interface for UNIX<br />

(POSIX). Because <strong>Windows</strong> is case insensitive (but the POSIX subsystem will support case<br />

sensitivity), failure to enforce this policy setting makes it possible for a user of the POSIX<br />

subsystem to create a file with the same name as another file by using mixed case to label<br />

it. Such a situation can block access to these files by another user who uses typical Win32<br />

tools, because only one of the files will be available.<br />

The recommended state for this setting is: Enabled.<br />

Rationale:<br />

Because <strong>Windows</strong> is case-insensitive but the POSIX subsystem will support case sensitivity,<br />

failure to enable this policy setting would make it possible for a user of that subsystem to<br />

create a file with the same name as another file but with a different mix of upper and lower<br />

case letters. Such a situation could potentially confuse users when they try to access such<br />

files from normal Win32 tools because only one of the files will be available.<br />

Audit:<br />

Navigate to the UI Path articulated in the Remediation section and confirm it is set as<br />

prescribed. This group policy setting is backed by the following registry location:<br />

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session<br />

Manager\Kernel:ObCaseInsensitive<br />

239 | P a g e

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!