Accounts & identity
Dormant account abuse
Dormant account abuse
Dormant-account abuse exploits an old active identity, often retaining forgotten permissions.
Fiche de sensibilisationPrête à diffuser à vos équipes ou clients
MIGHT YOU BE AFFECTED?
Turn knowledge into action.
How does this work?
Dormant-account abuse exploits an old active identity, often retaining forgotten permissions. Investigation requires examining identity events, sessions and effective permissions; a single alert alone does not establish impact.
REAL-WORLD EXAMPLE
« An old contractor account that was inactive for a year suddenly downloads documents. »
Typical sequence
- 1Identify an old identity with remaining permissions.
- 2Confirm that it is active and rarely monitored.
- 3Acquire its credentials or a recoverable session.
- 4Use lingering historical permissions.
- 5Access available data or services discreetly.
Warning signs
- Unusual activity in security logs.
- Unknown devices, processes or network origins.
- Unexplained setting or permission changes.
- Correlated security alerts.
- Unauthorised access or data modifications.
How to protect yourself
- Disable dormant accounts and alert on unexpected reactivation.
- Limit privileges and protect accounts.
- Patch software and review configurations.
- Use context-appropriate strong authentication.
- Monitor and investigate suspicious logs.
- Train staff to recognise deceptive requests.
- Keep protected and tested backups.
If you think you are affected
Suspend suspicious access, preserve events and identify misused sessions or permissions. Disable ownerless accounts; review access regularly; alert on reactivation. Revoke affected sessions and review account changes.
Last updated: 8 October 2026