- Affected assets
- sso-portal
- Accounts affected
- 1
- Stated confidence
- 94% stated
A confidence the scenario's author stated when writing it — not a measured rate. Nothing here has yet been scored against a human's later verdict; calibration arrives when outcomes exist (R96), and until then no figure is invented for it.
Causal chain
- 203[.]0[.]113[.]22->sso-portal:443
412 sign-in failures from one new ASN in 6 minutes
evidence: SEC-0001-a
technique: T1110.004 Credential Stuffing · Credential Access
- j.rivera
failures → one success on the same account
evidence: SEC-0001-b, SEC-0001-c
technique: T1078.004 Cloud Accounts · Defense Evasion
- sso-portal
session issued to an unrecognised device
evidence: SEC-0001-d
technique: T1078 Valid Accounts · Persistence
Diagnosis
Credential stuffing against the SSO portal succeeded on one account: 412 failures from a single new ASN, then one success.
evidence: SEC-0001-a, SEC-0001-b, SEC-0001-c
Also considered
- The user is travelling and signed in from a new location.3% stated
contradicted by: SEC-0001-c, SEC-0001-a
Shown because a system that hides its own doubt is harder to trust than one that reports it.
Remediation plan
- 01revoke_sessionrisk 25expects session invalidrollback: reissue_session
- 02require_mfa_reauthrisk 10expects session re-verifiedrollback: clear_mfa_requirement
Risk shown is the action’s base score. Effective risk rises with blast radius, production environment, and low confidence — it never falls, and the dashboard never computes it here.
Timeline
- agent:sentinelcorrelated412 failures and one success on one account within 11 minutes
- agent:analystdiagnosedimpossible travel rules out the travelling-user reading
- dharmaawaiting approvalrevoke_session scores 25 → approval tier
