How do I install the Cis Docker V170 3.2 skill?

Run npx skillmds@latest add cyberstrikeus/cis-docker-v170-3-2 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.2 skill do?

Ensure that docker.service file permissions are appropriately set It is listed under DevOps & Infra on SkillMD.

Is Cis Docker V170 3.2 safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: CAUTION, 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.2?

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.2 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.2?

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

Cis Docker V170 3.2 by cyberstrikeus

Name: Cis Docker V170 3.2
Author: cyberstrikeus

File contents

CIS Docker Benchmark v1.7.0 - Control 3.2

Description

You should verify that the docker.service file permissions are either set to 644 or to a more restrictive value.

Rationale

The docker.service file contains sensitive parameters that may alter the behavior of the Docker daemon. It should therefore not be writable by any other user other than root in order to ensure that it can not be modified by less privileged users.

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 permissions are set to `644` or a more restrictive value:

For example:

stat -c %a /usr/lib/systemd/system/docker.service

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 exists, execute the command below including the correct file path to set the file permissions to `644`:

For example:

chmod 644 /usr/lib/systemd/system/docker.service

Default Value

This file may not be present on the system. In that case, this recommendation is not applicable. By default, if the file is present, the file permissions are correctly set to 644.

References

https://docs.docker.com/articles/systemd/

CIS Controls

Controls Version	Control	IG 1	IG 2	IG 3
v8	3.3 Configure Data Access Control ListsConfigure data access control lists based on a user's need to know. Apply data access control lists, also known as access permissions, to local and remote file systems, databases, and applications.	●	●	●
v7	14.6 Protect Information through Access Control ListsProtect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities.	●	●	●

Profile Applicability

Level 1 - Docker - Linux

Assessment Status

Automated

---name: cis-docker-v170-3-2description: Ensure that docker.service file permissions are appropriately set---# CIS Docker Benchmark v1.7.0 - Control 3.2## DescriptionYou should verify that the `docker.service` file permissions are either set to `644` or to a more restrictive value.## RationaleThe `docker.service` file contains sensitive parameters that may alter the behavior of the Docker daemon. It should therefore not be writable by any other user other than `root` in order to ensure that it can not be modified by less privileged users.## 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 permissions are set to `644` or a more restrictive value:For example:```bashstat -c %a /usr/lib/systemd/system/docker.service```## 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 exists, execute the command below including the correct file path to set the file permissions to `644`:For example:```bashchmod 644 /usr/lib/systemd/system/docker.service```## Default ValueThis file may not be present on the system. In that case, this recommendation is not applicable. By default, if the file is present, the file permissions are correctly set to `644`.## References1. https://docs.docker.com/articles/systemd/## CIS Controls| Controls Version | Control | IG 1 | IG 2 | IG 3 || ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | ---- | ---- || v8 | 3.3 Configure Data Access Control Lists<br>Configure data access control lists based on a user's need to know. Apply data access control lists, also known as access permissions, to local and remote file systems, databases, and applications. | ● | ● | ● || v7 | 14.6 Protect Information through Access Control Lists<br>Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities. | ● | ● | ● |## Profile Applicability- Level 1 - Docker - Linux## Assessment StatusAutomated

Frequently asked questions

Cis Docker V170 3.2

File contents

CIS Docker Benchmark v1.7.0 - Control 3.2

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 permissions are set to 644 or a more restrictive value:

Remediation

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 to set the file permissions to 644:

Default Value

References

CIS Controls

Profile Applicability

Assessment Status

Related skills

Frequently asked questions

How do I install the Cis Docker V170 3.2 skill?

What does the Cis Docker V170 3.2 skill do?

Is Cis Docker V170 3.2 safe to use?

Which AI agents work with Cis Docker V170 3.2?

Is Cis Docker V170 3.2 free to use?

Who published Cis Docker V170 3.2?

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 permissions are set to `644` or a more restrictive value:

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 to set the file permissions to `644`: