Swipe left or tap Next ▶ to turn the page.
Select any text to highlight it or add a note. Tap a diagram to enlarge it.
Security Basics: CIA Triad, Risk, Common Attacks and Security Controls
- ✔ Explain the CIA triad and map any security incident to the property it breaks
- ✔ Tell threats, vulnerabilities and risk apart and score a risk with likelihood and impact
- ✔ Recognise phishing, malware and denial-of-service attacks and name the defences for each
- ✔ Classify security controls by function and by type, and apply defence in depth and least privilege
What cyber security protects
Every interview for a security role starts here, so you should be able to explain the field in two minutes without notes.
Cyber security protects information and the systems that hold it from harm, whether from criminals, careless staff, buggy software or a flooded server room. Attacks can never be made impossible, so the aim is to make them hard, noticeable and recoverable.
Think of a busy railway station: ticket checkers, CCTV and locked control rooms each cover gaps left by the others. Cyber security works the same way.
What a fresher actually does
Entry-level security jobs are mostly defensive. Typical tasks are:
- Watching alerts in a Security Operations Centre (SOC) and deciding which ones are real.
- Checking that laptops are patched and that antivirus is running.
- Reviewing who has access to which system and removing access that is no longer needed.
- Helping staff report suspicious emails.
The three questions behind every security decision
- What are we protecting? (the asset)
- What could go wrong? (the threat and the weakness)
- What will we do about it? (the control)
Today answers these in order. Days 2 to 5 cover networking, web security, cryptography and identity, and SOC work.
The CIA triad
Every security incident breaks at least one of three properties. Naming the right one is the most common fresher interview question.
The CIA triad is the base model of security: three properties we want information to keep.
| Property | Meaning | Typical protection |
|---|---|---|
| Confidentiality | Only authorised people can read the data | Encryption, access control, screen locks |
| Integrity | Data is accurate and not changed without permission | Hashing, digital signatures, change logs |
| Availability | Systems and data work when needed | Backups, spare servers, DDoS protection |
Same data, three different failures
Take a hospital's patient records:
- A receptionist reads a celebrity's medical file out of curiosity: confidentiality is broken.
- Someone changes a patient's blood group in the record: integrity is broken.
- Ransomware locks the record system during an emergency: availability is broken.
Situation: an exam result portal is flooded with fake traffic on result day and no student can open it.
Nobody read secret data and nobody changed marks, so confidentiality and integrity are fine.
The service could not be used when it was needed.
Answer: Availability.
CIA in practice: trade-offs and the extra properties
Real systems cannot maximise all three properties at once, and interviewers like candidates who know this.
Strong protection for one property can hurt another. Five passwords to log in helps confidentiality but annoys genuine users. Good security finds a balance that fits the business.
| Strong control | Helps | Can hurt |
|---|---|---|
| Very short login timeout | Confidentiality | Availability (users get logged out often) |
| Many copies of data | Availability | Confidentiality (more places to leak) |
| Mandatory approval for every change | Integrity | Availability (slow fixes) |
Beyond CIA: properties you should also know
- Authentication: proving who you are (password, fingerprint, OTP).
- Authorisation: deciding what you are allowed to do after you prove who you are.
- Accounting / auditing: recording who did what and when, in logs.
- Non-repudiation: the sender cannot later deny sending something, usually achieved with digital signatures and logs.
Authentication, authorisation and accounting together are called AAA.
Ravi enters his employee ID, password and an OTP. This proves identity: authentication.
The HR system lets Ravi view his leave balance but not edit other people's records: authorisation.
The system writes "Ravi viewed leave balance at 10:42" to a log: accounting.
Keep going with the full course
Day 1 has 21 pages. You have read the first 3.
See what's inside →