For autonomous vehicle security, which two architectural controls should you consider? (Choose two.)

Treating every microservice call between on-vehicle modules as untrusted implements a zero-trust security model. This is crucial for autonomous vehicles because it assumes that internal networks can be compromised, requiring strict authentication and authorization for all communications, even between internal components. This prevents an attacker who gains access to one module from easily compromising others. Using a Trusted Platform Module (TPM) and verifying firmware and binaries at boot ensures the integrity of the vehicle's software stack. A TPM provides a hardware-based root of trust, allowing the system to cryptographically verify that the bootloader, operating system, and application firmware have not been tampered with before execution. This protects against malicious code injection and ensures the vehicle operates with its intended, secure software. IPv6, functional programming languages, multiple connectivity subsystems, and Faraday cages are not primary architectural security controls for the software and communication aspects of autonomous vehicle security. While some might offer peripheral benefits, they don't address the core security challenges of inter-module communication trust and software integrity as directly and effectively as zero-trust and TPMs.