1. Resources
  2. Detection rules
  3. Password Length Requirement Changed in Google Workspace

Password Length Requirement Changed in Google Workspace detection rules

An admin lowers the minimum or maximum password length of a Google Workspace organization, so that shorter passwords are accepted. The change is quiet and makes password guessing easier.

Platform
Google Cloud
Severity
Low
Log source
Google Cloud Audit Logs
Last updated
Rule formats
Sigmaand queries for: SplunkMicrosoft SentinelIBM QRadar
What an attacker needs
An admin account with the Security settings privilege, or a super admin account, in an organization whose users sign in with Google passwords.
Impact
New passwords in the affected unit can be shorter, which makes guessing and spraying more likely to succeed, most of all without 2-Step Verification.
Response
Restore the required minimum and maximum length, check the other password settings and have users with weak passwords change them.
Mitigation
Enforce 2-Step Verification for every user and keep strong password enforcement and the required minimum length on every organizational unit.
API methods
google.admin.AdminService.changePasswordMinLengthgoogle.admin.AdminService.changePasswordMaxLength
Threat groups
FIN13Salt Typhoon

How the attack works

The password settings of Google Workspace and Cloud Identity define what a user may choose as a password. An administrator can enforce strong passwords, set a minimum and a maximum length between 8 and 100 characters, allow or prevent the reuse of old passwords and set an expiration. The settings apply per organizational unit.

An attacker with the Security settings privilege who wants more accounts to fall to guessing, or an administrator who gives in to complaints, lowers the requirement. A lower minimum lets users choose shorter passwords. A lower maximum caps the length of every new password, and a maximum set close to the minimum removes long passphrases altogether. Nothing changes for an account until its password is next set, so the effect arrives slowly and is hard to trace back to the change.

The Admin audit log records CHANGE_PASSWORD_MIN_LENGTH and CHANGE_PASSWORD_MAX_LENGTH, each with the domain and the old and new length. Organizations that share Workspace data with Google Cloud receive them in Cloud Audit Logs at organization level as Admin Activity entries of admin.googleapis.com. Google's event reference and its list of Cloud Audit Logs methods hold no event for the other password settings, strength enforcement, reuse and expiration, so a change to those is not visible in this log source.

What an attacker needs

  • An admin account with the Security settings privilege, or a super admin account.
  • Users who sign in with a Google password. Google states that the password policies do not apply when users authenticate through a third-party identity provider with OIDC.

Impact

New passwords in the affected organizational unit can be shorter than before, which makes password guessing and password spraying against those accounts more likely to succeed. The change gives no access by itself. It matters most for accounts without 2-Step Verification.

Detection rules

Password Minimum or Maximum Length Changed in Google Workspace

Detects a change of the password length requirement of a Google Workspace or Cloud Identity account (Admin audit events CHANGE_PASSWORD_MIN_LENGTH and CHANGE_PASSWORD_MAX_LENGTH, rendered as "Password minimum length for {DOMAIN_NAME} changed from {OLD_VALUE} to {NEW_VALUE}"). Google allows a length between 8 and 100 characters. A lower minimum lets users choose shorter passwords, and a lower maximum caps the length of every new password. The rule fires on a change in EITHER direction, because the method name does not carry it. Read OLD_VALUE and NEW_VALUE in protoPayload.metadata. The admin is in principalEmail. Google documents no audit event for the other password settings (strength enforcement, reuse, expiration), so this rule does not see them. The entries reach Cloud Audit Logs as Admin Activity entries at organization level, which are always written once Google Workspace data sharing with Google Cloud is enabled, and reach the SIEM only when the organization-level logs are routed to it.

LevelLowStatusExperimentalLog sourceGoogle Cloud Audit Logs
title: Password Minimum or Maximum Length Changed in Google Workspace
id: d1526daa-5cf1-4692-8d1d-6a2fcab0fc05
status: experimental
description: >-
  Detects a change of the password length requirement of a Google Workspace
  or Cloud Identity account (Admin audit events CHANGE_PASSWORD_MIN_LENGTH
  and CHANGE_PASSWORD_MAX_LENGTH, rendered as "Password minimum length for
  {DOMAIN_NAME} changed from {OLD_VALUE} to {NEW_VALUE}"). Google allows a
  length between 8 and 100 characters. A lower minimum lets users choose
  shorter passwords, and a lower maximum caps the length of every new
  password. The rule fires on a change in EITHER direction, because the
  method name does not carry it. Read OLD_VALUE and NEW_VALUE in
  protoPayload.metadata. The admin is in principalEmail. Google documents
  no audit event for the other password settings (strength enforcement,
  reuse, expiration), so this rule does not see them. The entries reach
  Cloud Audit Logs as Admin Activity entries at organization level, which
  are always written once Google Workspace data sharing with Google Cloud
  is enabled, and reach the SIEM only when the organization-level logs are
  routed to it.
references:
  - https://docs.cloud.google.com/logging/docs/audit/gsuite-audit-logging
  - https://developers.google.com/workspace/admin/reports/v1/appendix/activity/admin-domain-settings
  - https://knowledge.workspace.google.com/admin/users/enforce-and-monitor-password-requirements-for-users
  - https://attack.mitre.org/techniques/T1556/
author: Forestall
date: 2026-11-18
tags:
  - attack.defense-impairment
  - attack.credential-access
  - attack.t1556
logsource:
  product: gcp
  service: gcp.audit
detection:
  selection:
    protoPayload.serviceName: admin.googleapis.com
    protoPayload.methodName:
      - google.admin.AdminService.changePasswordMinLength
      - google.admin.AdminService.changePasswordMaxLength
  condition: selection
falsepositives:
  - A change that raises the minimum length, for example when a new password policy is introduced.
  - An administrator who aligns the settings of an organizational unit with the rest of the organization. The settings change rarely, so compare every event with the documented policy.
level: low

False positives

  • A change that raises the minimum length, for example when a new password policy is introduced.
  • An administrator who aligns the settings of an organizational unit with the rest of the organization. The settings change rarely, so compare every event with the documented policy.

Triage

  • Read OLD_VALUE and NEW_VALUE in the event parameters in protoPayload.metadata to see whether the length was lowered or raised, and DOMAIN_NAME for the domain.
  • Identify the admin who made the change (principalEmail) and confirm it against a change request.
  • Open the password settings in the Admin console and check the other settings of the same organizational unit, strength enforcement, reuse and expiration, which this log does not show.
  • Check whether the same admin changed other authentication settings around that time, such as 2-Step Verification or account recovery.

Response

Once the attack is confirmed:

  1. Set the minimum and maximum length back to the values your policy requires and check the strength, reuse and expiration settings of the same organizational unit.
  2. Use the Accounts user report of the Admin console, which shows password strength, to find users with weak passwords, and require those who set a password while the requirement was lowered to change it.
  3. If the change was not authorized, secure the admin account that made it. Reset its password, reset its sign-in cookies and review its admin roles.
  4. Review the Login audit log for runs of failed sign-ins against accounts in the affected unit since the change.

Mitigation

  • Enforce 2-Step Verification for every user, so that a weak password alone does not open an account.
  • Enforce strong passwords in the password settings and keep the minimum length at the value your policy requires for every organizational unit.
  • Give the Security settings privilege only to the administrators who own authentication policy.
  • Keep a record of the password settings of each organizational unit and compare the Admin console with it regularly, because only the length settings leave an audit event.
  • Share Workspace data with Google Cloud and route the organization-level audit logs to the SIEM.

Frequently asked questions

Which password policy changes does the Google Workspace audit log record?

Google's reference for Admin audit events lists two, `CHANGE_PASSWORD_MIN_LENGTH` and `CHANGE_PASSWORD_MAX_LENGTH`, and the Cloud Audit Logs method list holds the matching `changePasswordMinLength` and `changePasswordMaxLength`. Neither page lists an event for strength enforcement, password reuse or expiration. A change to those settings has to be found by comparing the Admin console with a record.

Does a lower minimum length weaken the passwords users already have?

No. Existing passwords stay as they are. The requirement applies when a user next chooses a password. Google also states that the strength and length requirements do not apply to passwords an admin resets manually or to passwords set with a hash, for example through the bulk upload tool, the Directory API or a sync tool.

How short can a Google Workspace password be made?

Google states that the minimum and maximum length can be between 8 and 100 characters, and the event reference gives 8 as the lowest minimum the API allows. A minimum of 8 without strong password enforcement is the weakest setting. The event shows the length only, so check the strength setting in the Admin console.

References

We respect your privacy

We use cookies to keep this site secure and working properly. With your permission, we also use optional cookies to understand usage and improve the experience. Cookie Policy

You can change your choice at any time.