A Kubernetes user attempted to perform a high number of actions that were denied

Set up the kubernetes integration.

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Goal

Identify when a Kubernetes user attempts to perform a high number of actions that are denied in a short amount of time.

Strategy

This rule identifies responses of the API server where the reason for the error is set to Forbidden, indicating that an authenticated user attempted to perform an action that they are not explicitly authorized to perform.

The rule flags users who receive permission denied errors on several distinct API endpoints in a short amount of time.

Triage and response

  1. Determine if the user: {{@usr.id}} is expected to perform the denied actions. If yes, the alert may be due to a misconfigured application or a service account with insufficient privileges.
  2. Use the Cloud SIEM User Investigation dashboard to review any user actions that may have occurred after the potentially malicious action.

Changelog

  • 7 May 2024 - Updated detection query to include logs from Azure Kubernetes Service.
  • 15 July 2024 - Updated detection query to include logs from Google Kubernetes Engine.
PREVIEWING: antoine.dussault/service-representation-ga-docs-us1