Account Use Policies
Configure features related to account use like login attempt lockouts, specific login times, etc.
Techniques Addressed by Mitigation
| Domain | ID | Name | Use | |
|---|---|---|---|---|
| Enterprise | T1110 | Brute Force |
Set account lockout policies after a certain number of failed login attempts to prevent passwords from being guessed. Too strict a policy may create a denial of service condition and render environments un-usable, with all accounts used in the brute force being locked-out. Use conditional access policies to block logins from non-compliant devices or from outside defined organization IP ranges.[1] Consider blocking risky authentication requests, such as those originating from anonymizing services/proxies.[2] |
|
| .001 | Password Guessing |
Set account lockout policies after a certain number of failed login attempts to prevent passwords from being guessed. Too strict a policy may create a denial of service condition and render environments un-usable, with all accounts used in the brute force being locked-out. Use conditional access policies to block logins from non-compliant devices or from outside defined organization IP ranges.[1] Consider blocking risky authentication requests, such as those originating from anonymizing services/proxies.[2] |
||
| .003 | Password Spraying |
Set account lockout policies after a certain number of failed login attempts to prevent passwords from being guessed. Too strict a policy may create a denial of service condition and render environments un-usable, with all accounts used in the brute force being locked-out. Use conditional access policies to block logins from non-compliant devices or from outside defined organization IP ranges.[1] Consider blocking risky authentication requests, such as those originating from anonymizing services/proxies.[2] |
||
| .004 | Credential Stuffing |
Set account lockout policies after a certain number of failed login attempts to prevent passwords from being guessed. Too strict a policy may create a denial of service condition and render environments un-usable, with all accounts used in the brute force being locked-out. Use conditional access policies to block logins from non-compliant devices or from outside defined organization IP ranges.[1] Consider blocking risky authentication requests, such as those originating from anonymizing services/proxies.[2] |
||
| Enterprise | T1621 | Multi-Factor Authentication Request Generation |
Enable account restrictions to prevent login attempts, and the subsequent 2FA/MFA service requests, from being initiated from suspicious locations or when the source of the login attempts do not match the location of the 2FA/MFA smart device. Use conditional access policies to block logins from non-compliant devices or from outside defined organization IP ranges.[1] |
|
| Enterprise | T1648 | Serverless Execution |
Where possible, consider restricting access to and use of serverless functions. For examples, conditional access policies can be applied to users attempting to create workflows in Microsoft Power Automate. Google Apps Scripts that use OAuth can be limited by restricting access to high-risk OAuth scopes.[3][4] |
|
| Enterprise | T1550 | Use Alternate Authentication Material |
Where possible, consider restricting the use of authentication material outside of expected contexts. |
|
| .001 | Application Access Token |
Where possible, consider restricting the use of access tokens outside of expected contexts. For example, in AWS environments, consider using data perimeters to prevent credential use outside of an expected network.[5] |
||
| Enterprise | T1078 | Valid Accounts |
Use conditional access policies to block logins from non-compliant devices or from outside defined organization IP ranges.[1] |
|
| .004 | Cloud Accounts |
Use conditional access policies to block logins from non-compliant devices or from outside defined organization IP ranges.[1] |
||
References
- Microsoft. (2022, December 14). Conditional Access templates. Retrieved February 21, 2023.
- Moussa Diallo and Brett Winterford. (2024, April 26). How to Block Anonymizing Services using Okta. Retrieved May 28, 2024.
- Microsoft Developer Support. (2020, May 9). Control Access to Power Apps and Power Automate with Azure AD Conditional Access Policies. Retrieved July 1, 2024.