Learn Cybersecurity with any AI
Defending the digital world
Cybersecurity is the discipline of protecting systems, data and people from digital threats — and of understanding how attacks work well enough to defend against them. This node is taught strictly defensively: the aim is to build things that don't break, not to break them.
It's part mathematics, part systems engineering, and part human psychology, because most breaches exploit people rather than code. Set your level below.
Compose your prompt
Choose a prompt and a level, then copyA map of Cybersecurity
Defence, in depthThe field, taught from the defender's side.
- Cryptography — the mathematics of keeping information secret and verifying it's genuine.
- Network & systems security — protecting the machines and connections themselves.
- Digital forensics — reconstructing what happened after an incident.
- Governance, risk & compliance — managing security as an organisational discipline.
- Privacy engineering — building systems that protect people's data by design.
- The human factor — why awareness of social engineering matters more than any firewall.
The canon
The foundations of secure systemsReal figures and principles, all defensive.
- Kerckhoffs's principle (1883) — a system should stay secure even if everything about it except the key is public. The bedrock of modern crypto.
- Claude Shannon — put secrecy on a rigorous mathematical footing.
- Diffie & Hellman (1976) — public-key cryptography, which made secure communication between strangers possible.
- Rivest, Shamir & Adleman — the RSA algorithm, long a workhorse of the secure internet.
- "Defence in depth" — the principle of never relying on a single layer of protection.
- Bruce Schneier — popularised security as a way of thinking, not a product.
The live debates
The field's real dilemmasCybersecurity is full of genuine value conflicts.
- Encryption vs lawful access. Strong encryption protects everyone — including from the state. Should there be a way in for authorities? (There's no free lunch here.)
- Responsible vs full disclosure. How and when to reveal a vulnerability so it gets fixed, not exploited.
- Privacy vs security. How much monitoring is justified in the name of safety.
- Is perfect security possible? (No — the honest goal is managing risk, not eliminating it.)
- Security vs usability. The tension between systems that are safe and systems people will actually use.
Where to start
A route inA route in — everything runs from the panel above, and stays defensive.
- Run Orientation on cryptography, or on how systems are protected.
- Sit with Kerckhoffs's principle via the tutor — it changes how you think about secrecy.
- Use Great Debates on encryption backdoors.
- Read a good security primer, thinking always as a builder and defender.
The mindset is the subject: assume things will fail, and design so that when they do, the damage is contained.