Skip to content
Back to skills

Cis K8s V1111 1.2.20

ASecurity

Ensure that the --request-timeout argument is set as appropriate (Manual)

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

Works with

  • api

Security analysis

A100/100

Scanned September 3, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Cis K8s V1111 1.2.20?

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

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

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.20
description: "Ensure that the --request-timeout argument is set as appropriate (Manual)"
category: cis-k8s
version: "1.11.1"
author: cyberstrike-official
tags: [cis, kubernetes, control-plane, api-server, request-timeout, availability]
cis_id: "1.2.20"
cis_benchmark: "CIS Kubernetes Benchmark v1.11.1"
tech_stack: [kubernetes]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---

# 1.2.20 Ensure that the --request-timeout argument is set as appropriate (Manual)

## Profile Applicability

- Level 1 - Master Node

## Description

Set global request timeout for API server requests as appropriate.

## Rationale

Setting global request timeout allows extending the API server request timeout limit to a duration appropriate to the user's connection speed. By default, it is set to 60 seconds which might be problematic on slower connections making cluster resources inaccessible once the data volume for requests exceeds what can be transmitted in 60 seconds. But, setting this timeout limit to be too large can exhaust the API server resources making it prone to Denial-of-Service attack. Hence, it is recommended to set this limit as appropriate and change the default limit of 60 seconds only if needed.

## Impact

None

## Audit

Run the following command on the Control Plane node:

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

Verify that the `--request-timeout` argument is either not set or set to an appropriate value.

## Remediation

Edit the API server pod specification file `/etc/kubernetes/manifests/kube-apiserver.yaml` and set the below parameter as appropriate and if needed. For example,

```bash
--request-timeout=300s
```

## Default Value

By default, `--request-timeout` is set to 60 seconds.

## References

1. https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/
2. https://github.com/kubernetes/kubernetes/pull/51415

## CIS Controls

| Controls Version | Control                                                  | IG 1 | IG 2 | IG 3 |
| ---------------- | -------------------------------------------------------- | ---- | ---- | ---- |
| v8               | 4 Secure Configuration of Enterprise Assets and Software |      |      |      |
| v7               | 5.1 Establish Secure Configurations                      | x    | x    | 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.