Study guide

1.3 Information Security Fundamentals

EC-Council Certified Ethical Hacker CEH

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 CEH Exam Format, Cost & Eligibility 1.2 The Five Phases of Ethical Hacking 1.3 Information Security Fundamentals 1.4 Ethical Hacking Concepts, Scope & Legal Framework 1.5 The CEH Domains & Your Study Priority Map

2 Reconnaissance, Footprinting, Scanning & Enumeration

2.1 Footprinting & Reconnaissance Concepts 2.2 Footprinting Sources & Techniques 2.3 Network Scanning Concepts 2.4 Banner Grabbing, OS Fingerprinting & Scanning Beyond IDS/Firewall 2.5 Enumeration 2.6 Vulnerability Scanning & Countermeasures

3 Vulnerability Analysis & System Hacking Phases

3.1 Vulnerability Analysis Concepts 3.2 System Hacking Methodology Overview 3.3 Gaining Access: Password Attack Concepts 3.4 Privilege Escalation Concepts 3.5 Maintaining Access: Backdoors, Rootkits & Persistence 3.6 Covering Tracks, Anti-Forensics & Blue-Team Detection

4 Malware Threats, Sniffing & Social Engineering

4.1 Malware Concepts and Taxonomy 4.2 Malware Analysis and Detection 4.3 Sniffing Concepts and Layer 2 Attacks 4.4 Sniffing Countermeasures and Detection 4.5 Social Engineering Types and Human Psychology 4.6 Social Engineering and Insider Threat Defenses

5 Network & Perimeter Hacking

5.1 Denial of Service and DDoS Attacks 5.2 Session Hijacking 5.3 Evading IDS and IPS (Defensive Focus) 5.4 Evading Firewalls 5.5 Evading Honeypots and Defensive Deception 5.6 Network Security Controls and Architecture 5.7 Packet Analysis and Secure Protocols for Defenders

6 Web Server & Web Application Hacking

6.1 Web Server Attacks & Hardening 6.2 OWASP Top 10 Overview 6.3 Injection: SQL Injection & Command Injection 6.4 Cross-Site Scripting (XSS) & CSRF 6.5 Authentication, Session & Access-Control Flaws 6.6 API & Web App Security Testing Concepts

7 Wireless Network Hacking

7.1 Wireless Concepts and Standards 7.2 Wireless Encryption 7.3 Wireless Threats and Attack Concepts 7.4 Wireless Security Countermeasures

8 Mobile Platform, IoT & OT Hacking

8.1 Mobile Platform Threats & Security Models 8.2 Mobile Attack Vectors & Risks 8.3 Mobile Device Management & Enterprise Defense 8.4 IoT Hacking Concepts & Defense 8.5 OT, ICS & SCADA Security

9 Cloud Computing & Cryptography

9.1 Cloud Computing Concepts 9.2 Cloud Threats & Attack Surfaces 9.3 Cloud Security Controls 9.4 Cryptography Fundamentals 9.5 PKI & Cryptographic Applications 9.6 Cryptanalysis, Crypto Attacks & Best Practices

1.3 Information Security Fundamentals

Key Takeaways Explain This Topic AI

The CIA triad — Confidentiality, Integrity, Availability — is the model every CEH attack is measured against; many questions ask which element an attack violates

A threat is a potential danger, a vulnerability is a weakness, and risk is the likelihood and impact of a threat exploiting a vulnerability (Risk = Threat x Vulnerability x Impact, conceptually)

Hacker classes the exam tests: white/black/gray hat, script kiddie, hacktivist, state-sponsored, suicide hacker, and cyber terrorist

The Cyber Kill Chain (7 Lockheed Martin stages) and MITRE ATT&CK (tactics + techniques) are the two adversary models CEH expects you to recognize

Security controls are classified by function (preventive, detective, corrective, deterrent, compensating) and by type (administrative, technical, physical)

Last updated: June 2026

The CIA Triad

The CIA triad is the foundation of information security. Every attack in CEH can be mapped to which property it breaks:

Confidentiality — information is accessible only to authorized parties. Broken by data theft, eavesdropping/sniffing, shoulder surfing, or weak access control.

Integrity — information is accurate and unaltered except by authorized changes. Broken by tampering, man-in-the-middle modification, or unauthorized writes. Verified with hashing (MD5/SHA) and digital signatures.

Availability — systems and data are usable when needed. Broken by denial-of-service (DoS/DDoS), ransomware, or hardware/network failure.

Extensions you should recognize: Authenticity (the source is genuine) and Non-repudiation (a party cannot deny an action — provided by digital signatures and logging). Some frameworks add these to form a five-element model.

Exam tip: A DoS attack targets Availability , sniffing targets Confidentiality , and altering a record in transit targets Integrity . Map the attack to the broken property — this is one of the most common question patterns.

Threat vs. Vulnerability vs. Risk

These three terms are repeatedly tested as distractors. Keep them precise:

Term Definition Example

Threat A potential cause of an unwanted incident (the actor or event) A ransomware group, a malicious insider, a flood

Vulnerability A weakness that a threat can exploit An unpatched server, a weak password policy

Risk The likelihood and impact of a threat exploiting a vulnerability Probable downtime cost if ransomware hits that unpatched server

Exploit The actual technique/code that takes advantage of a vulnerability A Metasploit module for that CVE

Conceptually, Risk = Threat x Vulnerability x Impact . Removing the vulnerability (patching) or reducing impact (backups, segmentation) lowers risk even if the threat still exists — you usually cannot remove the threat itself. An asset is anything of value being protected; zero-day describes a vulnerability with no available patch.

Classes of Hackers and Threat Actors

CEH expects you to classify attackers by intent and authorization :

  • Type Intent / Authorization
  • White hat Authorized, ethical — security professionals and pen testers (the CEH role)
  • Black hat Malicious, unauthorized — criminals seeking profit, theft, or damage

Gray hat In-between — acts without authorization but not for clear malice (e.g., reports a flaw they found while poking around)

  • Script kiddie Unskilled, uses prebuilt tools/exploits they don't understand
  • Hacktivist Politically or socially motivated (defacement, leaks, DDoS)

State-sponsored / nation-state Government-backed espionage or sabotage; often an Advanced Persistent Threat (APT)

  • Suicide hacker Aims for impact regardless of getting caught or punished
  • Cyber terrorist Uses attacks to cause fear/harm for ideological ends

The defining line for ethical hacking is authorization , not technique — a white hat and a black hat may run the same Nmap scan, but only one has written permission.

Attack Vectors and the Attack Surface

An attack vector is the path or method used to reach a target — email phishing, an exposed web app, a malicious USB, or a supply-chain component.

The attack surface is the sum of all points where an unauthorized user could try to enter or extract data. Reducing it (closing ports, removing unused services, least privilege) is a core defensive goal.

Attack categories the exam expects: passive (eavesdropping, traffic analysis — no modification), active (modification, injection, DoS), close-in (physical proximity), insider (authorized misuse), and distribution (tampering with hardware/software before delivery).

Adversary Models: Cyber Kill Chain and MITRE ATT&CK

CEH tests two complementary adversary models.

Cyber Kill Chain (Lockheed Martin)

The Cyber Kill Chain models an intrusion as seven sequential stages : Reconnaissance, Weaponization, Delivery, Exploitation, Installation, Command and Control (C2), and Actions on Objectives . Breaking any single link disrupts the whole attack, which is why it is used to argue for layered defense — for example, blocking malicious email at Delivery stops the chain before Exploitation .

MITRE ATT&CK

MITRE ATT&CK (Adversarial Tactics, Techniques, and Common Knowledge) is a continuously updated knowledge base of real-world attacker behavior. It is organized into tactics (the adversary's goal , e.g., Initial Access, Persistence, Exfiltration) and techniques (the how , each with a T-number such as T1566 Phishing). Unlike the linear kill chain, ATT&CK is a behavior matrix that blue teams use to map detection coverage and to drive threat-hunting. CEH wants you to know it is behavior-based and complementary to the kill chain — not a replacement for it.

Defense-in-Depth

Loading diagram... Defense-in-Depth Layers

Defense-in-depth layers independent controls so a single failure does not cause full compromise. Think of concentric rings from policy at the outside to the protected asset at the core, as above.

Classifying Security Controls

CEH expects you to classify controls two ways at once — by function and by type:

By function:

  • Preventive — stop an incident (firewall rules, MFA, encryption, patching)
  • Detective — discover an incident (IDS/IPS, SIEM, log monitoring, audits)
  • Corrective — recover after an incident (backups, restore, incident response)
  • Deterrent — discourage (warning banners, visible cameras)
  • Compensating — substitute when a primary control isn't feasible

By type:

  • Administrative — policies, training, background checks, procedures
  • Technical (logical) — software/hardware: ACLs, encryption, IDS, MFA
  • Physical — locks, guards, cameras, mantraps, biometric doors

Exam tip: Map the scenario to both axes. A SIEM that alerts is detective + technical ; a backup that restores is corrective + technical ; security-awareness training is preventive + administrative ; a guard at the door is preventive + physical .