There is a bug with CIS on 1903 where CIS will log memory access being blocked where there is no memory access happening. It is a usability error; it’s not an error that has impact on functioning of programs nor is it a security risk.
CIS always has blocked memory access to its processes as part of how CIS protects its self. The blocking gets logged in HIPS logs.
Now with Blocked Applications this blocking is brought to the front and confuses people. Blocked Applications is not very informative and doesn’t inform about the nature of a block. It was probably introduced to make managing certain blocking actions easily visible and manageable. But Blocked Applications overplayed its hand by brining memory access to the front, offering to unblock memory access where it is not capable of doing so.
This freaks people where there is nothing to worry about. 99,9999% of the programs work normally when they don’t get memory access to CIS processes.