A: CIS will protect its self by denying programs to access CIS processes in memory.
In a nutshell:
- 99,999999% of the programs will work when access to CIS processes in memory is denied
- Memory access has always been logged in the background in the HIPS logs
- Blocked Applications brings memory access to the front which worries people
- Blocked application offers to unblock the blocking of memory access but can not deliver; that's a design flaw and causes people to worry even more
- 99,999999% of the programs work without getting access to CIS processes in memory
- Even though Blocked Application fails to allow memory access to CIS processes programs will work normally
In the end this is just a storm in a tea cup because of a usability issue. Programs will continue to function normally and there is no security risk. People get worried and think something is wrong even though programs are functioning normally and get freaked out when unblocking is not working.
The confusion shows that the decision to let Blocked Applications log memory access was a big mistake. Memory access should only be logged in the background in the HIPS logs only as it always has been. Information about memory access to CIS processes is only needed for 0,000001% of the programs.