High School Beginner • B3.7

Device Basics Review Lab

Apply everything from Module B3 by reviewing a fake student device setup, identifying safer choices, and writing a clear beginner-friendly safety recommendation.

Lesson Progress

Module B3: Computers, Devices, and Operating Systems • Lesson 7 of 7

100%

Readiness Check

Before You Start

Can you name the role of hardware, operating systems, accounts, files, apps, and updates?
Can you explain why permissions and shared-device habits matter?
Can you make a safe recommendation without guessing, blaming, or opening private data?

Why defenders care

Professional Hook

Beginner defenders often start by learning how to read a device situation clearly. They do not need to touch private files, bypass settings, or make dramatic claims. They learn to connect small pieces of evidence: update status, account type, file locations, app permissions, storage health, and shared-device behavior.

This review lab turns the full module into one safe workflow: observe fake evidence, organize what it means, choose approved actions, and communicate the recommendation clearly.

You will be able to

Learning Objectives

  • Review a fake device setup using beginner defensive thinking.
  • Connect device components, operating systems, accounts, files, apps, permissions, updates, and shared-device habits.
  • Separate facts from guesses when analyzing fake device evidence.
  • Choose safe next steps that respect privacy and permission boundaries.
  • Write a short safety recommendation for a student, family, or school setting.

From knowledge to judgment

Why This Matters

Knowing definitions is useful, but cybersecurity also requires judgment. A device review is not just asking, “What is wrong?” It is asking, “What evidence do we have, what risk might it create, what should be handled by approved support, and what should we avoid touching?”

In real school and workplace environments, good defenders are careful. They document calmly, respect boundaries, and ask trusted adults, teachers, guardians, or technology staff when a problem involves someone else's data, account, or device settings.

The device review mindset

Core Concept

A safe device review looks for patterns across the whole system. Hardware can affect access and privacy. The operating system manages accounts and settings. Files and extensions affect how information is opened. Apps and processes request permissions. Updates and system health affect stability. Shared-device habits affect privacy and accountability.

The key is to make recommendations that are defensive, approved, and realistic. Beginner defenders should avoid invasive actions and focus on safer habits, better organization, approved updates, permission review, and trusted reporting.

Visual Diagram

B3 Device Review Map

1

Components

What parts support use, storage, access, and privacy?

2

OS

What manages users, files, apps, and updates?

3

Accounts

Are users separated with appropriate access?

4

Files

Are names, extensions, and locations clear?

5

Apps

Do permissions match real purpose?

6

Health

Are updates, storage, and warnings handled?

7

Shared Use

Will the next user inherit risk?

Terms to review

Key Vocabulary

Component

A device part such as storage, memory, camera, microphone, battery, processor, port, or network adapter.

Operating system

The main software that manages accounts, apps, files, device settings, and updates.

Permission

Access an app or account is allowed to use, such as camera, microphone, files, or location.

Process

An app or background activity running on the device.

Extension

The end of a file name that helps indicate the file type.

Defensive recommendation

A safe suggested action based on evidence, boundaries, and approved support.

How to review the fake device

Technical Breakdown

Observe

Read the fake dashboard, fake files, fake permission panel, and fake shared-device notes.

Classify

Sort each item as healthy, needs review, needs trusted help, or avoid touching.

Prioritize

Handle the highest-risk privacy, update, permission, and shared-device issues first.

Recommend

Write practical next steps that a student, teacher, family member, or technology staff member could safely follow.

Avoid these in the lab

Common Mistakes

Jumping from one warning to a dramatic conclusion without enough evidence.
Opening private files, messages, browser sessions, or another person's account.
Changing school device settings or installing tools without permission.
Ignoring simple maintenance items like approved updates, restarts, and storage cleanup.
Treating every background process as dangerous just because it is unfamiliar.
Writing blame-focused reports instead of calm evidence-based recommendations.

Fake Dashboard

Student Device Review Snapshot

OS Update

Restart required

Account Type

Standard student

Downloads

Mixed files

Saved Passwords

Prompt visible

Camera Permission

Allowed for video app

Camera Permission

Allowed for notes app

Storage

12% free

Shared Session

Previous tab open

[08:10] device_profile: fake_student_laptop_lab_03

[08:12] update_status: restart_required_after_approved_update

[08:13] downloads_review: school_notes.docx, project-final.pdf, project.pdf.exe

[08:15] permission_review: notes_app_camera_access_enabled

[08:17] browser_status: save_password_prompt_visible

[08:18] recommended_boundary: do_not_open_private_files_or_other_accounts

Fake-data only

Safe Defensive Lab

Review the fake device snapshot. Your job is not to fix a real computer. Your job is to write a safe recommendation based on fake evidence.

Good lab action: Recommend saving work, restarting for approved updates, checking unnecessary app permissions with trusted help, avoiding saved passwords on shared devices, and asking staff about another person's open session.
Needs caution: The confusing file name should not be opened. It should be treated as a review item and handled through approved guidance.
Unsafe lab action: Open unknown files, explore someone else's session, disable protections, install tools, or change admin settings without permission.

Device review table

Analyze the Evidence

EvidenceWhat it meansSafe recommendation
Restart requiredAn approved update may not be complete yet.Save work and restart at an approved time.
project.pdf.exeThe file name may be misleading.Do not open it. Ask trusted support for guidance.
Notes app camera accessThe permission may not match the app's purpose.Review with approved settings or technology staff.
Save password promptThe browser may store account credentials.Do not save passwords on shared or school devices.
Previous session visibleSomeone else may have left an account open.Do not explore. Report to trusted adult or staff.

Choose the best response

Scenario Decision Challenge

You are reviewing the fake snapshot for a student laptop. You notice three issues at once: a confusing file extension, a password-save prompt, and an open browser tab from a previous user.

Unsafe response: Open the confusing file to see what it does, click around in the previous user's tab, and save the password so you can finish faster.
Best response: Do not open the file, do not explore the other account, do not save the password, and write a calm recommendation to ask a teacher or technology staff member for approved help.

Skills you should now have

Defender Checklist

  • I can explain how device components, operating systems, accounts, files, apps, permissions, updates, and shared use connect to cybersecurity.
  • I can identify fake evidence that needs review without opening private or unknown items.
  • I can separate facts from guesses when reviewing a fake device dashboard.
  • I can recommend safe next steps using approved updates, permission review, password safety, and trusted reporting.
  • I can write a beginner-friendly device safety recommendation that respects privacy and permission boundaries.

Mini Scored Quiz

Check your device review decisions

1. A fake device dashboard shows a restart is required after an update. What is the safest beginner-level recommendation?

2. Which item is the best example of respecting permission boundaries on a school device?

3. A file is named project.pdf.exe in a fake file list. What should a beginner defender notice?

4. A camera permission is enabled for a fake calculator app. What is the best review question?

5. What is the best final output for this review lab?

Build your cyber notebook

Portfolio Prompt

Write a short “Device Review Recommendation” using this format: 1) what fake evidence you noticed, 2) what risk it may create, 3) what not to touch, 4) what safe approved action you recommend, and 5) who should be asked for help if the issue involves another person's account or school device settings.

Remember

Key Takeaways

A device review should connect hardware, operating systems, accounts, files, apps, permissions, updates, and shared-device behavior.
Good defenders use evidence carefully and avoid opening private data, unknown files, or other people's accounts.
Safe recommendations are calm, realistic, approved, and focused on protecting people and data.