Skip to main content

What to Capture for a Suspicious Login Alert

November 16, 2026 5 min read
A blank security notice card and notebook on an office desk.

When an unfamiliar device or login appears in a security alert, the first priority is to report it safely. The details you capture can help your security contact determine what happened, but you do not need to investigate the alert yourself.

This checklist covers what to capture for a suspicious login alert, how to record actions you have already taken, and how to pass the information along. Follow your company’s incident reporting process if it gives different instructions.

Start with a safe response

Do not click links or open attachments in an alert email to investigate. An unexpected alert could be genuine, but an email that imitates a security notice can also lead to a fake sign-in page. Instead, report it through a company channel you already know, such as your established help desk or security contact. If your company has a security portal, access it using a saved bookmark or the address you normally use, not a link in the message.

Preserve the alert and report it promptly, especially if you recognize that you approved a sign-in, entered a password, or clicked something connected to it. Avoid deleting the message, changing settings, or trying to test the unfamiliar device. The person handling security can advise you on the next step.

A folder and blank note cards arranged on a desk to represent securely sharing an incident report.

What to capture for a suspicious login alert

Record what the alert actually says and what you observed. You do not need to interpret technical details or decide whether the activity was malicious. A useful report is factual, specific, and clear about what you do not know.

  • Where the alert appeared: Note whether it came by email, appeared in an app, or showed up in a work account’s security page. Include the alert’s subject or heading and the service or account it refers to.
  • The alert wording: Copy the relevant text, including any stated reason for the alert. If you cannot copy it safely, describe it in your own words and mark it as a summary.
  • When you saw it: Record the date and time shown in the alert, if available, and when you personally received or noticed it. Include your time zone. If you are unsure which time zone the alert uses, say so rather than guessing.
  • The account involved: Identify the work account, email address, or username named in the notice. Share account details only through your company’s approved reporting channel.
  • The device and sign-in details: Note any device name or type, browser, operating system, location, IP address, or application listed. Include only what the alert shows; do not search for or try to verify technical details on your own.
  • Whether the sign-in succeeded or failed: Record the result if it is displayed. If the alert does not say, note that the result is unknown.
  • What you recognize: Say whether the device, location, or sign-in time could be yours. An unfamiliar location alone does not prove that someone else signed in. IP-based location information can be approximate, as noted in Microsoft’s sign-in log activity details.
  • What you did afterward: Make a short timeline of your actions, such as opening the alert, clicking a link, entering a password, approving or denying a multifactor authentication prompt, changing a password, or contacting support. Include approximate times if you do not know the exact time.

Microsoft’s guidance for viewing work or school sign-in activity can help explain what account activity may be visible to a user, but your company may use different systems or processes. Use your organization’s instructions for reporting and follow-up.

Should you take a screenshot?

A screenshot can help preserve the alert’s wording and visible details. If company policy allows it, capture the relevant alert and keep the original message when possible. Do not edit, annotate, or forward it through a personal account. A screenshot is useful evidence, but it does not replace a written note about what you did after seeing the alert.

Alert screenshots and sign-in information may contain sensitive account or business details. Send them only through a company-approved channel, such as the established security ticketing system or a direct report to the designated contact. If you are unsure whether a channel is approved, ask your manager or security contact how to share it. Do not post the image in a public or broadly shared chat.

Copy-and-paste report template

Use this as a starting point. Leave a field blank or write “not shown” if the information is unavailable. Do not guess.

  • Alert source and heading:
  • Alert wording or summary:
  • Date and time shown, including time zone if available:
  • When I noticed the alert, including my time zone:
  • Account named:
  • Device, browser, or application shown:
  • Location or other sign-in details shown:
  • Sign-in result shown, or unknown:
  • Do I recognize this activity? Why or why not?
  • Actions I took, in order, with approximate times:
  • Screenshot or original alert preserved and shared through:
  • Best way to reach me:

What to leave for the security responder

Employees can preserve the alert, note what they saw, and describe their own actions. Technical investigation is a separate job. A security administrator or provider may need to review sign-in logs, compare account activity, confirm device information, or determine whether an access session needs to be secured. Those details may not be visible in the alert you received.

Do not try to log into an unfamiliar device, contact a location shown in the alert, or collect extra technical information by experimenting with account settings. Send your factual report and let the person handling security decide what to check next. For a clearer picture of what may happen after reporting, see what happens after a suspicious sign-in alert.

A written response process helps staff know where to send a report and what to expect. If your company is reviewing its process, this guide to incident response planning for small companies offers a related starting point.

Frequently asked questions

Should I click links in a security alert email?

No. Report the message through a company channel you already trust. If you need to check your account, use your usual saved bookmark or known address rather than a link in the alert.

Should I include whether the login succeeded or failed?

Yes, if the alert shows the result. If it is missing or unclear, say that it is unknown. Do not infer success or failure from other details.

What if I clicked a link or approved an MFA request?

Tell the security contact promptly and record what happened, including the action and approximate time. Be direct about whether you entered a password or approved a prompt. Do not hide a mistake or try to undo it without instructions.

How should I share screenshots or alert details?

Use the company’s approved security reporting channel and limit access to people who need the information. Do not send sensitive details to a personal email account or share them in a public channel.

Make the report, then follow instructions

A useful suspicious-login report does not need to solve the incident. Capture the alert, account, time and time zone, visible device details, sign-in result, and your actions. Then send the information through the known company channel and wait for guidance. If your business needs help preparing staff for security events, Zevonix provides fully managed cybersecurity for small businesses. You can call (904) 658-0777 to discuss your needs.

Ready to Strengthen Your IT?

Let Zevonix handle your technology so you can focus on what matters most — your business.

Schedule a Free IT Assessment