MT.1089: Devices with critical credentials should be protected by Credential Guard.
| ID | MT.1089 |
| Severity | Medium |
| Suite | Mito |
| Product | Defender |
| Feature | Exposure Management |
| Security area | Devices and endpoints |
| Resource type | Device |
| User impact of fixing | Low |
| Effort to fix | Medium |
| MITRE ATT&CK | T1003.001 |
| Reads from | Microsoft Graph |
What this checks and how to fix it
Section titled “What this checks and how to fix it”Devices shown in the output are devices where Credential Guard is not enabled or misconfigured, but contains credentials of critical accounts. When critical credentials are stored on devices without Credential Guard enabled, it is easy for adversaries to steal those credentials when the device is compromised. This is because, without Credential Guard enabled, Kerberos, NTLM, and Credential Manager secrets are stored in the Local Security Authority (LSA) process called lsass.exe, which can be dumped with various tools like MimiKatz. With Credential Guard enabled, these secrets are protected and isolated using Virtualization-based security (VBS).
How to fix
Section titled “How to fix”Investigate the related devices and the steps that need to be taken in order to enable Credential Guard. This varies depending on operating system, hardware, and device. More information on how Credential Guard works and how it can be configured can be found in this documentation page.
Mito check. Author: RobbeVandenDaele; contributors: SamErde. 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.
