How do I install the Cis Docker 7.6 skill?

Run npx skillmds@latest add cyberstrikeus/cis-docker-7-6 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 7.6 skill do?

Ensure that the swarm manager auto-lock key is rotated periodically It is listed under DevOps & Infra on SkillMD.

Is Cis Docker 7.6 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 7.6?

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 7.6 free to use?

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

Who published Cis Docker 7.6?

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

Cis Docker 7.6 by cyberstrikeus — Agent Skill

Name: Cis Docker 7.6
Author: cyberstrikeus

File contents

7.6 Ensure that the swarm manager auto-lock key is rotated periodically (Manual)

Profile Applicability

Level 1 - Docker Swarm

Description

You should rotate the swarm manager auto-lock key periodically.

Rationale

The swarm manager auto-lock key is not automatically rotated. Good security practice is to rotate keys.

Impact

None

Audit Procedure

Currently, there is no mechanism to find out when the key was last rotated on a swarm manager node. You should check with the system administrator to see if there is a key rotation process, and how often the key is rotated.

Remediation

You should run the command below to rotate the keys.

docker swarm unlock-key --rotate

Additionally, to facilitate auditing of this recommendation, you should maintain key rotation records and ensure that you establish a pre-defined frequency for key rotation.

Default Value

By default, keys are not rotated automatically.

References

https://docs.docker.com/engine/reference/commandline/swarm_unlock-key/

CIS Controls

Controls Version	Control	IG 1	IG 2	IG 3
v8	5.2 Use Unique PasswordsUse unique passwords for all enterprise assets. Best practice implementation includes, at a minimum, an 8-character password for accounts using MFA and a 14-character password for accounts not using MFA.	●	●	●
v7	4.4 Use Unique PasswordsWhere multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system.		●	●

---name: cis-docker-7-6description: Ensure that the swarm manager auto-lock key is rotated periodically---# 7.6 Ensure that the swarm manager auto-lock key is rotated periodically (Manual)## Profile Applicability- Level 1 - Docker Swarm## DescriptionYou should rotate the swarm manager auto-lock key periodically.## RationaleThe swarm manager auto-lock key is not automatically rotated. Good security practice is to rotate keys.## ImpactNone## Audit ProcedureCurrently, there is no mechanism to find out when the key was last rotated on a swarm manager node. You should check with the system administrator to see if there is a key rotation process, and how often the key is rotated.## RemediationYou should run the command below to rotate the keys.```docker swarm unlock-key --rotate```Additionally, to facilitate auditing of this recommendation, you should maintain key rotation records and ensure that you establish a pre-defined frequency for key rotation.## Default ValueBy default, keys are not rotated automatically.## References1. https://docs.docker.com/engine/reference/commandline/swarm_unlock-key/## CIS Controls| Controls Version | Control | IG 1 | IG 2 | IG 3 || ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | ---- | ---- || v8 | 5.2 Use Unique Passwords<br>Use unique passwords for all enterprise assets. Best practice implementation includes, at a minimum, an 8-character password for accounts using MFA and a 14-character password for accounts not using MFA. | ● | ● | ● || v7 | 4.4 Use Unique Passwords<br>Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. | | ● | ● |

Frequently asked questions

Cis Docker 7.6