ICE
ICE (Continuous)
Default: Computer Hacking-2 or Expert (Computer Security).
Base Complexity: 3.
Intrusion Countermeasure Electronics deny unauthorized access to a network, computer, program, or data object.
ICE runs continuously, generally alongside a Listen program to grant access to those with the proper credentials. As long as it’s in effect, no program can be executed on the protected object without satisfying the Listen program or successfully Breaching the ICE, or Spoofing the gatekeeper Listen program.
An ICE program that has been successfully Breached is considered “off” until it’s restarted by a sysadmin or automated defense system (or a Blackhat covering his tracks); ICE that’s been Spoofed is still “on,” but has granted access to the Blackhat for the current session (until he disconnects from that computer). Highly secure systems often run several instances of ICE – one to restrict access to the computer itself, and others to protect critical programs, classified databases, etc. See Layered ICE.
ICE can allow some communication through. For example, a Listen program that’s functioning as gatekeeper for the ICE, or an Analyze or Search that’s reaching through the computer’s ICE to look around the network (or monitor the ICE), can still be Spoofed. ICE doesn’t prevent the protected object from being found in a Search, but it does prevent the object’s contents from being Altered, Controlled, Searched, or otherwise accessed. For example, a Search executed over a penetrated network can find an individual computer protected by its own ICE, but that ICE would have to be defeated before the computer could be Controlled, or a Search invoked to find a specific program or datum on it.
This is one of the Hacking Programs.
skill_defaults:: "Computer Hacking-2 or Expert (Computer Security)"
complexity:: 3