القائمة
Ensure containers are restricted from acquiring new privileges
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-docker-v170-2-14يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | cis-docker-v170-2.14 |
| description | Ensure containers are restricted from acquiring new privileges |
| category | cis-docker |
| version | 1.7.0 |
| author | cyberstrike-official |
| tags | ["cis","docker","daemon","configuration","no-new-privileges","privilege-escalation"] |
| cis_id | 2.14 |
| cis_benchmark | CIS Docker Benchmark v1.7.0 |
| tech_stack |
| ["docker"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
By default you should restrict containers from acquiring additional privileges via suid or sgid.
A process can set the no_new_priv bit in the kernel and this persists across forks, clones and execve. The no_new_priv bit ensures that the process and its child processes do not gain any additional privileges via suid or sgid bits. This reduces the security risks associated with many dangerous operations because there is a much reduced ability to subvert privileged binaries.
Setting this at the daemon level ensures that by default all new containers are restricted from acquiring new privileges.
no_new_priv prevents LSMs such as SELinux from escalating the privileges of individual containers.
To confirm this setting, you should review the dockerd start-up options and a check of any settings in /etc/docker/daemon.json should also be carried out.
To review the dockerd startup options, the following command can be used:
ps -ef | grep dockerd
You should ensure that the --no-new-privileges parameter is present and that it is not set to false.
The contents of /etc/docker/daemon.json should also be reviewed.
You should run the Docker daemon as below:
dockerd --no-new-privileges
By default, containers are not restricted from acquiring new privileges.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 6.1 Establish an Access Granting Process Establish and follow a process, preferably automated, for granting access to enterprise assets upon new hire, rights grant, or role change of a user. | ● | ● | ● |
| v7 | 4 Controlled Use of Administrative Privileges Controlled Use of Administrative Privileges |
Level 1 - Docker - Linux (Manual)