Modern computing platforms increasingly need to host critical workloads that require strong security guarantees. Trusted Execution Environments (TEEs) provide such guarantees. They isolate applications from untrusted components such as the operating system or hypervisor. A small Security Monitor (SM), assumed to be trusted by the entire platform, executes alongside the platform firmware and manages TEEs by configuring hardware-based memory isolation. However, current firmware stacks are large and include a variety of device drivers and management logic in addition to TEE functionality. This significantly increases the Trusted Computing Base (TCB) and, with it, the risk of vulnerabilities. To address this issue, recent research has explored several directions, such as developing firmware components in memory-safe languages like Rust, applying formal verification techniques, or changing firmware designs to reduce complexity.