How do I install the Cis Docker V170 3.1 skill?

Run npx skillmds@latest add cyberstrikeus/cis-docker-v170-3-1 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Cis Docker V170 3.1 skill do?

Ensure that the docker.service file ownership is set to root:root It is listed under DevOps & Infra on SkillMD.

Is Cis Docker V170 3.1 safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cis Docker V170 3.1?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cis Docker V170 3.1 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cis Docker V170 3.1?

cyberstrikeus (@cyberstrikeus) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cis Docker V170 3.1 by cyberstrikeus

Name: Cis Docker V170 3.1
Author: cyberstrikeus

File contents

CIS Docker Benchmark v1.7.0 - Control 3.1

Description

You should verify that the docker.service file ownership and group ownership are correctly set to root.

Rationale

The docker.service file contains sensitive parameters that may alter the behavior of the Docker daemon. It should therefore be individually and group owned by the root user in order to ensure that it is not modified or corrupted by a less privileged user.

Impact

None.

Audit Procedure

Step 1: Find out the file location

systemctl show -p FragmentPath docker.service

Step 2: If the file does not exist, this recommendation is not applicable. If the file exists, execute the command below including the correct file path in order to verify that the file is owned and group owned by `root`:

For example:

stat -c %U:%G /usr/lib/systemd/system/docker.service | grep -v root:root

The command above should not return anything.

Remediation

Step 1: Find out the file location

systemctl show -p FragmentPath docker.service

Step 2: If the file does not exist, this recommendation is not applicable. If the file does exist, you should execute the command below, including the correct file path, in order to set the ownership and group ownership for the file to `root`:

For example:

chown root:root /usr/lib/systemd/system/docker.service

Default Value

This file may not be present on the system and if it is not, this recommendation is not applicable. By default, if the file is present, the correct permissions are for the ownership and group ownership to be set to "root".

References

https://docs.docker.com/config/daemon/systemd/

CIS Controls

Controls Version	Control	IG 1	IG 2	IG 3
v8	5.4 Restrict Administrator Privileges to Dedicated Administrator AccountsRestrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user's primary, non-privileged account.	●	●	●
v7	4 Controlled Use of Administrative PrivilegesControlled Use of Administrative Privileges

Profile Applicability

Level 1 - Docker - Linux

Assessment Status

Automated

---name: cis-docker-v170-3-1description: Ensure that the docker.service file ownership is set to root:root---# CIS Docker Benchmark v1.7.0 - Control 3.1## DescriptionYou should verify that the `docker.service` file ownership and group ownership are correctly set to `root`.## RationaleThe `docker.service` file contains sensitive parameters that may alter the behavior of the Docker daemon. It should therefore be individually and group owned by the `root` user in order to ensure that it is not modified or corrupted by a less privileged user.## ImpactNone.## Audit Procedure### Step 1: Find out the file location```bashsystemctl show -p FragmentPath docker.service```### Step 2: If the file does not exist, this recommendation is not applicable. If the file exists, execute the command below including the correct file path in order to verify that the file is owned and group owned by `root`:For example:```bashstat -c %U:%G /usr/lib/systemd/system/docker.service | grep -v root:root```The command above should not return anything.## Remediation### Step 1: Find out the file location```bashsystemctl show -p FragmentPath docker.service```### Step 2: If the file does not exist, this recommendation is not applicable. If the file does exist, you should execute the command below, including the correct file path, in order to set the ownership and group ownership for the file to `root`:For example:```bashchown root:root /usr/lib/systemd/system/docker.service```## Default ValueThis file may not be present on the system and if it is not, this recommendation is not applicable. By default, if the file is present, the correct permissions are for the ownership and group ownership to be set to "root".## References1. https://docs.docker.com/config/daemon/systemd/## CIS Controls| Controls Version | Control | IG 1 | IG 2 | IG 3 || ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | ---- | ---- || v8 | 5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts<br>Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user's primary, non-privileged account. | ● | ● | ● || v7 | 4 Controlled Use of Administrative Privileges<br>Controlled Use of Administrative Privileges | | | |## Profile Applicability- Level 1 - Docker - Linux## Assessment StatusAutomated

Frequently asked questions

Cis Docker V170 3.1

File contents

CIS Docker Benchmark v1.7.0 - Control 3.1

Description

Rationale

Impact

Audit Procedure

Step 1: Find out the file location

Step 2: If the file does not exist, this recommendation is not applicable. If the file exists, execute the command below including the correct file path in order to verify that the file is owned and group owned by root:

Remediation

Step 1: Find out the file location

Step 2: If the file does not exist, this recommendation is not applicable. If the file does exist, you should execute the command below, including the correct file path, in order to set the ownership and group ownership for the file to root:

Default Value

References

CIS Controls

Profile Applicability

Assessment Status

Related skills

Frequently asked questions

How do I install the Cis Docker V170 3.1 skill?

What does the Cis Docker V170 3.1 skill do?

Is Cis Docker V170 3.1 safe to use?

Which AI agents work with Cis Docker V170 3.1?

Is Cis Docker V170 3.1 free to use?

Who published Cis Docker V170 3.1?

Step 2: If the file does not exist, this recommendation is not applicable. If the file exists, execute the command below including the correct file path in order to verify that the file is owned and group owned by `root`:

Step 2: If the file does not exist, this recommendation is not applicable. If the file does exist, you should execute the command below, including the correct file path, in order to set the ownership and group ownership for the file to `root`: