Security Principles overview
93 topics in 15 lessons, each in one line. Every topic opens the page that teaches it.
After this course you can
- Weigh a risk by likelihood and impact, choose how to treat it, and name the control that does the job.
- Explain how attacks unfold and how identity, cryptography, network, endpoint and data controls stop them.
- Detect, respond to and recover from an incident, and map the work to frameworks such as NIST CSF and ISO 27001.
1Security principles and risk
- The CIA triadEvery security failure breaks one of three promises about data
- Threats and vulnerabilitiesA loss needs a threat, a weakness and something worth taking
- Likelihood and impactRank risks by how likely they are and how much they would hurt
- Risk treatmentReduce, transfer, avoid or accept: every risk gets one answer
- Control typesSome controls act before an attack, some during it, some after
2Attackers and how attacks unfold
- Threat actorsAttackers differ by motive, skill and money, and so must the defence
- Initial accessMost breaches start with a stolen login, an exposed flaw or a lure
- The Cyber Kill ChainAn intrusion runs through seven steps, and each is a chance to stop it
- Ransomware as a serviceRansomware is an industry, with suppliers, brokers and affiliates
- Supply chain attacksOne breached supplier opens the door to every one of its customers
- AI-enabled threatsAI makes old attacks cheaper and opens new ones against AI itself
3Social engineering
- Social engineeringAttackers persuade people rather than break machines, using six levers
- PhishingA phishing email gives itself away in seven places
- Phishing channelsThe same trick arrives by email, phone, text, QR code and in person
- Business email compromiseOne email in a real thread can redirect a payment, with no malware
- PretextingA believable story and a helpful help desk can hand over the keys
- Security awarenessSomeone will click; what matters is how fast someone reports
4Malware and vulnerabilities
- Malware typesName malware by how it gets in, hides and what it does
- Worms and patchingWannaCry hit 59 days after the fix was already available
- InjectionSQL injection turns a user name into a database command
- CVE and disclosureEvery public flaw gets a number, then the race begins
- Patch managementAttackers now exploit new flaws in days, not months
5Cryptography
- Cryptographic primitivesThree tools do almost all of it: one key, two keys, or no key
- Symmetric encryptionEach extra key bit doubles the work: 56 bits fell, 128 never will
- Key distributionShared keys must be delivered first, and their number explodes
- Asymmetric encryptionAnyone can lock with a public key; only the private key opens it
- HashingChange one character, and about half the fingerprint changes
- Digital signaturesSigned with a private key, checked with the public one
- Hybrid encryptionReal systems combine all three tools, each for what it does best
6Certificates and TLS
- Why certificates existA public key is worthless until something proves whose it is
- X.509 certificatesA certificate is a signed card: who, which key, until when
- Chain of trustYour device trusts a few roots; every site borrows that trust
- Certificate validationFive checks stand between you and a fake website
- Certificate lifetimesCertificates will last 47 days, so renewal must be automatic
- TLS handshakeTLS 1.3 sets up a secure connection in one round trip
7Authentication
- Authentication factorsThree kinds of proof, and what a thief must steal to beat each
- Password storageA server should keep a salted, slow hash, never the password itself
- Password policyLength beats complexity, and forced changes make passwords worse
- Credential stuffingOne reused password unlocks every site that shares it
- Second factor strengthEvery second factor helps, but only some survive a phishing page
- PasskeysA passkey signs a challenge, and the server keeps nothing worth stealing
8Authorisation and access
- Identity life cycleAccess must follow each person from joining, through moves, to leaving
- Access control modelsWho decides: the owner, labels, a role, a rule, or attributes
- Privileged accessAdmin power should be borrowed for an hour, not owned all year
- Single sign-on and SAMLOne identity provider vouches for you, and every app trusts it
- Conditional accessEach sign-in is judged by who, which device, where and how risky
9Network security
- SegmentationSegmentation turns one break-in into one room, not the building
- Firewall rulesA firewall reads rules top to bottom; the first match decides
- IDS and IPSAn IDS tells you about an attack; an IPS can stop it
- Zero trustZero trust checks every request; location earns nothing
- VPNsA VPN protects the path across untrusted networks
- DDoSAgainst a flood, the defence is to be bigger than the flood
- Secure protocolsEvery clear-text protocol has a secure twin, on its own port
10Protecting devices, applications and data
- Data statesData at rest, in transit and in use each need their own lock
- Data classificationClassify data first, or every file gets the same protection
- Data loss preventionDLP catches sensitive data on its way out the door
- HardeningHardening removes every door you do not need, and locks the rest
- Endpoint detectionEDR judges what a program does, not what the file looks like
- Secure developmentSecurity is built into every stage of development, not tested in
11Detecting attacks
- Dwell timeAttackers once hid for a year; detection cut it to two weeks
- LoggingEach log source answers one question; together they tell the story
- SIEMA SIEM joins four quiet signals into one alert worth waking for
- Vulnerability scanningGive a scanner credentials, and it sees what is really installed
- Penetration testingA penetration test proves what an attacker could really do
12Incident response
- Incident response lifecycleIncident response is a cycle that starts before the incident
- Running an incidentThe hardest part of a response is the decisions, made at speed
- ContainmentContain fast, but know what each action costs you
- Digital forensicsCollect the evidence that disappears fastest, first
- Chain of custodyA chain of custody proves the evidence was never touched
- NotificationReporting deadlines are counted in hours, not weeks
- Lessons learnedLessons learned keeps asking “why?” until it reaches a fix
13Backup and recovery
- RPO and RTORPO is how much data you can lose; RTO is how long you can be down
- Backup typesIncremental is quick to take and slow to restore; differential the reverse
- The 3-2-1 ruleKeep one copy that attackers can’t reach, and prove it restores
- Availability and redundancyEach extra nine cuts downtime tenfold and costs far more
- Recovery sitesThe faster you must recover, the more you keep running in advance
- Business impact analysisThe business, not IT, decides what comes back first
- Testing recoveryA recovery plan nobody has tested is only a hope
14Governance, risk and compliance
- Compliance chainEvery legal requirement traces to a policy, a control and proof
- NIST CSF 2.0NIST CSF 2.0 puts Govern at the centre of security
- ISO 27001ISO 27001 certifies a system that keeps improving
- RegulationsWhich rules apply depends on whose data you hold and where
- Residual riskControls shrink a risk; what is left is accepted on the record
- Third-party riskYou can outsource the work, but not the responsibility
- Audits and attestationType I shows good design on a day; Type II proves it worked all year
15One email, one breachWorked case
- The problemA breach usually starts with one ordinary-looking email
- The attack chainAn attack is a chain, and each link needs the one before it
- The first defenceTraining is a filter, not a wall
- The causeEach link held because one control was missing there
- The fixThree controls, one per link; any one stops the chain
- Respond and recoverResponse runs in the same order; the alert decides when it starts
- Defence in depthLayers around what matters, so one failure is not the end
- A real caseAt Twitter in 2020, a phone call and a fake VPN page
Sources and credit
61 sourcesThe chapters and drawings are written by NeuroqAI from these sources. Each lesson lists its own at the end of its chapter, and figures on the pages are taken from them or computed from them.