Kerberos Enforce AES

๐Ÿ”’ Secure Bits ๐Ÿ’ก
๐—ช๐—ฎ๐—ป๐˜ ๐˜๐—ผ ๐—ฑ๐—ถ๐˜€๐—ฎ๐—ฏ๐—น๐—ฒ ๐—ฅ๐—–๐Ÿฐ ๐—ฎ๐—ป๐—ฑ ๐—ฒ๐—ป๐—ณ๐—ผ๐—ฟ๐—ฐ๐—ฒ ๐—”๐—˜๐—ฆ ๐—ถ๐—ป ๐—ž๐—ฒ๐—ฟ๐—ฏ๐—ฒ๐—ฟ๐—ผ๐˜€?

You should โ€” butย ๐—ฑ๐—ผ๐—ปโ€™๐˜ ๐—ฑ๐—ผ ๐—ถ๐˜ ๐—ฏ๐—น๐—ถ๐—ป๐—ฑ๐—น๐˜†.

Enforcing strong authentication (like AES-only Kerberos) is an important part of ๐—บ๐—ผ๐—ฑ๐—ฒ๐—ฟ๐—ป ๐—ฆ๐—ฒ๐—ฐ๐˜‚๐—ฟ๐—ถ๐˜๐˜† ๐—•๐—ฎ๐˜€๐—ฒ๐—น๐—ถ๐—ป๐—ฒ๐˜€ย โ€” just like LDAP signing or NTLM hardening. But in older environments,ย RC4 is still widely used, and flipping the switch ๐—ฐ๐—ฎ๐—ป ๐—ฏ๐—ฟ๐—ฒ๐—ฎ๐—ธ ๐˜๐—ต๐—ถ๐—ป๐—ด๐˜€ ๐—ณ๐—ฎ๐˜€๐˜.

๐Ÿ›‘ย Donโ€™t deploy security baselines without visibility first.

๐—›๐—ฒ๐—ฟ๐—ฒโ€™๐˜€ ๐—ต๐—ผ๐˜„ ๐˜๐—ผ ๐˜€๐—ฎ๐—ณ๐—ฒ๐—น๐˜† ๐˜๐—ฟ๐—ฎ๐—ฐ๐—ธ ๐—ž๐—ฒ๐—ฟ๐—ฏ๐—ฒ๐—ฟ๐—ผ๐˜€ ๐—ฒ๐—ป๐—ฐ๐—ฟ๐˜†๐—ฝ๐˜๐—ถ๐—ผ๐—ป ๐˜‚๐˜€๐—ฎ๐—ด๐—ฒ:
๐Ÿ“ ๐—˜๐—ป๐—ฎ๐—ฏ๐—น๐—ฒ ๐˜๐—ต๐—ฒ ๐—ณ๐—ผ๐—น๐—น๐—ผ๐˜„๐—ถ๐—ป๐—ด ๐—ฎ๐˜‚๐—ฑ๐—ถ๐˜ ๐—ฝ๐—ผ๐—น๐—ถ๐—ฐ๐—ถ๐—ฒ๐˜€:
โ†’ Advanced Audit Policy ConfigurationAccount Logon
โœ” Audit Kerberos Authentication Service
โœ” Audit Kerberos Service Ticket Operations

๐—ง๐—ต๐—ถ๐˜€ ๐—ฒ๐—ป๐—ฎ๐—ฏ๐—น๐—ฒ๐˜€ ๐—˜๐˜ƒ๐—ฒ๐—ป๐˜ ๐—œ๐——๐˜€ ๐Ÿฐ๐Ÿณ๐Ÿฒ๐Ÿด ๐—ฎ๐—ป๐—ฑ ๐Ÿฐ๐Ÿณ๐Ÿฒ๐Ÿต, ๐˜„๐—ต๐—ถ๐—ฐ๐—ต ๐—น๐—ผ๐—ด:
๐Ÿ”ธ Ticket Encryption Type
๐Ÿ”ธ Pre-Authentication Encryption Type
๐—”๐—ป๐—ฑ ๐˜€๐—ถ๐—ป๐—ฐ๐—ฒ ๐—๐—ฎ๐—ป ๐Ÿฎ๐Ÿฌ๐Ÿฎ๐Ÿฑ โ€” ๐—ฒ๐˜…๐˜๐—ฟ๐—ฎ ๐—ณ๐—ถ๐—ฒ๐—น๐—ฑ๐˜€ ๐—น๐—ถ๐—ธ๐—ฒ:
๐Ÿ”น Advertised Etypes
๐Ÿ”น Supported Encryption Types
๐Ÿ”น Available Keys

Once you seeย which accounts still rely on ๐—ฅ๐—–๐Ÿฐ, you can fix them โ€” andย safely enforce AESย across the domain.

โœ… Audit first. Enforce later. Break nothing.

๐Ÿ“Œ Iโ€™ll continue this series onย real-world challengesย when applying security baselines โ€” and how to do it without breaking legacy systems.