Security field notes

Pause before you click.

A convincing message can still be a trap. Verify the request using a channel you already trust.

Look at the request, not just the presentation

Phishing can arrive by email, text, social media, or a phone call. A message may impersonate a colleague, supplier, delivery company, or familiar service. Correct spelling and polished branding do not establish that it is legitimate.

Be cautious when a message creates urgency, requests credentials or financial information, or asks you to change a payment destination. An unexpected attachment or sign-in link deserves a second look.

Verify independently

Open the service through a saved bookmark or its known address. Contact the person through a number or channel already in your records, rather than the contact information supplied in the suspicious message.

Do not reply to the message, open its attachment, or use its unsubscribe link while trying to determine whether it is safe. Report it using your organization’s process or the reporting option in your email service.

If you already interacted

Tell your IT or security contact promptly. Explain whether you opened a page, entered a password, approved a prompt, downloaded a file, or sent money. That distinction helps the response team understand what happened.

For WLC government accounts and devices, use the established internal support channel. Preserve the original message for the team according to its instructions. Do not forward suspicious attachments broadly or continue experimenting with the link.

Further reading

CISA: Recognize and Report Phishing
CISA: Phishing Guidance

Let’s build what comes next.

Start with your needs. We’ll help define the technology.

Start a conversation