Unexpected account activity
The employee receives a sign-in, password, recovery, forwarding, or profile-change notice they did not initiate.
Account Takeover Awareness
How to Recognize and Report Account Takeover
Account takeover occurs when an unauthorized person gains control of an account and can act as its legitimate user.
Use this guide to turn the threat into a clear employee decision, a safe practice scenario, and a reporting step your organization can support.
Plain-English definition • Warning signs • Safe simulation ideas • Reporting practice
01Understand the threat
Account Takeover: a practical definition
Account takeover occurs when an unauthorized person gains control of an account and can act as its legitimate user.
Phishing is one possible entry point, but reused credentials, stolen sessions, malicious applications, and recovery-process abuse can also contribute. Awareness should focus on suspicious requests and early reporting rather than asking employees to diagnose the technical cause.
Source: CISA Phishing Guidance
02Recognition clues
Warning signs employees can check in a account takeover message
No single clue proves that a message is malicious. Teach employees to combine the request, sender, business context, destination, and available verification route before acting.
Unsolicited authentication
A message, caller, or prompt asks for a password, approval, authentication code, or recovery secret.
Messages sent as a known person
A familiar account begins making unusual payment, document, access, or secrecy requests.
03Safe response
Move from suspicion to a supported next step
| Moment | Employee action | Program preparation |
|---|---|---|
| Before acting | Open the known account service independently and contact the approved support or security route when activity cannot be explained. | Publish the authentic contact, application, or reporting route somewhere employees can reach without using the message. |
| When uncertain | Pause the request and report it through the approved channel with enough context for review. | Explain what the response team needs and how employees will know that their report was received. |
| After an interaction | Stop, contact the responsible team promptly, and describe the action taken without hiding the mistake. | Provide a well-known response route and avoid communications that discourage early reporting. |
Source: NIST: Recognizing, verifying, and reporting phishing
04Practice safely
Account Takeover simulation and discussion ideas
Choose one learning objective per exercise. Use fictional people, organizations, accounts, payments, documents, and events, and test the reporting route before sending to employees.
Unexpected sign-in notice
Use a fictional alert and practice reaching the real account-security page without following the message link.
Known-account request
Discuss an unusual document or payment request sent from a familiar fictional mailbox.
Early-reporting drill
Rehearse what information an employee should provide after an unexplained authentication prompt or account change.
05Campaign workflow
Build the exercise around a decision employees can repeat
- 1
Define the behavior
Write down the account takeover clue being practiced, the expected action, the authorized audience, and the owner of follow-up.
- 2
Confirm the real process
Test the independent verification route, message-reporting option, response handoff, and employee support path from a representative account.
- 3
Pilot the scenario
Check delivery, links, landing content, accessibility, event records, automated inspection, stop conditions, and the explanation employees will receive.
- 4
Review in context
Reconcile intended recipients, successful deliveries, unique employee events, verified reports, response handling, and completed follow-up before drawing conclusions.
Source: NIST SP 800-50 Rev. 1: Building a Cybersecurity and Privacy Learning Program
06Useful measurement
Evaluate recognition, reporting, and the surrounding process
Record actual counts and denominators for delivery, unique recipient events, reports, and follow-up. Separate automated email inspection and repeat events where the available evidence supports doing so.
A account takeover exercise samples one scenario under one set of conditions. It does not establish an employee's intent, overall security awareness, or likelihood of responding the same way to a real attack.
Use findings to improve the real workflow: clearer verification instructions, easier reporting, faster response handling, better role-specific training, or a business control that reduces reliance on email alone.
Common questions
Common questions about Phishmake's features, onboarding, and support, answered to help you get started with confidence.
Is account takeover the same as credential theft?
No. Credential theft may enable takeover, but account control can also be gained through stolen sessions, malicious application consent, recovery abuse, or other methods.
What should employees report first?
They should promptly report what they observed and any action they took, using the known support or security route. The responsible team can determine the technical response.
Can account takeover be used in a phishing simulation?
It can be practiced when the scenario is authorized, proportionate, and tied to a real reporting or verification process. Do not access, alter, lock, or attempt to compromise a real account. Do not generate production authentication prompts or collect credentials, codes, sessions, or recovery information.
How should account takeover simulation results be measured?
Review successful delivery, unique employee events, reports, response handling, and completed follow-up. Include scenario difficulty and operating context, and do not treat a click or report as a complete measure of employee risk.
Sources & further reading
Published by Phishmake · Updated
Keep building your program
All resourcesPut it into practice
Turn account takeover awareness into a repeatable response.
Use Phishmake to run controlled employee simulations, review campaign activity, assign relevant training, and keep follow-up records in one workflow.