A study-and-practice manual for the Master of Cyber Security (MC159P25) — the curriculum broken into what to learn, real labs to run, and quick quizzes to check yourself, so you arrive already fluent instead of starting from zero.
RMIT groups the degree's substance into technical security, attack & defence, and management & risk — then layers specialist electives and a final capstone on top. Tap any area to open it; several include a worked example.
Building security into applications from the first line of code — how software gets attacked, and how developers close those doors before shipping.
If a login form builds a query by directly pasting in what the user typed, typing something like ' OR '1'='1 into the password field can make the query true for every row — which is exactly why input is validated and parameterised queries are used instead of string concatenation.
Protecting the pipes: how traffic moves, where it's exposed, and the layered controls that keep connected systems trustworthy.
Each layer assumes the one before it can fail. A firewall blocks unwanted connections; an IDS/IPS watches what got through anyway. That redundancy is the whole idea behind "defence in depth."
The mathematics behind confidentiality and trust — turning readable data into something only the right key can unlock, and knowing when a hash isn't the same job as encryption.
Encryption is reversible with the right key — HELLO → 8f3a9c... and back again. Hashing is deliberately one-way — a password goes into a hash function and only the fixed-length digest is stored, so the original is never recoverable even by the system holding it.
Reconstructing what happened after a breach — who got in, how, what they touched, and building a defensible evidence trail.
Thinking like an attacker, legally — reconnaissance through exploitation — so you know what a real adversary would try first.
Simulating an attack against a system you're authorised to test — and turning what you find into a report a business can act on.
Reading the signal in the noise — connecting a suspicious login, a failed-auth burst and an odd data transfer into a real incident narrative.
The mirror image of cryptography — probing cipher and protocol weaknesses to understand exactly where "secure" quietly stops being true.
Moving from "can this be hacked?" to "how much does that matter?" — assessing likelihood, impact and the controls worth paying for.
People break technically-sound systems. This is the study of why — phishing, social engineering, and building a culture that resists it.
How organisations turn security into policy — the rules, standards and audits that make "secure" something you can prove, not just claim.
Not "crypto" trading — the security principles behind distributed systems that have to stay trustworthy with no central authority.
Each module has three tabs: Learn explains the concept properly, Practice is a hands-on lab you actually run, and Quiz checks whether it stuck. Work top to bottom — your progress and quiz scores save in this browser.
Pulled straight from the ten modules above. Search to jump to a definition instead of hunting back through each module.
RMIT offers specialist elective areas on top of the core curriculum. You don't need to pick now — but knowing the shape of each helps you steer your pre-study electives above.
Reading attacker behaviour and indicators of compromise before, during and after an incident. Pairs naturally with SOC / blue-team work.
Attacking cryptographic systems to understand where they fail. Maths-heavy; rewards a strong footing in the core cryptography module first.
The path toward senior and leadership security roles — policy, audit and regulatory fluency rather than hands-on-keyboard work.
Security of distributed, trustless systems — architecture, consensus and smart-contract risk, not just cryptocurrency mechanics.
The degree closes with one substantial piece of work. Compare both paths — you'll choose closer to the end of your candidature.
A practical, applied engagement with a real-world cybersecurity problem — the natural choice if you want your capstone to double as portfolio evidence for employers. RMIT's own examples include critical-infrastructure vulnerability evaluation, log-file analysis for threat hunting, and security-controls design and analysis.
A research-oriented path — better suited if you're considering a PhD afterward, or want to go deep on one open question (for example, AI-assisted threat detection or explainable security tooling) rather than deliver a bounded practical artefact.
Install and get comfortable with these before term starts — nobody teaches "how to install Kali Linux" in a master's lecture.