|
1 | 1 | Windows Server 2016 CIS |
2 | 2 | ========= |
| 3 | + |
| 4 | + |
| 5 | +Configure a Windows Server 2016 system to be [CIS](https://www.cisecurity.org/cis-benchmarks/) v1.2.0 compliant. There are some intrusive tasks that have a toggle in defaults main.yml to disable to automated fix |
| 6 | + |
| 7 | +Caution(s) |
| 8 | +------- |
| 9 | +This role **will make changes to the system** that could break things. This is not an auditing tool but rather a remediation tool to be used after an audit has been conducted. |
| 10 | + |
| 11 | +This role was developed against a clean install of the Operating System. If you are implementing to an existing system please review this role for any site specific changes that are needed. |
| 12 | + |
| 13 | +To use release version please point to main branch |
| 14 | +Based on [CIS Windows Server 2016 Benchmark ](https://community.cisecurity.org/collab/public/index.php). |
| 15 | + |
| 16 | +Documentation |
| 17 | +------------- |
| 18 | +[Getting Started](https://www.lockdownenterprise.com/docs/getting-started-with-lockdown)<br> |
| 19 | +[Customizing Roles](https://www.lockdownenterprise.com/docs/customizing-lockdown-enterprise)<br> |
| 20 | +[Per-Host Configuration](https://www.lockdownenterprise.com/docs/per-host-lockdown-enterprise-configuration)<br> |
| 21 | +[Getting the Most Out of the Role](https://www.lockdownenterprise.com/docs/get-the-most-out-of-lockdown-enterprise)<br> |
| 22 | +[Wiki](https://github.com/ansible-lockdown/Windows-2016-CIS/wiki)<br> |
| 23 | +[Repo GitHub Page](https://ansible-lockdown.github.io/Windows-2016-CIS/)<br> |
3 | 24 |
|
4 | | -Configure a Windows Server 2016 system to be CIS compliant. |
5 | 25 |
|
6 | | -This role is based on CIS Microsoft Windows Server 2016 RTM: [Version 1.2.0 Rel 1607 released on May 27, 2020] (https://learn.cisecurity.org/l/799323/2020-07-10/zx1v). |
7 | 26 |
|
8 | 27 | Requirements |
9 | 28 | ------------ |
10 | 29 |
|
11 | | -Windows Server 2016 - Other versions are not supported. |
| 30 | +**General:** |
| 31 | +- Basic knowledge of Ansible, below are some links to the Ansible documentation to help get started if you are unfamiliar with Ansible |
| 32 | + - [Main Ansible documentation page](https://docs.ansible.com) |
| 33 | + - [Ansible Getting Started](https://docs.ansible.com/ansible/latest/user_guide/intro_getting_started.html) |
| 34 | + - [Tower User Guide](https://docs.ansible.com/ansible-tower/latest/html/userguide/index.html) |
| 35 | + - [Ansible Community Info](https://docs.ansible.com/ansible/latest/community/index.html) |
| 36 | +- Functioning Ansible and/or Tower Installed, configured, and running. This includes all of the base Ansible/Tower configurations, needed packages installed, and infrastructure setup. |
| 37 | +- 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 consiquences in a live production system. Also familiarize yourself with the variables in the defaults/main.yml file or the [Main Variables Wiki Page](https://github.com/ansible-lockdown/Windows-2016-CIS/wiki/Main-Variables). |
| 38 | + |
| 39 | +**Technical Dependencies:** |
| 40 | +- Running Ansible/Tower setup (this role is tested against Ansible version 2.9.1 and newer) |
| 41 | +- Python3 Ansible run environment |
| 42 | + |
| 43 | +Role Variables |
| 44 | +-------------- |
| 45 | + |
| 46 | +This role is designed 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. These variables can be found [here](https://github.com/ansible-lockdown/Windows-2016-CIS/wiki/Main-Variables) in the Main Variables Wiki page. All variables are listed there along with descriptions. |
| 47 | + |
| 48 | +Branches |
| 49 | +-------- |
| 50 | + |
| 51 | +- **devel** - This is the default branch and the working development branch. Community pull requests will pull into this branch |
| 52 | +- **main** - This is the release branch |
| 53 | +- **reports** - This is a protected branch for our scoring reports, no code should ever go here |
| 54 | +- **gh-pages** - This is the github pages branch |
| 55 | +- **all other branches** - Individual community member branches |
| 56 | + |
| 57 | +Community Contribution |
| 58 | +---------------------- |
| 59 | + |
| 60 | +We encourage you (the community) to contribute to this role. Please read the rules below. |
| 61 | + |
| 62 | +- Your work is done in your own individual branch. Make sure to Signed-off and GPG sign all commits you intend to merge. |
| 63 | +- All community Pull Requests are pulled into the devel branch |
| 64 | +- Pull Requests into devel will confirm your commits have a GPG signature, Signed-off, and a functional test before being approved |
| 65 | +- 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 |
0 commit comments