Cybersecurity in Everyday Work

Cybersecurity in Everyday Work Make a safer next move Practical cybersecurity guidance for everyday work, from messages and sign-ins to sharing information. This fictional example follows Northstar Works, a cross-functional organization. Start with the topic that matches your situation; if a work account, device, or information may be at risk, use your organization's approved urgent help route. Pause, check, then act If a request or sign-in feels unexpected, pause before clicking, replying, approving, or sharing. Verify through a work channel you already trust, never send passwords or authentication codes, and use the approved help route if something may already have happened. Choose a topic Open the page that best matches the decision in front of you. Suspicious messages Notice unusual requests and decide how to verify or report them. Accounts and devices Review everyday sign-in and device habits, and what to do when something seems wrong. Sharing information Check the audience, scope, and method before sharing work information. Urgent help Know what context to give when a work account, device, or information may be at risk. A small check can prevent a bigger detour A fictional Northstar Works scenario shows how these decisions connect. A request arrives out of context A project coordinator receives a message asking for a full planning file before a meeting. The sender name looks familiar, but the request does not match the team's usual workflow. Pause instead of opening the attachment or forwarding the file. Check with the colleague through a known work channel. Share only what the work needs After verifying the meeting request, the coordinator shares a short summary with the named collaborators rather than sending the full file to a broad, unverified audience. Confirm who needs the information. Use an approved method for the information and audience. Who does what Role descriptions are illustrative, not a directory of assigned staff. Every employee: pause when something is unexpected, protect sign-in details, limit sharing to the intended audience, and raise concerns through approved routes. IT support: helps with workplace technology and account or device questions through the organization's established support channels. Security specialists: assess suspected security concerns and advise through the organization's designated security process. Use the approved urgent route when an issue may be time-sensitive. IT and Security owns this fictional guide. Follow the organization's established route to ask a question or flag a correction. Suspicious messages Spot what does not fit Unexpected context matters as much as an unfamiliar sender. Pause when a message asks you to act quickly, share credentials, approve a sign-in you did not start, open an unexpected attachment, or transfer information outside the normal workflow. Check whether the sender details and request fit the conversation you were already having. A familiar display name is not enough to verify a request. Do not use a link or phone number supplied in a suspicious message to check whether it is genuine. Compare the request with the context Fictional Northstar Works examples. Expected work request You are already discussing a meeting agenda with a colleague. A message asks for the agenda section you agreed to prepare, and the request matches the conversation. Check the recipient before sending. Share only the agreed material using an approved method. Unexpected high-pressure request A message claiming to be from a senior colleague demands a password and a full project file immediately, though you were not expecting either request. Do not reply with credentials or open the message's links. Verify through a known work channel and use the approved reporting route. Make a safe decision If the message remains suspicious, use your organization's approved reporting route. Pause Do not click, reply, open an unexpected attachment, or approve an unexpected sign-in. Verify separately Contact the person through a work channel you already know, not details supplied by the message. Report through the approved route Use the organization's suspicious-message reporting process. If you already entered account details or approved a prompt, go to Urgent help. Choose the next page Urgent help For a possible account, device, or information risk. Accounts and devices If the concern involves sign-in details or an unexpected authentication prompt. Accounts and devices Protect the sign-in and the device Use the account and device practices approved for your work environment. Use the organization's approved sign-in method. Do not share passwords or authentication codes, and do not approve a sign-in prompt you did not initiate. Lock a device when you step away, and keep work on devices approved for your role. Exact sign-in, recovery, and device requirements can depend on your organization's approved environment. Follow its current instructions rather than improvising a recovery or security procedure. If a sign-in does not look right An unexpected authentication prompt appears Do not approve it. If you initiated a sign-in, stop and verify through a known work channel before proceeding. If the prompt continues or you think someone else may be using your account, contact the approved IT or security route. Note when the prompt appeared. Do not share a one-time code or password in a message. You may have shared account details Use the approved urgent route promptly and explain what information may have been exposed and what you did. Follow the organization's account recovery instructions; do not rely on a message that prompted the disclosure. Do not include passwords or authentication codes in your report. Use the Urgent help page for the appropriate handoff. Choose the right kind of help Route descriptions identify responsibilities; use the actual routes approved by your organization. Situation Next step Routine device or sign-in question Contact the organization's approved IT support route. Unexpected prompt or possible account compromise Use the approved urgent IT or security route promptly. Concern began with a suspicious message Use the approved suspicious-message reporting route; explain if account details were also shared. Related guidance If the concern began with a suspicious message, review Suspicious messages . For a suspected account or device concern, use Urgent help to identify the appropriate handoff. Sharing information Check before you share Match the recipient, amount of information, and sharing method to the work. Before sending or granting access, check who needs the information, whether each recipient is the intended audience, and whether the method is approved for that information. If you cannot confirm the audience or the right method, pause and ask the responsible team through an approved work channel. A short summary or the whole file? Fictional Northstar Works example. Narrow, verified audience A coordinator confirms that three named collaborators need the date and agenda decisions from a project meeting. They share a brief summary using an approved method. The recipients match the task. The shared content is limited to what they need. Broad, unverified audience A request asks for the entire project folder to be forwarded to a broad group whose membership has not been checked. The request does not explain why everyone needs access. Pause rather than forwarding the folder. Verify the request and check the approved sharing method. Run a pre-share check Use these questions before sending a file, message, or access invitation. Recipient: can you identify who will receive or access the information? Scope: are you sharing only what those people need for this task? Sensitivity: does the information require a particular approved handling method? Method: is this channel or access method approved for this information and audience? If anything is unclear, pause and ask the responsible team through a known work channel. If the situation changes Urgent help If information may have gone to the wrong audience. Suspicious messages If a message prompted an unexpected sharing request. Urgent help A work account, device, or information may be at risk? Use your organization's approved urgent IT or security route promptly. This site does not provide incident submission or replace that process. Share useful context, not secrets A clear account of what happened helps the responsible team understand the concern. Describe the event Say what you noticed and when it happened, using approximate times if needed. Identify the work account, device, or information involved without including secrets. Explain what you clicked, approved, sent, or changed, if anything. Keep credentials private Never include passwords, authentication codes, or recovery codes in a report or ordinary message. Do not forward sensitive credentials to colleagues. Follow instructions only through the organization's approved route. Urgent concern or routine question? Choose based on what may be at risk; use the actual support destinations approved by your organization. Possible security concern An account or device may be compromised, an unexpected sign-in was approved, or information may have reached the wrong audience. Contact the approved urgent IT or security route promptly. Include what happened, when, and what action you took. Do not send passwords or authentication codes. Routine question You need ordinary help with a device or sign-in and have no indication of a security incident. Use the organization's established IT support route. If new facts suggest a risk, switch to the approved urgent route. Review the related topic For sign-in prompts, account details, and device habits, see Accounts and devices . If a message prompted the concern, see Suspicious messages . For a possible unintended information share, see Sharing information .