AP CYBERSECURITY Week 4 Case Files Units 3–4 · Topics 3.4–3.5, 4.1–4.2
0 / 5 cases

Week 4 Case Files

Unit 3 — Securing Networks (Topics 3.4–3.5)  |  Unit 4 — Securing Devices (Topics 4.1–4.2)

This week's investigation follows two organizations: Riverbend Bakery & Café, whose small network relies on firewall rules and log monitoring, and Fairwind Family Clinic, a small medical practice working to secure its devices and staff logins. Work through each case in order. Your responses save automatically to this browser as you type.

Note to students: Riverbend Bakery & Café and Fairwind Family Clinic are fictional organizations created for this lab. All logs, tables, device inventories, and scenarios below are simulated for instructional purposes and do not represent a real business, clinic, incident, or person.
CASE 2027-4A
Firewall Traffic Filtering
Riverbend Bakery & Café · Topic 3.4
NETWORK
DEFENSE

Riverbend Bakery & Café recently installed a firewall to separate its guest Wi-Fi from its point-of-sale (POS) and back-office network. The owner asked the IT contractor to configure rules that keep customers online without exposing the register system or back-office computers to outside traffic.

Review the firewall rule table below, then evaluate whether each overnight traffic event would be allowed or blocked under those rules.

Rule #SourceDestinationPort / ServiceAction
1Guest Wi-Fi (any device)Internet80/443 – HTTP/HTTPSALLOW
2Guest Wi-Fi (any device)POS Server3389 – RDPDENY
3POS TerminalsPayment Processor443 – HTTPSALLOW
4Any external networkBack-Office Network22 – SSHDENY
5Manager LaptopCloud Accounting Portal443 – HTTPSALLOW
6Guest Wi-Fi (any device)Back-Office Printer9100 – RAW/PrintingDENY
Fictional rule set authored for this lab, based on Topic 3.4 concepts (allow rules, deny rules, ports).
#Traffic EventYour Determination
1A guest's phone on Wi-Fi attempts to connect to the POS Server on port 3389 (RDP).
2A front-counter POS terminal connects to the payment processor over port 443.
3An unknown external IP address attempts SSH (port 22) into the back-office router.
4The manager's laptop connects to the cloud accounting portal over HTTPS.
5A guest laptop on Wi-Fi attempts to print directly to the back-office printer (port 9100).
Saved
Saved
CASE 2027-4B
Detecting Network Attacks
Riverbend Bakery & Café · Topic 3.5
INCIDENT
REVIEW

A few weeks after the firewall was installed, Riverbend's manager notices the back-office computer running slowly and asks the IT contractor to check the logs. Normal business hours are 6:00 AM–9:00 PM, and only three employee accounts (Manager, Assistant Manager, Bookkeeper) should ever log in remotely.

Review the network log below. Flag any entries you believe are indicators of compromise (IoCs) using the flag button, then answer the questions.

TimeSourceDestination / AccountEventFlag
6:45 AMFront-counter POSPOS ServerNormal shift login
8:15 AMManager LaptopBack-Office NetworkNormal login, manager account
1:12 AMGuest Wi-Fi devicePOS Terminal3 failed login attempts to POS admin panel
2:47 AM203.0.113.44 (external)Manager account5 failed login attempts in 2 minutes
2:51 AM203.0.113.44 (external)Manager accountSuccessful login after failed attempts
2:53 AMBack-Office Server198.51.100.9 (external)Large outbound data transfer, 1.2 GB
9:10 AMEmployee phoneGuest Wi-FiNormal badge-in connection
3:15 PMVendor delivery scannerGuest Wi-FiNormal vendor check-in scan
4:00 PMBookkeeper LaptopBack-Office NetworkNormal close-out report generated
Fictional log authored for this lab, based on Topic 3.5 concepts (baseline, anomaly, IoC).
CASE 2027-4C
Device Vulnerabilities & Attacks
Fairwind Family Clinic · Topic 4.1
ENDPOINT
RISK

Fairwind Family Clinic is a small medical practice with a front desk, two exam rooms, a billing office, and a waiting room. Staff use a mix of laptops, tablets, and a check-in kiosk to manage patient records. A new IT intern has been asked to audit the clinic's devices before a compliance review.

DeviceOS / Patch StatusObserved IssueVulnerability
Front Desk TabletAndroid 9 (end of life), no updates in 14 monthsOS no longer receives security updatesUnsupported OS — no patches for known exploits
Nurse Station LaptopWindows 10, patches currentAntivirus disabled by staff to "speed up" the computerNo active malware protection
Dr. Ahmed's LaptopWindows 11, 3 critical patches pending (60+ days overdue)Updates postponed repeatedlyUnpatched known vulnerabilities
Waiting Room Check-in KioskWindows 10 IoTPublic USB ports enabled; open web browsing allowedPhysical access / malware injection risk
Billing DesktopWindows 10Standard employee account has local admin rightsViolates least privilege; malware could gain admin access
Personal Phone (BYOD)Unknown / unmanagedStaff member connects personal phone to clinic Wi-FiUnmanaged device on a trusted network
Fictional device inventory authored for this lab, based on Topic 4.1 concepts (endpoint, patch, vulnerability, endpoint protection).
CASE 2027-4D
Strengthening Authentication
Fairwind Family Clinic · Topic 4.2
ACCESS
CONTROL

Following the device audit, Fairwind's office manager asks the IT intern to review how staff log into clinic systems — since the clinic stores protected patient health information, weak logins are a serious risk.

#Login ScenarioYour Rating
1Front desk staff share one login and password for all check-ins to save time.
2A nurse uses a fingerprint scanner plus a PIN to open the medication log.
3Billing staff use a 6-character password with no MFA to access the accounting software.
4Doctors tap an ID badge and enter a rotating 6-digit code to open the patient records (EHR) system.
5The IT admin account still uses the default password set at installation, and it has never been changed.
6A receptionist uses a 20-character passphrase (no MFA) to log into the scheduling calendar.
Fictional login scenarios authored for this lab, based on Topic 4.2 concepts (authentication factors, MFA, least privilege).
CASE 2027-4E
Weekly Review: Securing Networks & Devices
Riverbend Bakery & Café + Fairwind Family Clinic · Topics 3.4–3.5, 4.1–4.2
FIELD
REVIEW

To close out the week, pull together everything you've learned about firewalls, detection, device vulnerabilities, and authentication. Work through four short AP-style scenarios, then reflect on a network topology to finish the week.

Scenario 1 — Network

Riverbend's software vendor asks for direct remote access into the POS network to install updates whenever needed.

Scenario 2 — Device

Fairwind's front desk tablet is running an operating system that no longer receives security updates.

Scenario 3 — Authentication

Fairwind's billing team wants a faster way to log into their shared computer during busy mornings.

Scenario 4 — Detection

An overnight log shows a successful login to the manager's account from an unfamiliar IP address, outside business hours.