Windows 10 Enterprise CIS

Configure a Windows 10 Enterprise system to be CIS compliant

Based on Microsoft Windows 10 Enterprise Benchmark v2.0.0 - 03-07-2023

---

---

Looking for support?

Lockdown Enterprise

Ansible Support

Community

On our Discord Server to ask questions, discuss features, or just chat with other Ansible-Lockdown users

---

Caution(s)

This role will make changes to the system which may have unintended consequences. This is not an auditing tool but rather a remediation tool to be used after an audit has been conducted.

Check Mode is not supported! The role will complete in check mode without errors, but it is not supported and should be used with caution.

This role was developed against a clean install of the Windows 10 Enterprise 22H2 Operating System. If you are implementing to an existing system please review this role for any site specific changes that are needed.

To use release version please point to main branch and relevant release for the cis benchmark you wish to work with.

---

Matching a security Level for CIS

It is possible to only run level 1 or level 2 controls for CIS as well as a variety of other tags that are available for this role. This is managed using tags:

• level1-corporate-enterprise-environment
• level2-high-security-sensitive-data-environment
• level1-next-generation-windows-security
• level1-bitlocker-next-generation-windows-security
• level2-next-generation-windows-security
• level2-bitlocker-next-generation-windows-security
• next-generation-windows-security
• level1-bitlocker
• level2-bitlocker
• bitlocker

The controls found in defaults/main also need to reflect those control numbers due to aligning every control to the audit component.

Coming from a previous release

CIS releases always contain changes, so it is highly recommended to review the new references and available variables. This has changed significantly since the ansible-lockdown initial release. This is now compatible with python3 if it is found to be the default interpreter. This does come with prerequisites that configure the system accordingly.

Further details can be seen in the Changelog

Auditing (new)

Currently this release does not have a auditing tool that is up to date.

Documentation

• Read The Docs
• Getting Started
• Customizing Roles
• Per-Host Configuration
• Getting the Most Out of the Role

Requirements

General:

• Basic knowledge of Ansible, below are some links to the Ansible documentation to help get started if you are unfamiliar with Ansible

  • Main Ansible documentation page
  • Ansible Getting Started
  • Tower User Guide
  • Ansible Community Info

• Functioning Ansible and/or Tower Installed, configured, and running. This includes all of the base Ansible/Tower configurations, needed packages installed, and infrastructure setup.

• Please read through the tasks in this role to gain an understanding of what each control is doing. Some of the tasks are disruptive and can have unintended consequences in a live production system. Also familiarize yourself with the variables in the defaults/main.yml file.

Technical Dependencies:

• Windows 10 Enterprise 22H2 - Other versions are not supported
• Running Ansible/Tower setup (this role is tested against Ansible version 2.10.1 and newer)
• Python3 Ansible run environment
• passlib (or python2-passlib, if using python2)
• python-lxml
• python-xmltodict
• python-jmespath
• pywinrm

Package 'python-xmltodict' is required if you enable the OpenSCAP tool installation and run a report. Packages python(2)-passlib and python-jmespath are required for tasks with custom filters or modules. These are all required on the controller host that executes Ansible.

Role Variables

This role is designed so that the end user should not have to edit the tasks themselves. All customizing should be done via the defaults/main.yml file or with extra vars within the project, job, workflow, etc.

Tags

There are many tags available for added control precision. Each control has it's own set of tags noting what level, if its automated or manual check, if it's a patch or audit, and the rule number.

Below is an example of the tag section from a control within this role. Using this example if you set your run to skip all controls with the tag rpc, this task will be skipped. The opposite can also happen where you run only controls tagged with smb.

  tags:
      - level1-corporate-enterprise-environment
      - rule_18.4.2
      - automated
      - patch
      - rpc

Tags for entire sections can be run using the tags that are in the main.yml files for each section. In this particular case this is the following example and how it breaks down for sections.

Section 18 - administrative-templates-computer
Section 18.10 - windows-components
Section 18.10.3 - app-package-deployment

- name: "SECTION | 18.10.3 | App Package Deployment"
  ansible.builtin.import_tasks:
      file: cis_18.10.3.x.yml
  tags:
      - administrative-templates-computer
      - windows-components
      - app-package-deployment

Community Contribution

We encourage you (the community) to contribute to this role. Please read the rules below.

• Your work is done in your own individual branch. Make sure to Signed-off and GPG sign all commits you intend to merge.
• All community Pull Requests are pulled into the devel branch
• Pull Requests into devel will confirm your commits have a GPG signature, Signed-off, and a functional test before being approved
• Once your changes are merged and a more detailed review is complete, an authorized member will merge your changes into the main branch for a new release

Pipeline Testing

uses:

• ansible-core 2.12
• ansible collections - pulls in the latest version based on requirements file
• runs the audit using the devel branch
• This is an automated test that occurs on pull requests into devel