Make a defined set of changes to systems and system components, at a defined frequency, so that the attack surface stops presenting a fixed and predictable target. Attack planning assumes consistency in the points where an adversary can enter, act or extract data, so varying the timing and circumstances of routine actions removes that assumption. Shortening credential validity at irregular intervals, performing routine activities at different times of day, alternating between technologies or suppliers, and rotating the roles and responsibilities of personnel all inject uncertainty. The intent is to force miscalculation, delay adversary action, and make attackers more observable when they do move. The organization decides which changes qualify and how often each system and component receives them.
NIST SP 800-172 3.13.2e is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-172 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 24 of 35 NIST SP 800-172 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 5 were rejected on the NIST SP 800-53 Rev 5 pair alone.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.