Lab Instructions
What is Cybersecurity?
Follow these written lab steps in order. Run one command at a time and verify output before moving on.
Lab objective and scenario
This lab simulates connecting to a public WiFi network inside the AKT VM so you can see what you are exposed to when you join an untrusted network. Public WiFi at cafes, airports, and hotels is often insecure: traffic can be observed, fake hotspots can steal credentials, and unencrypted data can be captured. No real network is used. Your goal: open the WiFi app, connect to the simulated Public WiFi, then review the "What you are exposed to" panel to understand real-world risks and why you should avoid sensitive activities on public WiFi or use a VPN.
Command
Read brief.txt in the VM (Notes app or Folder Structure) for the same instructions.Expected result: You understand the objective: simulate public WiFi connection and observe exposure risks in a safe environment.
Step 1 - Launch AKT VM and open the lab environment
Click Open Lab Video to launch the AKT Virtual Machine. Sign in (default: akt / 1234). You will see a restricted desktop with only the apps needed for this lab: Folder Structure, Brute Force Lab, and Notes. The mission and step-by-step instructions are in brief.txt; you can read them in the Notes app or by opening brief.txt in Folder Structure. This is a controlled simulation—no real systems are attacked.
Command
AKT Action: Open Lab Video → sign in → view desktop with Folder Structure, Brute Force Lab, NotesExpected result: AKT OS desktop is visible with the three lab apps. You can open Notes or brief.txt to follow the written steps.
Step 2 - Create the wordlist file in Folder Structure
Open Folder Structure (file manager). Create a new file named wordlist.txt. This file represents the list of candidate passwords an attacker would try against the target account. In real attacks, wordlists are built from leaked passwords, common patterns, and dictionary words. Here you will paste a starter list that includes the target actual password so the simulation can demonstrate a successful breach.
Command
AKT Action: Folder Structure → New file → name: wordlist.txt → CreateExpected result: wordlist.txt appears in the file tree and is open in the editor, ready for content.
Step 3 - Fill the wordlist and save
Use the "Copy list" button in the editor toolbar to copy the starter password list (which includes "password" and other common candidates) into the AKT clipboard. Paste into the wordlist.txt editor, then click Save. The wordlist must contain "password" so that when the Brute Force simulation runs, it will eventually try that value and succeed. This models how real attackers use wordlists to guess weak passwords.
Command
AKT Action: Copy list → Paste into wordlist.txt → Save fileExpected result: wordlist.txt contains multiple lines including "password". The file is saved and the status bar confirms it.
Step 4 - Run Part 1 (weak password) and observe the breach
Open Brute Force Lab. The target account password is fixed to "password" for this lab (you do not set it). Click "Run Part 1 (weak password)". The simulation will try each wordlist entry in order; when it tries "password", the account is compromised. Watch the Attack Progress bar and the Live attempt log. You will see an "Access gained" message and the status will show that the credential was cracked. This demonstrates how dangerous weak, guessable passwords are.
Command
AKT Action: Brute Force Lab → Run Part 1 (weak password)Expected result: Simulation runs, attempts are logged, and eventually "Access gained" appears with the message that you have gained access to the target account.
Step 5 - Locate the encrypted file in the target’s folder structure
After the breach, a "Target account files (compromised)" section appears in the Brute Force app. This is the target’s folder structure—it is only visible here, not in the main Folder Structure app. Expand the folders: click the chevron next to "Documents", then expand "confidential". You will see the file aktEncrypted.enc. Click it to view its contents. The file is encrypted: you can see that even with account access, the content cannot be read without the decryption key. This illustrates that encryption is a last line of defense—weak passwords let the attacker in, but encryption can still protect the data.
Command
AKT Action: Brute Force Lab → Target account files → Expand Documents → Expand confidential → Click aktEncrypted.encExpected result: You see the folder tree (Documents → confidential → aktEncrypted.enc) and, after clicking the file, the encrypted file message: content cannot be read without the decryption key.
Step 6 - Run Part 2 (strong password) and observe the block
In the same Brute Force Lab, click "Run Part 2 (strong password)". This simulates attacking an account that uses a strong password (not in your wordlist). The simulation will try entries from the wordlist, fail to find a match, and hit the account lockout limit. The attack is blocked. No access is gained. This shows how strong, unguessable passwords—combined with lockout policy—make brute force impractical.
Command
AKT Action: Brute Force Lab → Run Part 2 (strong password)Expected result: Simulation runs, attempts are logged, and the attack is blocked (lockout) before any compromise. No "Access gained" message.
Step 7 - Compare outcomes and reflect
Compare the two runs: In Part 1, a weak password in the wordlist led to quick compromise and "access" to the target’s folder (with one encrypted file). In Part 2, a strong password not in the wordlist led to lockout and no access. In your own words, summarize: (1) what the attacker did in both runs, (2) why the weak-password account failed, (3) how the strong password and lockout prevented compromise, and (4) why the encrypted file remained protected even after the Part 1 breach.
Command
AKT Action: Write a short comparison (no code): attacker actions, weak-account failure, strong-account defense, role of encryption.Expected result: You can explain in plain language how weak passwords enable brute-force compromise, how strong passwords and lockout block it, and how encryption protects data even when the account is breached.