A plausible message and an encrypted destination
A fictional employee receives an email claiming that a shared file will be deleted unless they sign in immediately. The display name resembles a colleague’s name, and the destination webpage shows anHTTPSconnection. Its hostname differs from the organization’s known service, and the message asks for both a password and a current one-time authentication code. The employee proposes replying-all with the code so the helpdesk can solve the issue quickly. The task is to assess the warning signs and identify a suitable verification path without opening the link, contacting anyone or changing an account. No assumption is made that every message with urgency is malicious, but the combination of destination, requested secrets and unverified identity requires careful handling.
1. Does the padlock establish that the requested sign-in is trustworthy?
Read the worked answer
No.HTTPSprotects aspects of the connection to that destination; it does not prove that the destination is the organization’s intended service or that the request is legitimate.
2. What is a suitable next step in the written scenario?
Read the worked answer
Avoid sharing the password or current code and verify through an appropriate known organizational channel or independently reached service. Preserve/report relevant evidence under the actual process rather than forwarding secrets to the recipient list.