"Cyber security" conjures hoodies and green terminals, but underneath the drama it is a disciplined engineering field with a clear purpose. Strip away the tools and the jargon and it protects just three things.
The CIA triad
Every security control, from a password to a firewall to encryption, exists to protect one or more of:
- Confidentiality — only authorised people can read the data. (Your messages stay private.)
- Integrity — the data has not been altered, secretly or accidentally. (The amount on a bank transfer is exactly what was sent.)
- Availability — the system is there and working when legitimate users need it. (The site stays up; ransomware doesn't lock you out.)
These pull in different directions — locking something down for confidentiality can hurt availability — so security is always a set of trade-offs, not a checkbox.
Think like an attacker: threat modelling
You cannot defend everything against everyone, so you don't try. Instead you threat model — reason deliberately about risk before choosing defences by asking four questions:
- What are we protecting? (The assets — data, money, uptime, reputation.)
- Who are we protecting it from? (The adversaries — a bored script kiddie, a competitor, an insider, a nation-state. Their skill and motivation differ enormously.)
- How could they attack it? (The attack surface — every input, account, dependency and person is a way in.)
- What happens if a defence fails? (The impact — and so how much the defence is worth.)
The output is priorities: spend effort where the likely, damaging threats are, not on exotic ones that won't happen or trivial ones that don't matter.
There is no perfect security
A crucial mindset: absolute security does not exist. Given unlimited time and resources, most things can be broken. The realistic goal is to make an attack cost more — in time, money, skill or risk — than the target is worth to the attacker, and to detect and recover when something does get through. Security is economics and probability as much as technology.
With the why in place, the rest of this track builds the how. It starts with the two cryptographic primitives nearly everything else rests on: hashing (for integrity) and keys (for confidentiality). Hashing is next.