I love these cards, and this is not meant to be critical of their development.
Do you think in the interest of the KISS method of placement and development that creating cards for "Actions/software" vs./and the IC is the primary goal; with cards that list the systems that the IC is meant to protect created as general categories would be an excellent way to proceed? The suggestions that have been posted are fantastic and beautiful ideas. Many of them could be grouped under a single card say: Control Systems, Building Systems, Communication systems and so on. It is making the sub-categories listed on such a card the ones that can be grouped as such.
Giving the cards for the protected systems more general utility and not making them overly specific would keep a system layout on the table reasonably small. After all, once past the IC that protects a Hopper's control systems, you don't have to hack again to switch control to a different subsystem, i.e., going from the lift controls to unlocking the doors. It could allow for the subsystems to act more as prompts and not a direct list of the action that could be taken against/with those subsystems.
For example (using the previous replies)
Security (cameras, sensors, door locks)
disable, misfire, acquire new target)
Fuel Systems (Speed/throttle)
Environmental controls (windows/doors/AC/heater)
By creating just the general category of systems and the subsystems found within them, there is no need to list the specific "actions" that they can be used for when control is seized. They then act more like a creative prompt.