AZDO.1031: Validate SSH Key Expiration.
| ID | AZDO.1031 |
| Severity | High |
| Suite | Mito |
| Product | Azure DevOps |
| Feature | Security policies |
| Security area | Authentication |
| Resource type | Tenant |
| User impact of fixing | Medium |
| Effort to fix | Low |
| Framework controls | nist-800-53-r5:IA-5 Authenticator Management |
| MITRE ATT&CK | T1552.004 |
| Reads from | Azure DevOps |
| Further reading | https://learn.microsoft.com/azure/devops/organizations/accounts/change-application-access-policies?view=azure-devops#ssh-key-policies |
What this checks and how to fix it
Section titled “What this checks and how to fix it”Validation of SSH key expiration date should be enabled.
Rationale: Expired SSH keys should not be valid for authentication towards Azure DevOps.
Remediation action
Section titled “Remediation action”Enable the policy to stop these requests and notifications.
- Sign in to your organization.
- Choose Organization settings.
- Select Policies under Security.
- Switch the Validate SSH key expiration button to ON.
Results: When active, Azure DevOps enforces that keys with expired expiration dates immediately become invalid for authentication.
Related links
Section titled “Related links”Mito check. Author: SebastianClaesson. Open-source licences.
Open-source licences. CIS Benchmark material © Center for Internet Security, Inc.; CISA SCuBA baselines are public domain (CC0).
© 2026 Virtual Petals. Mito is a Virtual Petals service, hosted in Microsoft Azure UAE North.