CIA Triad and Core Security Concepts Every Beginner Must Know

Every security decision, from choosing a password policy to designing a data centre, rests on a small set of ideas. If you understand them deeply, new technologies stop looking mysterious: you simply ask the same questions in a new setting. This lesson covers the CIA triad, the AAA model, the difference between threats, vulnerabilities and risk, and the design principles that experienced professionals use daily.

The CIA Triad

The CIA triad is the foundation of information security. Each letter describes a property you want to protect.

PropertyMeaningThreat exampleControl example
ConfidentialityOnly authorised people can read the informationCustomer database leakedEncryption, access control
IntegrityInformation is accurate and has not been altered improperlyAttacker changes a bank transfer amountHashing, digital signatures, change control
AvailabilityInformation and systems are accessible when neededRansomware or DDoS takes a service offlineRedundancy, backups, DDoS protection

The three properties often pull against each other. Locking a system down tightly improves confidentiality but may reduce availability for legitimate users. Good security is a balance chosen according to what the business values most. A hospital emergency system prioritises availability; a classified research archive prioritises confidentiality; a financial ledger prioritises integrity.

Beyond CIA

Two further properties are often added. Authenticity means being able to verify that a person, system or message is genuine. Non-repudiation means someone cannot credibly deny an action they performed, which digital signatures and audit logs support.

AAA: Authentication, Authorisation and Accounting

  1. Authentication: proving who you are (password, token, biometric).
  2. Authorisation: deciding what you are allowed to do once identified.
  3. Accounting (auditing): recording what you did, so actions can be reviewed.

A simple example: at an office building you show your badge (authentication), the door opens only to floors you are permitted on (authorisation) and a log records your entries (accounting). Many real incidents involve a failure in just one of these three, for example a user who is properly authenticated but authorised to see far more than their job requires.

Authentication factors fall into three families: something you know (password), something you have (phone, hardware key) and something you are (fingerprint). Combining factors from different families is multi-factor authentication; see Password Security: Hashing, Salting, MFA and Passkeys.

Asset, Threat, Vulnerability, Risk

TermDefinitionExample
AssetAnything of value to protectCustomer database
ThreatA potential cause of harmA criminal group seeking stolen data
VulnerabilityA weakness that a threat can useUnpatched database server
ExploitA way of using a vulnerabilityCode that abuses the unpatched flaw
RiskThe likelihood and impact of a threat using a vulnerability against an assetHigh chance of breach with large financial and legal impact
Control (countermeasure)Something that reduces riskPatching, firewall rule, monitoring

A simple way to remember it: risk = threat × vulnerability × impact. If any factor is zero, risk is zero. This is why removing a vulnerability, reducing a threat or limiting impact are all valid ways to manage risk. The formal process is covered in Security Governance, Risk and Compliance.

Types of control

  • Preventive: stops an incident (firewall, MFA, door lock).
  • Detective: identifies an incident (log monitoring, intrusion detection, CCTV).
  • Corrective: fixes damage (restore from backup, patching).
  • Deterrent: discourages attackers (warning banners, visible cameras).
  • Compensating: an alternative when the ideal control is impossible.

Controls are also grouped as technical (software and hardware), administrative (policies and training) and physical (locks, guards).

Core Design Principles

Defence in depth

Use multiple layers so that if one fails, others still protect. For a web application: a web application firewall, input validation in code, least-privilege database accounts, encryption and monitoring. No single layer is expected to be perfect.

Least privilege

Give users, programs and systems only the access needed for their task, for only as long as needed. An accountant does not need administrator rights on servers; a web application does not need to own the database.

Separation of duties

Split critical tasks among several people so one person cannot misuse the process alone, such as one person raising a payment and another approving it.

Fail securely

When something breaks, the system should default to a safe state. If an authorisation service is unreachable, deny access instead of allowing it.

Keep it simple

Complexity creates bugs and misconfigurations. A simpler design is easier to review and secure.

Zero trust mindset

“Never trust, always verify”: no user or device is trusted merely because it is inside the network. See Zero Trust Architecture Explained.

Security by design and secure defaults

Build security in from the start, and ship products with the safest settings enabled by default, rather than expecting users to harden them afterwards.

Worked Example: Online Shop

Consider a small online shop. Assets: customer accounts, order history and payment tokens. Threats: credential stuffing, SQL injection, ransomware. Vulnerabilities: no rate limiting on login, an old plugin and a single unencrypted backup in the same building. A sensible mix of controls would be:

RiskControlTypeCIA property
Credential stuffingMFA, rate limiting, breached-password checksPreventiveConfidentiality
InjectionParameterised queries, WAFPreventiveConfidentiality, Integrity
Outdated pluginPatch management and vulnerability scanningPreventive, DetectiveAll three
RansomwareOffline encrypted backups, restore testsCorrectiveAvailability
Unnoticed intrusionCentral logging and alertsDetectiveAll three

Practice Exercises

  1. For each scenario, name the CIA property most affected: (a) a student changes their grade in the school database; (b) a website is unreachable due to a flood of traffic; (c) an employee emails a spreadsheet of salaries to the wrong person.
  2. Pick any app you use daily. List its assets, two threats and one vulnerability for each.
  3. Classify these as preventive, detective or corrective: door lock, CCTV, restoring from backup, antivirus blocking a file, audit log review.
  4. Explain in your own words why defence in depth is better than a single very strong control.

Suggested answers: 1(a) Integrity; 1(b) Availability; 1(c) Confidentiality. 3: preventive, detective, corrective, preventive, detective.

Mentor tip: When you are stuck on any security question, return to three questions: What are we protecting? From whom? What is the cheapest control that meaningfully reduces the risk? These questions solve more problems than any tool.

Educational use only: practise security techniques only on systems you own or have explicit written permission to test.

Key takeaways
  • CIA: confidentiality, integrity and availability are the properties we protect.
  • AAA: authenticate, authorise and account.
  • Risk comes from threats using vulnerabilities against assets, weighted by impact.
  • Layer preventive, detective and corrective controls: defence in depth.
  • Least privilege, separation of duties and secure defaults reduce damage when something fails.

Related Lessons