Ensure an Account Locking Policy Is Configured

보통레벨 1수동 검토tdsql

설명

An account locking policy automatically locks accounts after consecutive login failures, preventing brute-force attacks. Assessed manually here: the benchmark check is environment-specific and cannot be evaluated reliably by a single command.

점검 방법

감사 방식: 수동 검토

이 권장 사항은 자동으로 점검할 수 없습니다. --include-manual 옵션을 전달하면 스캔 결과에 이 지침과 함께 표시됩니다.

Run SELECT User, Host, User_attributes FROM mysql.user; and confirm business accounts carry FAILED_LOGIN_ATTEMPTS (e.g. 5) and PASSWORD_LOCK_TIME (e.g. 1 day) in User_attributes. On the SQLEngine run SHOW VARIABLES LIKE 'tdsql_user_lock_by_ip'; (should be ON). Accounts without a locking policy are a finding.

조치 방법

조치 방식: 가이드 또는 인프라 패치

Set a locking policy when creating or modifying a user: ALTER USER 'username'@'host' FAILED_LOGIN_ATTEMPTS 5 PASSWORD_LOCK_TIME 1; Enable SQLEngine's per-IP locking: SET GLOBAL tdsql_user_lock_by_ip = ON; SQLEngine's tdsql_user_lock_by_ip feature tracks failed login counts and locks per source IP, providing finer control than MySQL's native per- account locking.

속성

운영 체제: 모두
태그: tdsqlauthentication
참고 자료: CIS Tencent TDSQL 10.3.22 Benchmark v1.0.0 - 7.4 Ensure an Account Locking Policy Is Configured