Study guide

8.1 Mobile Platform Threats & Security Models

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

8.1 Mobile Platform Threats & Security Models

Key Takeaways Explain This Topic AI

The OWASP Mobile Top 10 2024 leads with M1 Improper Credential Usage and M2 Inadequate Supply Chain Security — its first major revision since 2016

Android uses an open ecosystem with sideloading and a permissive review pipeline, while iOS uses a closed, single-store, hardware-rooted model

App sandboxing isolates each app's data and processes so a compromised app cannot freely read another app's storage by default

Runtime permission models (Android 6+, iOS) force per-resource consent, but over-permissioned apps remain a top CEH-tested weakness

iOS jailbreaking and Android rooting both destroy the platform trust model by breaking the sandbox and code-signing guarantees

Last updated: June 2026

Why Mobile Security Is on the CEH Exam

The Mobile Platform, IoT, and OT Hacking domain is roughly 10% of the CEH v13 blueprint and one of the most testable on this domain. Mobile devices hold credentials, OAuth tokens, corporate email, and synced files, yet they live outside the traditional network perimeter and roam across untrusted Wi-Fi and cellular networks. The exam expects you to reason about which weakness class applies to a described scenario and what defensive control mitigates it — not to perform live exploitation. Treat every item below as authorized, defensive knowledge: you are learning the attack surface in order to harden it.

The mobile attack surface spans four areas you should be able to name: the device (storage, OS integrity, lock screen), the application (code, permissions, local data), the network (transport security, Wi-Fi), and the server/back-end (APIs the app calls). A weakness in any one of these can compromise the others — for example, a plaintext token on the device (app/device) can be replayed against the back-end (server).

OWASP Mobile Top 10 (2024) — Conceptual

The Open Worldwide Application Security Project (OWASP) publishes a Mobile Top 10. The 2024 release is the first major revision since 2016 and deliberately reorders the list around credentials and the software supply chain, reflecting how real-world breaches actually begin.

  • ID Risk (2024) Plain-language meaning
  • M1 Improper Credential Usage Hardcoded keys, reused tokens, credentials in source or logs
  • M2 Inadequate Supply Chain Security Compromised SDKs, third-party libraries, or build pipeline
  • M3 Insecure Authentication/Authorization Weak login, missing server-side authorization checks
  • M4 Insufficient Input/Output Validation Unvalidated data into the app or its backend
  • M5 Insecure Communication Missing or weak Transport Layer Security (TLS)
  • M6 Inadequate Privacy Controls Excess collection or leakage of personal data
  • M7 Insufficient Binary Protections No anti-tamper, no obfuscation, easy reverse engineering
  • M8 Security Misconfiguration Insecure defaults, debug enabled, exported components
  • M9 Insecure Data Storage Sensitive data in plaintext on the device
  • M10 Insufficient Cryptography Weak algorithms or poor key management

Note the shift: the 2016 list led with Improper Platform Usage ; the 2024 list elevates credentials (M1) and supply chain (M2) . M3 in 2024 also merges the old separate Insecure Authentication and Insecure Authorization items. A common exam trap is confusing M5 Insecure Communication (data in transit , a TLS problem) with M9 Insecure Data Storage (data at rest , a storage problem) — read the scenario for where the data lives.

Android vs iOS Security Models

The two dominant platforms make different trust trade-offs. Knowing the difference lets you predict which attack vector a scenario implies and which defense fits.

  • Dimension Android iOS
  • Ecosystem Open; multiple stores; sideloading allowed Closed; single official store; sideloading restricted
  • App review Automated + policy review; more permissive Stricter human + automated review
  • Isolation Per-app Linux user ID (UID) sandbox Per-app sandbox enforced by the OS
  • Code signing Developer self-signed certificates accepted Apple-issued signing required to run

Hardware root of trust Varies by Original Equipment Manufacturer (OEM); Trusted Execution Environment / StrongBox Secure Enclave on supported devices

  • Update control Often OEM/carrier dependent ( fragmentation ) Vendor-controlled, broad and fast
  • Privilege bypass Rooting Jailbreaking

Key exam idea: Android's open model historically faces a larger malware surface mainly because of sideloading and ecosystem fragmentation (slow, inconsistent patching), not because the Linux kernel is weaker or lacks isolation. iOS reduces malware exposure through a curated store and mandatory signing, but a jailbroken iOS device discards those protections and is no safer than an unmanaged Android.

App Sandboxing

App sandboxing confines each application's code and data so that, by default, one app cannot read another app's private storage or interfere with its processes. On Android, each app typically runs under its own UID with a private data directory; on iOS, the OS enforces a per-app container. Sandboxing is a containment control: it limits blast radius if one app is malicious or compromised. It does not stop a user from granting an app excessive permissions, and it is weakened or broken entirely once the device is rooted/jailbroken.

Permission Models and Code Signing

Modern Android (6.0+) and iOS use runtime permissions : the user is prompted to allow access to a sensitive resource (location, camera, contacts, microphone) at the moment it is first needed, and can revoke it later in settings. The recurring CEH weakness is over-permissioning — an app requests far more access than its declared function requires (a flashlight asking for SMS and contacts). The defensive principle is least privilege ; app-vetting tools and Mobile Threat Defense agents flag permission scope that does not match declared functionality.

Code signing binds an app to a verifiable author and guarantees the binary has not been tampered with since signing. iOS requires Apple-issued signing to launch any app; Android accepts developer self-signed certificates, which is more flexible but means signing alone proves continuity of authorship, not trustworthiness. Both models collapse on a rooted/jailbroken device, which is why root/jailbreak detection is a baseline control for any app that handles sensitive data.