Mobile and Automotive Security
Stub. Smartphone security (app sandboxing/permission models, mobile-specific malware, baseband/radio attack surface) and automobile security (the in-vehicle CAN bus's lack of authentication, remote attack surfaces via cellular/Bluetooth/Wi-Fi, and the safety-critical stakes that make automotive security different from a typical IT system).
Two consumer cyber-physical platforms whose security models diverge from a general-purpose computer’s. Smartphones layer a permission-based sandbox on top of a conventional OS kernel, which mostly works but still admits mobile-specific malware and an expanded attack surface (baseband processors, radio stacks) beyond the application layer. Automobiles are a starker case: internally, many components communicate over the CAN bus, a broadcast network with no built-in authentication, so any compromised component (even one reached only through an ostensibly unrelated interface, like infotainment or cellular connectivity) can spoof messages from any other — and because these are safety-critical systems, a security failure here can mean physical harm, not just a data breach.
Outline (TODO — flesh out each)
- Smartphone sandboxing and permission models
- Mobile malware; baseband/radio attack surface
- The CAN bus and its lack of authentication
- Remote attack surfaces in modern vehicles
- Why automotive security is safety-critical