Skip to content
Back to skills

Cis K8s V1111 1.2.14

ASecurity

Ensure that the admission control plugin NodeRestriction is set (Automated)

  • 3,518 stars
  • 0 votes
  • 0 copies
  • 6 views
  • Added September 3, 2026
securitygobashnodekubernetesapidocumentation

Works with

  • api

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill cis-k8s-v1111-1.2.14 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cis K8s V1111 1.2.14?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cis K8s V1111 1.2.14
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-cis-k8s-v1111-1-2-14/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-k8s-v1111-1-2-14)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cis-k8s-v1111-1.2.14
description: "Ensure that the admission control plugin NodeRestriction is set (Automated)"
category: cis-k8s
version: "1.11.1"
author: cyberstrike-official
tags: [cis, kubernetes, control-plane, api-server, admission-control, node-restriction]
cis_id: "1.2.14"
cis_benchmark: "CIS Kubernetes Benchmark v1.11.1"
tech_stack: [kubernetes]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---

# 1.2.14 Ensure that the admission control plugin NodeRestriction is set (Automated)

## Profile Applicability

- Level 2 - Master Node

## Description

Limit the `Node` and `Pod` objects that a kubelet could modify.

## Rationale

Using the `NodeRestriction` plug-in ensures that the kubelet is restricted to the `Node` and `Pod` objects that it could modify as defined. Such kubelets will only be allowed to modify their own `Node` API object, and only modify `Pod` API objects that are bound to their node.

## Impact

None

## Audit

Run the following command on the Control Plane node:

```bash
ps -ef | grep kube-apiserver
```

Verify that the `--enable-admission-plugins` argument is set to a value that includes `NodeRestriction`.

## Remediation

Follow the Kubernetes documentation and configure `NodeRestriction` plug-in on kubelets. Then, edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` on the master node and set the `--enable-admission-plugins` parameter to a value that includes `NodeRestriction`.

```bash
--enable-admission-plugins=...,NodeRestriction,...
```

## Default Value

By default, `NodeRestriction` is not set.

## References

1. https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/
2. https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#noderestriction
3. https://kubernetes.io/docs/reference/access-authn-authz/node/

## CIS Controls

| Controls Version | Control                                              | IG 1 | IG 2 | IG 3 |
| ---------------- | ---------------------------------------------------- | ---- | ---- | ---- |
| v8               | 13.10 Perform Application Layer Filtering            |      |      | x    |
| v7               | 12.9 Deploy Application Layer Filtering Proxy Server |      |      | x    |

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in security →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.