For us it is currently resolved with a workaround of updating Sophos to
- 2025.2.3.32.2-MR5 core
- 2025.2.3.9.3-MR5 intercept
and also adding exclusions to the Quartus bin64 executables folder. Specifically:
- Add a Process Exclusion
- Add a File/Folder Exclusion
- Add an Exploit Mitigation Exclusion for the process and path
The form of the exception entry is also sensitive, and works with (for example)
D:\intelFPGA_pro\24.1\quartus\bin64\*.exe but not D:\intelFPGA_pro\24.1\quartus\bin64\*
Sophos has not said whether the exceptions are permanent or whether they will work to resolve the underlying false detections related to Quartus.