Week 5 explainer and transcript
Practice safe decisions, complete a skills challenge, and measure your growth.
Choose a chapter or replay a skill
Use judgment, not fear, to stay safer
Think about how you handle an unexpected request in everyday life. You might ask who is asking, why they need something, and how you can check the story. Those habits are valuable online too. In this lesson, we will examine a fictional urgent message, compare different protections for a file, and choose permissions that fit a task. You do not need to identify every kind of attack by name. You need a repeatable decision process: pause, inspect the evidence, verify independently, and choose an action that limits risk. Use fictional examples throughout. There is no reason to open a suspicious link or expose a private account to complete the practice.
Set up for comfort and control
A workable setup supports attention as well as visibility. Adjust the chair, screen position, text size, and sound to suit the task and your comfort, following the lab's arrangements. Take a screen-free break when needed. People differ in what they find helpful; do not assume one text size or pace suits everyone. Captions, clear labels, keyboard access, and instructions that do not rely on color can help many learners. These are examples of designing for a wider range of users rather than treating access as an afterthought. Pause and choose one control in this course that makes the work easier for you. Explain the benefit in terms of your task.
Recognize pressure in a message
Our fictional message says your service will stop unless you act immediately through a link. The urgency is a reason to slow down, not proof that the request is genuine. Look at what the sender wants you to do: reveal a password, provide a payment, open an attachment, or follow an unfamiliar link. A convincing name or logo can be copied. Even a message from a familiar account deserves a check when the request is unusual. Avoid trying to prove safety by clicking the link. Instead, describe the claim in plain language. Someone says I must provide information immediately. That helps you separate the pressure from the evidence.
Verify through a route you already trust
Open the organization's known website yourself, use a saved bookmark you trust, or find its contact details independently. Do not use the suspicious message's phone number as your independent check. Ask whether the claimed issue exists and what action, if any, is needed. If you already acted, stop further interaction and contact the appropriate official support channel promptly; in the lab, tell the instructor what happened. The exact recovery steps depend on what was shared. Pause and choose between replying to the message for reassurance and checking through a known route. The known route is stronger because it does not let the original sender supply all the evidence for its own claim.
Screen demonstration steps
This is an original screen simulation with fictional practice data. Menus vary by application. Pause or replay each action before trying it yourself.
- Do not follow the message’s link
- Leave the suspicious message
- Open a bookmark you already trust
- Use Contact on the known website
- Verify the claim through the independent contact
Separate editing restrictions from encryption
Imagine a document labeled read-only. That may prevent ordinary editing, but the content can still be readable. Encryption addresses a different question: can someone understand the data without the required key or authorized access? A password can protect different actions depending on the application, so do not assume every password prompt means the file is encrypted. Inspect what the feature actually promises. In our diagram, a readable file becomes protected data that requires a key. That does not remove the need to manage who can access an unlocked device or account. Pause and explain which protection fits preventing accidental edits, and which addresses readable data being exposed.
Treat unknown devices cautiously
A USB drive found in a parking lot might look like an ordinary storage device. You cannot determine that it is safe by its appearance or by the label written on it. Do not plug it into your computer to discover its owner. Give it to authorized staff and follow the organization's procedure. The same general habit applies to unfamiliar attachments or unexpected software prompts: stop and verify the purpose before opening or installing. This is not about avoiding every useful tool. It is about making the source and task clear before granting a device or file a path into your system. Use only the instructor-approved fictional examples for this exercise.
Grant camera and microphone access for a reason
A video meeting may need a camera and microphone, but a simple text page normally has no reason to use them. When a permission prompt appears, identify which app is asking and what task you are trying to complete. Grant access only when the request fits that task and you trust the application. Deny an unrelated request, then review the setting later if a legitimate feature needs it. After a meeting, check the app's state and review permissions when appropriate. A permission decision is not permanent approval of everything an app might do. Pause and compare our two examples. Explain why a meeting and a text page lead to different choices.
Screen demonstration steps
This is an original screen simulation with fictional practice data. Menus vary by application. Pause or replay each action before trying it yourself.
- Which site is asking, and why?
- Trusted meeting + camera task → Allow
- Check the permission that was granted
- A text page does not need the camera → Block
- Review permissions • blocked here
Protect attention and respond to harmful behavior
Safety also includes the way an online interaction affects your attention and wellbeing. Catfishing uses a false identity to build trust. A friendly conversation does not by itself verify the person's story. Fear of missing out can encourage repeated checking of alerts even when you intended to do something else. Choose notification settings and breaks that support your own goals. If a post or interaction becomes harmful, avoid escalating it. Use the service's reporting or blocking tools when appropriate, and seek help from a trusted person or the relevant support channel. You do not have to solve every problem alone or continue a conversation because someone pressures you to respond.
Practice the complete decision process
Here is a new fictional scenario. A message claiming to represent a community service asks for a private code before it will confirm an appointment. Pause the video and state three things: what evidence you have, what remains unverified, and what you would do next. A strong response identifies the unusual request, avoids sharing the code, and checks the appointment through a known contact method. It does not rely only on spelling mistakes or how professional the message looks. Ask a partner to explain a different scenario using the same process. If you disagree, discuss the evidence behind each choice rather than guessing what answer the instructor wants.
Use results to choose your next practice
Before the post-test, review the skills you can demonstrate: adjust a setting and check it, justify a source, choose file access, test a calculation, and communicate a clear next step. Complete the assessment independently, then use its explanations to identify a useful practice task. A classroom score is one piece of evidence, not a judgment about your ability to learn and not a certification result. Keep the saved report if it helps you plan. Choose one skill to repeat with less help and one situation from your own routine where it would be useful. Confidence grows from being able to explain and repeat a successful process, including knowing when to ask for support.