Cybersecurity protects the confidentiality, integrity and availability of systems and information. Students encounter these concerns when using passwords, saving assignments, accessing school portals and exchanging documents. Small routine choices often determine whether an account remains secure.
The following lessons focus on prevention, detection and safe response. They are not instructions for attacking systems, and you should never experiment on accounts, networks or devices without authorization. Use the official CYB111 course guide for the current academic terminology.
What you will be able to do
- Recognise confidentiality, integrity and availability concerns.
- Spot warning signs in suspicious messages.
- Apply layered account and data protections.
- Outline a lawful, evidence-preserving response to an incident.
Lessons with worked examples
1. Security goals and risk thinking
Confidentiality means that information reaches only authorized people. Integrity means records remain accurate and are changed only appropriately. Availability means authorized users can access services when needed. These goals can compete: a very restrictive login may improve access control but, if poorly designed, make a service unusable for legitimate students.
A threat is a potential cause of harm, a vulnerability is a weakness that can be exploited, and risk involves the likelihood and impact of an unwanted event. An asset might be an academic record, a phone or a customer database. Identify what matters before choosing controls: not every asset faces the same threats or needs the same measures.
- Identify the asset, threat, vulnerability and consequence.
- Consider confidentiality, integrity and availability separately.
- Prefer proportional protections rather than one-size-fits-all claims.
Worked example — examination portal account
Asset: student account. Threat: unauthorized access. Weakness: a reused password. Impact: changed contact details or exposed records. Controls might include a unique password, multi-factor authentication where supported, and awareness of session activity. This explains security from the user’s viewpoint without attempting unauthorized access.
Takeaway: Security decisions are more effective when tied to a concrete risk.
2. Recognising social engineering and phishing
Social engineering manipulates human trust, fear or urgency. A phishing message might imitate a school office and demand immediate login through a suspicious address. The sender’s name and logo are not proof of authenticity; attackers can copy visual designs or display misleading names.
Safely verify messages through a previously known official channel, not a phone number or link supplied by the suspicious message itself. Be wary of requests for passwords, one-time codes or payment to restore access. If you clicked an unexpected link, avoid supplying further information and follow your organization’s incident guidance.
- Check destination domains instead of trusting button text.
- Treat urgent requests for credentials or OTPs as suspicious.
- Verify independently through known official contact methods.
Worked example — fake registration alert
A message says, “Your NOUN account closes in 10 minutes; verify your password now,” and links to a look-alike website. A safer response is to open the university portal using a saved trusted address, inspect notices there and report the message if appropriate. The correct response does not require forwarding the suspicious link to other students.
Takeaway: Independent verification defeats many urgent-message scams.
3. Layered access control and backups
Authentication establishes who is requesting access; authorization determines what they may do. Multi-factor authentication adds another check beyond one password, reducing risk from stolen passwords. Access should be limited to what a person needs to perform an approved task, and old permissions should be reviewed regularly.
Backups protect availability and recovery, but an unchecked copy is not automatically useful. Keep independent copies, protect them from the same failure or ransomware incident and test restoration periodically. An illustrative 3-2-1 backup strategy maintains three copies, on two storage types, with one copy off-site or otherwise isolated.
- Use unique passwords and MFA when available.
- Apply least privilege to accounts and shared files.
- Test backups by safely restoring a non-sensitive sample.
Worked example — shared project folder
Five students collaborate on a report. Everyone needs access to the current draft, but not everyone needs permission to delete the entire archive. Give appropriate edit roles, restrict deletion and maintain a separate backup of milestone versions. If a mistake occurs, restore from a verified previous version instead of relying on memory.
Takeaway: Authorization and recoverability are distinct parts of protection.
4. Responding to a possible incident
Incident response is a structured way to handle suspected harm: prepare, identify, contain, recover and learn. The precise sequence and reporting duties depend on the organization. A student noticing unfamiliar account access should use official recovery tools and alert the responsible support team rather than testing the suspicious activity or confronting unknown actors.
Keep accurate notes on what you observed and when, without publishing sensitive evidence. Changing compromised credentials, revoking sessions and scanning devices may be appropriate when directed by trusted support channels. After recovery, review what made the incident possible and improve procedures. Avoid destroying evidence when a formal investigation is required.
- Record facts and timestamps, not guesses about a culprit.
- Use official support channels and approved containment measures.
- Review lessons and update controls after recovery.
Worked example — unexpected sign-in notice
You receive an authentic-looking alert about an unrecognized sign-in. Instead of replying to the alert email, open the service from a known address, inspect active sessions and security settings, secure the account using official tools and notify support. Record the notification and steps taken. This limits risk while avoiding unverified links.
Takeaway: An orderly response is safer than improvisation.
Apply what you learned — CYB111 Practice Clinic
Original independent learning exercise. Try it before opening the worked explanation; this is not an official NOUN examination question.
Respond safely to an account-verification scam
Situation: A message uses a familiar logo, claims your school account will close in ten minutes and asks you to share a one-time code.
Your task: Identify three warning signs and propose safe actions without disclosing credentials or attacking the sender.
Reveal the step-by-step solution
- Recognise urgency and threatened loss of access as possible social-engineering pressure.
- Note that visual branding alone cannot prove the sender or destination is genuine.
- Do not send an OTP, password, recovery code or session token.
- Open the official university service independently, review sign-in activity if applicable and report the suspicious message through the official support process.
Answer: Treat the request as suspicious; verify independently using a known official route and never disclose the one-time code.
Common mistake to avoid: Do not assume HTTPS or a padlock proves that a website belongs to the university.
Test yourself — original practice questions
These are independently created learning questions, not official NOUN TMA or examination questions. Try each one before revealing the explanation.
Question 1. Protecting a record against unauthorized modification primarily concerns:
- Availability
- Integrity
- Bandwidth
- Screen resolution
Show answer and explanation
Answer B: Integrity
Integrity concerns data accuracy and protection against improper change.
Question 2. An urgent message requests your one-time login code. What is safest?
- Send it if the logo looks familiar.
- Share it only with classmates.
- Verify independently and do not share the code.
- Post it to a group for advice.
Show answer and explanation
Answer C: Verify independently and do not share the code.
OTP codes are authentication secrets and should not be provided to unverified requests.
Question 3. The principle of least privilege means:
- Everyone gets administrator access.
- Each user receives only necessary permissions.
- All users share one account.
- Backups should never be tested.
Show answer and explanation
Answer B: Each user receives only necessary permissions.
Limiting permissions reduces the harm possible from accidents or compromised accounts.
Question 4. Which is the best initial action on noticing a suspicious account sign-in?
- Try to hack the suspected intruder.
- Publish private account evidence online.
- Ignore it entirely.
- Use the official account security and recovery process.
Show answer and explanation
Answer D: Use the official account security and recovery process.
Authorized recovery and reporting routes protect the account without unauthorized escalation.
Three things to practise this week
- Check your own accounts for unique passwords and available MFA, without sharing any credentials.
- Draft a phishing-awareness checklist for classmates with two verification steps.
- List the files you could not afford to lose and plan how to test one backup safely.
Continue learning on PsalmEduLabs
Look up CYB111 in the relevant tool. Course availability may vary; we do not expose PRO-only documents in these public lessons.
Verify the course with NOUN
Check your current official course material for assessment rules, units and session-specific instructions. Institutional pages below establish course identity and broad subject context; they are not citations for our original worked exercises.
Continue with a related course
Build on this topic using another free PsalmEduLabs learning guide.