Abstract: A countermeasure for a computer security threat to a computer system is administered by establishing a baseline identification of an operating or application system type and an operating or application system release level for the computer system that is compatible with a Threat Management Vector (TMV). A TMV is then received, including therein a first field that provides identification of at least one operating system type that is affected by a computer security threat, a second field that provides identification of an operating system release level for the operating system type, and a third field that provides identification of a set of possible countermeasures for an operating system type and an operating system release level. Countermeasures that are identified in the TMV are processed if the TMV identifies the operating system type and operating system release level for the computer system as being affected by the computer security threat.

Abstract: A countermeasure for a computer security threat to a computer system is administered by establishing a baseline identification of an operating or application system type and an operating or application system release level for the computer system that is compatible with a Threat Management Vector (TMV). A TMV is then received, including therein a first field that provides identification of at least one operating system type that is affected by a computer security threat, a second field that provides identification of an operating system release level for the operating system type, and a third field that provides identification of a set of possible countermeasures for an operating system type and an operating system release level. Countermeasures that are identified in the TMV are processed if the TMV identifies the operating system type and operating system release level for the computer system as being affected by the computer security threat.

Abstract: A countermeasure for a computer security threat to a computer system is administered by establishing a baseline identification of an operating or application system type and an operating or application system release level for the computer system that is compatible with a Threat Management Vector (TMV). A TMV is then received, including therein a first field that provides identification of at least one operating system type that is affected by a computer security threat, a second field that provides identification of an operating system release level for the operating system type, and a third field that provides identification of a set of possible countermeasures for an operating system type and an operating system release level. Countermeasures that are identified in the TMV are processed if the TMV identifies the operating system type and operating system release level for the computer system as being affected by the computer security threat.

Abstract: A threat management domain controller is responsive to a computer-actionable threat management vector that includes a first computer-readable field that provides identification of at least one system type that is affected by a computer security threat, a second computer-readable field that provides identification of a release level for the system type and a third computer-readable field that provides identification of a set of possible countermeasures for a system type and release level. The threat management domain controller processes a threat management vector that is received for use by a domain of target computer systems, and transmits the threat management vector that has been processed to at least one of the target computer systems in the domain of target computer systems.

Abstract: Under the present invention, a data networking protocol is applied over a power delivery network to manage an electrical device. In a typical embodiment, the data networking protocol is 802.1X. To this extent, the present invention utilizes different configurations of a location component/function, an identification component/function (also known in the art as a “supplicant function”), an authentication component/function, and an authentication server to authenticate and manage power delivery to the electrical device.

Abstract: The present invention provides a system and method for disabling an electrical device (e.g., that utilizes a data networking protocol such as 802.1X). Specifically, under the present invention, the electrical device is connected to a power socket of a power delivery network via a power bar. When disablement of a particular device is desired, the device is located by an authentication server (that communicates with the power bar over the power delivery network) using information stored in a devices information database. Once the particular device is located, an instruction to disable it is sent from the authentication server to a component, which then disables the device via the power bar.

Abstract: In general, the present invention provides a method and system for calibrating an electrical device that utilizes a data networking protocol (e.g., 802.1X) over a power delivery network. Specifically, the present invention leverages information gathered and stored during the authentication and operation of the electrical device to determine whether the electrical device should be calibrated. In general, the present invention makes this determination based on time elapsed since a previous calibration and/or cumulative usage of the device.