Guide-linked quiz · Medium Level

Account Takeover Detection Quiz

Detect account takeover using event sequences and layered controls while balancing fraud prevention, false locks, secure recovery and privacy.

Related guide pathsAccount Takeover Detection
Question 1 of 8

Which event constitutes an account takeover?

Preview every question8 questions

Answers and explanations appear as you take the quiz.

  1. Which event constitutes an account takeover?
    • A legitimate owner changes their own password through verified recovery
    • A merchant reverses a disputed payment
    • Unauthorized access to an existing account followed by actions as its user
    • An attacker guesses a password but never gains account access
  2. What does credential stuffing involve?
    • Guessing many possible passwords for one account
    • Trying previously exposed credentials on another service
    • Trying one common password across many accounts
    • Resetting a password through the account’s verified recovery flow
  3. Why can a sequence of account events be more informative than one login signal?
    • One device change always proves fraud
    • Event ordering is never useful
    • Transactions cannot be connected to logins
    • Several linked actions can form a suspicious progression
  4. Which response is an example of step-up security?
    • Requesting an additional verification for a high-risk action
    • Allowing every transaction without checks
    • Revoking every customer session after each login
    • Permanently deleting the account
  5. Why must account-recovery flows be designed carefully?
    • Recovery has no connection to account security
    • A model can always identify the true owner
    • Attackers may abuse recovery while legitimate users need accessible access restoration
    • Account recovery should be impossible
  6. Which metric helps reveal harm from overly strict detection?
    • Only model training loss
    • Legitimate account lockouts and recovery time
    • The share of sessions using different device types
    • Password length among signed-in users
  7. What should customer-support teams never request through an untrusted channel?
    • A case reference number
    • A preferred contact time
    • A non-sensitive device model
    • A password or one-time authentication code
  8. Why avoid exposing detection thresholds and rules?
    • Attackers could tune behavior to evade the controls
    • The rules are public by default
    • It prevents legitimate users from signing in
    • It changes the model labels

Keep testing yourself

More quizzes picked for your level.

View all quizzes