Threat Explorer
Valid Accounts
T1078
Description
Adversaries obtain and abuse credentials of existing accounts.
Recommendations
- MFA
- Privileged access management
- Anomaly detection
Security Reasoning
Composed from the intelligence model — every conclusion is traceable.
Valid Accounts matters because it directly touches identity & directory and cloud infrastructure. The adversary's goal is to obtain stored credentials, which typically leads to privilege escalation and unauthorised access. Left unchecked, it becomes a stepping stone in a broader operation rather than an isolated event.
Possible consequences
Affected assets
Credentials and directory objects are the primary blast radius.
IaaS/SaaS control planes and secrets are targeted for lateral pivot.
Security controls
Detection opportunities
- Centralised log collection & monitoring → alerts on this behaviour
Governance context
Preventive controls stack meaningfully, but residual risk survives via drift and coverage gaps.
Reasoning chain
- Valid AccountsObtain stored credentialsEvery technique exists to advance an adversary objective.
- Obtain stored credentialsIdentity & directoryCredentials and directory objects are the primary blast radius.
- Obtain stored credentialsCloud infrastructureIaaS/SaaS control planes and secrets are targeted for lateral pivot.
- Identity & directoryPrivilege escalationOnce the goal is achieved, privilege escalation typically follows.
- Identity & directoryUnauthorised accessOnce the goal is achieved, unauthorised access typically follows.
- Identity & directoryLateral movementOnce the goal is achieved, lateral movement typically follows.
- Privilege escalationPhishing-resistant MFAPrevent credential replay when a password is phished or dumped.
- Privilege escalationPrivileged access managementIsolate, broker and audit administrator credentials.
- Privilege escalationCentralised log collection & monitoringPreserve tamper-resistant evidence and enable correlation.
- Phishing-resistant MFAConditional access policy requiring FIDO2 / passkeysDemonstrates that the control is designed and operating.
- Phishing-resistant MFASign-in report showing MFA claim on privileged sessionsDemonstrates that the control is designed and operating.
- Phishing-resistant MFAMFA coverage assessment across identitiesDemonstrates that the control is designed and operating.
- Phishing-resistant MFAISO 27001 · A.5.15 – A.5.18 Access control & identityISO 27001 fires here because the behaviour of "Valid Accounts" is the exact scenario A.5.15 – A.5.18 Access control & identity exists to prevent — Directly addresses provisioning, authentication and privileged access, which are the governance mirror of credential-based attacks.
- Phishing-resistant MFANIST CSF · PR.AA — Identity Management & AuthenticationNIST CSF fires here because the behaviour of "Valid Accounts" is the exact scenario PR.AA — Identity Management & Authentication exists to prevent — PR.AA is the CSF outcome category that fails when adversaries reuse or steal identities.
- Phishing-resistant MFANIS2 · Art. 21(2)(d) — Access control policiesNIS2 fires here because the behaviour of "Valid Accounts" is the exact scenario Art. 21(2)(d) — Access control policies exists to prevent — NIS2 requires essential entities to enforce access-control measures whose absence enables this behaviour.
- Compensating controlsResidual risk: mediumPreventive controls stack meaningfully, but residual risk survives via drift and coverage gaps.
AI reasoning
Ask the AI to explain why, how, what changes, and what remains exposed — grounded in this reasoning chain.