8.3.10.1 SP password rotation or posture
Additional requirement for service providers: customer passwords used as sole factor are changed at least every 90 days, or access is dynamically analyzed.
5
artefacts
2
held by a system
1
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration enforcing 90 day rotation for customers · Cloud console / configuration management
- Audit log of customer password rotations · Identity provider / directory
periodic reviewEvidence produced at each review
- Posture analysis platform evidence if used · Document repository
governing documentDocuments that govern the control
- Coverage list per customer tenant · Document repository
- Customer notifications of upcoming changes · Document repository
First move
Start with the 2 of 5 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Rotation not enforced per customer
- Posture analysis missing
- Inconsistent across tenants
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet8.3.10 Service provider customer password guidance · 8.3.11 Hardware token and other factor protection