Battlefield 6dev apologizes for requiring Secure Boot to power anti-cheat tools

In a recent announcement, EA revealed that players participating in the open beta of Battlefield 6 on PC would need to enable Secure Boot in their Windows OS and BIOS settings. This requirement has stirred up considerable debate among gamers, particularly those struggling to configure the complex security feature or those hesitant to grant EA's anti-cheat tools kernel-level access to their systems. Christian Buhl, the technical director for Battlefield 6, addressed the issue in an interview with Eurogamer, describing the Secure Boot requirement as a necessary measure to combat cheating. He expressed regret that this stipulation might deter some players from enjoying the game. "I wish we didn't have to implement Secure Boot," Buhl stated. "It does prevent some players from engaging with the game, which is unfortunate. I wish everyone could have a seamless experience without these hurdles." Despite the implementation of Secure Boot, Buhl acknowledged that it would not completely eliminate cheating in Battlefield 6 over the long term. However, he emphasized that the Javelin anti-cheat tools, which operate through Secure Boot's low-level access, are among the most effective resources available to combat cheaters. "While nothing can completely eradicate cheating, enabling Secure Boot and obtaining kernel-level access significantly complicates cheating efforts and enhances our ability to detect and prevent them," he explained. In a previous post on a Steam forum, EA detailed that the Secure Boot requirement would grant them features that help counteract cheats attempting to infiltrate the game during the boot process. By leveraging the Trusted Platform Module on motherboards through Secure Boot, the anti-cheat team can monitor for various threats, including kernel-level cheats, rootkits, memory manipulation, injection spoofing, hardware ID manipulation, virtual machine usage, and tampering attempts against anti-cheat systems.