Spot the Device-Code Trap
Recognize an unexpected authentication prompt as a phishing cue even when the login page appears legitimate.
The page can be real while the request is not. Which part of the scene is the strongest phishing cue? Unexpected device-code or MFA action Correct. Authentication should answer an action you initiated; an unexpected code request can authorize the attacker's session. Urgent chat timing before a client call A useful cue, but weaker alone. Urgency raises suspicion; the decisive issue is being asked to complete an authentication action you did not initiate. Familiar coworker avatar Not enough. Familiar names and avatars can be spoofed or compromised; they do not make the requested login action safe. Phone available for verification…
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in