Stay organized with collections
Save and categorize content based on your preferences.
This document describes a threat finding type in Security Command Center. Threat findings are generated by
threat detectors when they detect
a potential threat in your cloud resources. For a full list of available threat findings, see Threat findings index.
Overview
Someone created an RBAC binding that references one of the following users or groups:
system:anonymous
system:authenticated
system:unauthenticated
These users and groups are effectively anonymous and should be avoided when
creating role bindings or cluster role bindings to any RBAC roles. Review the
binding to ensure that it is necessary. If the binding isn't necessary, remove
it. For more details, see the log message for this finding.
How to respond
The following response plan might be appropriate for this finding, but might also impact operations.
Carefully evaluate the information you gather in your investigation to determine the best way to
resolve findings.
To respond to this finding, do the following:
Review any bindings created that granted permissions to the
system:anonymous user, system:unauthenticated group, or
system:authenticated group.
Determine whether there are other signs of malicious activity by the
principal in the audit logs in Cloud Logging.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-08 UTC."],[],[],null,["| Premium and Enterprise [service tiers](/security-command-center/docs/service-tiers)\n\nThis document describes a threat finding type in Security Command Center. Threat findings are generated by\n[threat detectors](/security-command-center/docs/concepts-security-sources#threats) when they detect\na potential threat in your cloud resources. For a full list of available threat findings, see [Threat findings index](/security-command-center/docs/threat-findings-index).\n\nOverview\n\nSomeone created an RBAC binding that references one of the following users or groups:\n\n- `system:anonymous`\n- `system:authenticated`\n- `system:unauthenticated`\n\nThese users and groups are effectively anonymous and should be avoided when\ncreating role bindings or cluster role bindings to any RBAC roles. Review the\nbinding to ensure that it is necessary. If the binding isn't necessary, remove\nit. For more details, see the log message for this finding.\n\nHow to respond\n\n\nThe following response plan might be appropriate for this finding, but might also impact operations.\nCarefully evaluate the information you gather in your investigation to determine the best way to\nresolve findings.\n\nTo respond to this finding, do the following:\n\n1. Review any bindings created that granted permissions to the `system:anonymous` user, `system:unauthenticated group`, or `system:authenticated` group.\n2. Determine whether there are other signs of malicious activity by the principal in the audit logs in Cloud Logging.\n\nIf there are signs of malicious activity, review [guidance for investigating and removing the bindings](/kubernetes-engine/docs/best-practices/rbac#default-roles-groups) that allowed this access.\n\nWhat's next\n\n- Learn [how to work with threat\n findings in Security Command Center](/security-command-center/docs/how-to-investigate-threats).\n- Refer to the [Threat findings index](/security-command-center/docs/threat-findings-index).\n- Learn how to [review a\n finding](/security-command-center/docs/how-to-investigate-threats#reviewing_findings) through the Google Cloud console.\n- Learn about the [services that\n generate threat findings](/security-command-center/docs/concepts-security-sources#threats)."]]
