The present disclosure relates generally to device security and, more particularly, to a computer program controlled security mechanism.
Most computer systems (laptop, workstation, servers) allow free access to the systems internal area, where the motherboard, expansion cards, hard disk, memory, and other interfaces reside. This free access to the systems internal hardware area can result in computer parts theft or in unintended (or intended) damage to the system. Accordingly, such access should be regulated, restricted, or otherwise controlled in some manner.
In order to provide a better understanding, example embodiments will now be described in detail, by way of example only, with reference to the accompanying figures, in which:
Overview
An apparatus is provided in one example embodiment and includes a locking member configured to be coupled to a case that contacts an electronic component, the locking member being part of a security protocol having a secure mode and a disabled mode. The secure mode restricts access to the electronic component and the disabled mode provides access to the electronic component. A signal receiver is configured to be coupled to the locking member to electronically control the locking member in order to switch between the modes. In more specific embodiments, the signal receiver receives instructions for switching the modes from a remote device configured to be coupled to a network. The remote device receives a password from an end user seeking to switch to one of the modes and the remote device switches between the modes if the password is authenticated. The instructions can be provided by a software application being executed on the remote device. In yet other embodiments, the case includes a flap that can be opened in order to access internal space of the electronic component once the locking member has switched to the disabled mode.
As shown in
Returning to
The mode of security mechanism 30, at least in this embodiment, is determined by a computer program loaded and running on the operation components of device 10. The computer program provides a graphical user interface 38 to be displayed on a touch screen 40. In some embodiments, a keyboard and/or mouse forms part of the user interface, possibly instead of the touch screen. User interface 38 may be an administration interface built into device 10 by the devices manufacturer and usable only after a security protocol—such as the entry and authentication of a login and password—is successfully completed. Alternatively, user interface 38 may be provided by the devices Basic Input Basic Output (BIOS).
In one embodiment, a person 14 seeking access is a computer technician who knows or holds the relevant login and password. The owner or user of device 10 may not have the login and password. This lack of knowledge prevents the untrained owner or user attempting to modify or repair device 10. In another embodiment, the owner or user of device 10 does hold the relevant login and password. The password may correspond with the administrator's standard password on device 10. Access to operational components 28 may be controlled as per an organization's maintenance or support policy. For example, an owner or user 14 of device 10 may be given access to add or remove a card from expansion bus 24 but not to change CPU 16.
In some embodiments, a forced or unauthorized access will initiate a message or alert, such as a page or email, to a person or machine. The person may be an administrator. Device 10 may be configured to prevent unauthorized physical access to internal space 36. This may prevent access to the devices operational components 28. Theft of operation components may be thwarted and possible component damage may be prevented. The insertion of undesirable components into internal space 36, such as malignant operational components, may be prevented.
In an example deployment of device 10 shown in
The information provided to the agent by user 14 may be one of, for example: a maintenance contract certificate number; a password (as depicted); biometric data (e.g., a fingerprint, or voice recognition sample); or information provided to the user when purchasing of a new or additional operating component. This information confirms that user 14 is entitled to access to operational components 28 in the particular circumstances. In some embodiments, the agent may be an agent of the device manufacturer or maintenance provider. In one embodiment, remote device 42 includes a web server and the information is provided via a web browser or similar component running on device 10. In another embodiment, the communication between remote device 42 and device 10 is via a meeting application or a similar program.
In some circumstances it may be desirable to gain access to the internal space without having to use the program on device 10 to disable the security mechanism, these circumstances including: device 10 has crashed; the device cannot be powered; the program controlling the security does not work; and the device is still in the factory and requires further work before being shipped. To accommodate these and any other circumstances, device 10 has a manually operated actuator 60, whereby the secure mode is overridden by operating actuator 60 making the internal space accessible. In this embodiment, the actuator is operated by a key 62, which is configured to be coupled to actuator 60 (as is shown in
The security mechanism does not have to protect an internal space of device 10. In another embodiment shown in
Structure 72 may be arranged to cooperate with the device such that device 10 cannot be opened when mounted in the structure. In these embodiments, device 10 can only be opened once removed from structure 72. This may provide protection against unauthorized removal of the device and unauthorized access to any internal space of device 70.
In one example implementation, structure 72 may be a variant on the 19-inch rack standardized under EIA 310-D, IEC 60297 and DIN 41494 SC48D. The rack is for mounting various electronic modules in a “stack,” or rack, 19 inches (482.6 mm) wide. Equipment designed to be placed in a rack is typically described as rack-mount, a rack mounted system, a rack mount chassis, sub-rack, rack mountable, or occasionally, simply shelf. The slang expression for a sub rack (generally 1U=1.75 in=44.45 mm height) is “pizza box” due to the similarity in size and shape. Racks are typically found in data centers and computer rooms.
In an alternative embodiment shown in
In another embodiment shown in
Note that the remote device (or a local device) can include memory elements for storing information to be used in achieving the security activities, as outlined herein. Additionally, each of these devices may include a processor that can execute software or an algorithm to perform the security activities, as discussed in this Specification. This could be inclusive of software and/or algorithms that may be used to assist in controlling access to any protected electronic component. This can certainly include lookup functions, password authentication, reporting, login information, etc. These network elements may further keep information in any suitable random access memory (RAM), read only memory (ROM), erasable programmable ROM (EPROM), electronically erasable PROM (EEPROM), application specific integrated circuit (ASIC), software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs.
It is important to note that the steps in the preceding FIGURES illustrate only some of the possible scenarios that may be executed by, or within, the presented architecture. Some of these steps may be deleted or removed where appropriate, or these steps may be modified or changed considerably without departing from the scope of the described concept. In addition, a number of these operations have been described as being executed concurrently with, or in parallel to, one or more additional operations. However, the timing of these operations may be altered considerably. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by the proffered system in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the described concept.
Although the present invention has been described in detail with reference to particular embodiments, it should be understood that various other changes, substitutions, and alterations may be made hereto without departing from the spirit and scope of the present invention. The illustrated device and operations have only been offered for purposes of example and teaching. Suitable alternatives and substitutions are envisioned and contemplated by the present invention: such alternatives and substitutions being clearly within the broad scope of the proposed solutions. In addition, while the foregoing discussion has focused on laptop or personal computer security activities, any other suitable environment requiring the protection of important electronic components (e.g., server blades, database architectures, server farms, etc.) may benefit from the teachings provided herein. It should also be noted that the systems described may be constructed of any suitable combination of rubber, plastic, metal, or any other viable composition that could withstand and readily accommodate the forces as explained herein.
Although the described concept has been described in detail with reference to particular arrangements and configurations, these example configurations and arrangements may be changed significantly without departing from the scope of the described concept. For example, the lodging or securing mechanisms may include additional pins, cables, rods, bolts, etc. and virtually any other element that offers such a mechanism (or that can assist) for securing a device.
Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the described concept encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke paragraph six (6) of 35 U.S.C. section 112 as it exists on the date of the filing hereof unless the words “means for” or “step for” are specifically used in the particular claims; and (b) does not intend, by any statement in the specification, to limit this invention in any way that is not otherwise reflected in the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
4891503 | Jewell | Jan 1990 | A |
4920334 | DeVolpi | Apr 1990 | A |
5490200 | Snyder et al. | Feb 1996 | A |
5646605 | Leonaggeo et al. | Jul 1997 | A |
5712626 | Andreou et al. | Jan 1998 | A |
5740744 | Nashirozawa et al. | Apr 1998 | A |
5917407 | Squire et al. | Jun 1999 | A |
5925128 | Harmon | Jul 1999 | A |
6076385 | Pedroso et al. | Jun 2000 | A |
6192236 | Irvin | Feb 2001 | B1 |
6323782 | Stephens et al. | Nov 2001 | B1 |
6708879 | Hunt | Mar 2004 | B2 |
6731500 | Allirot | May 2004 | B2 |
6820562 | Zodnik et al. | Nov 2004 | B2 |
6885738 | White et al. | Apr 2005 | B2 |
6987441 | Roeland | Jan 2006 | B2 |
7176785 | Edogawa et al. | Feb 2007 | B2 |
7266849 | Gregory et al. | Sep 2007 | B1 |
7310158 | Nakao et al. | Dec 2007 | B2 |
7362227 | Kim | Apr 2008 | B2 |
7495543 | Denison et al. | Feb 2009 | B2 |
7847675 | Thyen et al. | Dec 2010 | B1 |
7898439 | Bettez et al. | Mar 2011 | B2 |
8239062 | Vahlberg et al. | Aug 2012 | B2 |
8471675 | Couto et al. | Jun 2013 | B2 |
20050088279 | Denison et al. | Apr 2005 | A1 |
20050285716 | Denison et al. | Dec 2005 | A1 |
20060145847 | Simpson et al. | Jul 2006 | A1 |
20070247276 | Murchison et al. | Oct 2007 | A1 |
20080036611 | Noblitt | Feb 2008 | A1 |
20080191867 | Markovich | Aug 2008 | A1 |
20090124376 | Kelly et al. | May 2009 | A1 |
20100283575 | Tubb et al. | Nov 2010 | A1 |
20110025459 | Denison et al. | Feb 2011 | A1 |
Number | Date | Country | |
---|---|---|---|
20100237987 A1 | Sep 2010 | US |