MT.1060: Drift folders should match their baseline.
| ID | MT.1060 |
| Severity | Medium |
| Suite | Mito |
| Product | Microsoft 365 |
| Feature | Configuration drift |
| Security area | Infrastructure hardening |
| Resource type | Tenant |
| User impact of fixing | Low |
| Effort to fix | Low |
| Reads from | None |
What this checks and how to fix it
Section titled “What this checks and how to fix it”Checks JSON files that you supply for drift from a baseline.
Create a drift folder with one subfolder per drift check. Each subfolder holds a baseline.json (the expected configuration), a current.json (the actual configuration) and an optional settings.json whose ExcludeProperties lists properties to skip.
Four results are created per folder, with the folder name made safe for a test ID:
MT.1060.<folder>.1: the baseline file exists and is valid JSON.MT.1060.<folder>.2: the current file exists and is valid JSON.MT.1060.<folder>.3: the current file has no properties missing from the baseline.MT.1060.<folder>.4: every value in the current file matches the baseline.
In earlier versions of the engine these results were named MT1060.<folder>.<n>. The MT1060, MT1060.<n>, MT1060.<folder> and MT1060.<folder>.<n> tags are kept.
Remediation action
Section titled “Remediation action”Update the configuration, or the baseline, so that the two files match.
Mito check. Author: svrooij. 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.
