Browse Prior Art Database

Remote Enabling of System Security via a System Lock

IP.com Disclosure Number: IPCOM000019788D
Original Publication Date: 2003-Sep-29
Included in the Prior Art Database: 2003-Sep-29
Document File: 1 page(s) / 29K

Publishing Venue

IBM

Abstract

There is a need for system administrators or security personnel to have he ability to place all systems in a secure mode. This is when immediate action is required to protect data assets on the PCs Examples could be breach of physical security or building open for maintenance/janitors and/or normal procedure for after hours operation.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 71% of the total text.

Page 1 of 1

Remote Enabling of System Security via a System Lock

There is a need for system administrators or security personnel to have he ability to place all systems in a secure mode. This is when immediate action is required to protect data assets on the PCs Examples could be breach of physical security or building open for maintenance/janitors and/or normal procedure for after hours operation.

The invention is the creation of a network packet that is transmitted over wired and wireless LANs to each client. Upon receipt of the packet, the client device takes action to safe guard assets.

The invention is the creation of a network packet that is transmitted over wired and wireless LANs to each client. Upon receipt of the packet, the client device takes action to safe guard assets.

From a management console, the network admin or security personnel will send out a series of "action packets" The packets is sent periodically, to ensure that all systems receive the information. This provides protection to clients that missed the original packet due a variety of reasons: wireless client not associated, waking form power off state (Timer), or recently transported into area (Laptop). A packet of this type is received and decoded by the network chip (MAC) and forces the system management interrupt (SMI) to be generated (instead of PME as with WOL packets) BIOS code receives this SMI and determines the nature of the packet.

Security Concern: BIOS forces two things to happen: the loc...