HARDWARE TAMPERING DETECTION

Abstract

An information handling system may include at least one processor, a plurality of physical sensors, and a firmware having instructions coded thereon that are executable by the at least one processor for: detecting, based on one or more of the physical sensors, a tampering event associated with the information handling system; and transmitting data regarding the tampering event to a central monitoring system.

Claims

1. An information handling system comprising: at least one processor; a plurality of physical sensors; and a firmware having instructions coded thereon that are executable by the at least one processor for: detecting, based on one or more of the physical sensors, a tampering event associated with the information handling system; and transmitting data regarding the tampering event to a central monitoring system.

2. The information handling system of claim 1, wherein the information handling system is a portion of a hyper-converged infrastructure (HCl) system.

3. The information handling system of claim 2, wherein the information handling system is an edge node of the HCl system.

4. The information handling system of claim 1, wherein the physical sensors include at least one sensor selected from the group comprising vibration sensors, accelerometers, temperature sensors, chassis opening sensors, and tilt sensors.

5. The information handling system of claim 1, further comprising at least one tamper-evident mechanism.

6. The information handling system of claim 5, wherein the tamper-evident mechanism is selected from the group consisting of seals and intrusion detection systems.

7. A method comprising: an information handling system detecting, via a plurality of physical sensors thereof, a tampering event associated with the information handling system; and the information handling system transmitting, via a firmware thereof, data regarding the tampering event to a central monitoring system.

8. The method of claim 7, wherein the information handling system is a portion of a hyper-converged infrastructure (HCl) system.

9. The method of claim 8, wherein the information handling system is an edge node of the HCl system.

10. The method of claim 7, wherein the physical sensors include at least one sensor selected from the group comprising vibration sensors, accelerometers, temperature sensors, chassis opening sensors, and tilt sensors.

11. The method of claim 7, wherein the information handling system includes at least one tamper-evident mechanism.

12. The method of claim 11, wherein the tamper-evident mechanism is selected from the group consisting of seals and intrusion detection systems.

13. An article of manufacture comprising a non-transitory, computer-readable medium having computer-executable instructions thereon that are executable by a processor of an information handling system for: detecting, via a plurality of physical sensors of the information handling system, a tampering event associated with the information handling system; and transmitting, via a firmware thereof, data regarding the tampering event to a central monitoring system.

14. The article of claim 13, wherein the information handling system is a portion of a hyper-converged infrastructure (HCl) system.

15. The article of claim 14, wherein the information handling system is an edge node of the HCl system.

16. The article of claim 13, wherein the physical sensors include at least one sensor selected from the group comprising vibration sensors, accelerometers, temperature sensors, chassis opening sensors, and tilt sensors.

17. The article of claim 13, wherein the information handling system includes at least one tamper-evident mechanism.

18. The article of claim 17, wherein the tamper-evident mechanism is selected from the group consisting of seals and intrusion detection systems.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] A more complete understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:

[0015] FIG. 1 illustrates a block diagram of an example information handling system, in accordance with embodiments of the present disclosure;

[0016] FIGS. 2-3 illustrate example architectures, in accordance with embodiments of the present disclosure; and

[0017] FIG. 4 illustrates a flow chart of an example method, in accordance with embodiments of the present disclosure.

DETAILED DESCRIPTION

[0018] Preferred embodiments and their advantages are best understood by reference to FIGS. 1 through 4, wherein like numbers are used to indicate like and corresponding parts.

[0019] For the purposes of this disclosure, the term information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an information handling system may be a personal computer, a personal digital assistant (PDA), a consumer electronic device, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include memory, one or more processing resources such as a central processing unit (CPU) or hardware or software control logic. Additional components of the information handling system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input/output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communication between the various hardware components.

[0020] For purposes of this disclosure, when two or more elements are referred to as coupled to one another, such term indicates that such two or more elements are in electronic communication or mechanical communication, as applicable, whether connected directly or indirectly, with or without intervening elements.

[0021] When two or more elements are referred to as coupleable to one another, such term indicates that they are capable of being coupled together.

[0022] For the purposes of this disclosure, the term computer-readable medium (e.g., transitory or non-transitory computer-readable medium) may include any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time. Computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape disk drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; communications media such as wires, optical fibers, microwaves, radio waves, and other electromagnetic and/or optical carriers; and/or any combination of the foregoing.

[0023] For the purposes of this disclosure, the term information handling resource may broadly refer to any component system, device, or apparatus of an information handling system, including without limitation processors, service processors, basic input/output systems, buses, memories, I/O devices and/or interfaces, storage resources, network interfaces, motherboards, and/or any other components and/or elements of an information handling system.

[0024] For the purposes of this disclosure, the term management controller may broadly refer to an information handling system that provides management functionality (typically out-of-band management functionality) to one or more other information handling systems. In some embodiments, a management controller may be (or may be an integral part of) a service processor, a baseboard management controller (BMC), a chassis management controller (CMC), or a remote access controller (e.g., a Dell Remote Access Controller (DRAC) or Integrated Dell Remote Access Controller (iDRAC)).

[0025] FIG. 1 illustrates a block diagram of an example information handling system 102, in accordance with embodiments of the present disclosure. In some embodiments, information handling system 102 may comprise a server chassis configured to house a plurality of servers or blades. In other embodiments, information handling system 102 may comprise a personal computer (e.g., a desktop computer, laptop computer, mobile computer, and/or notebook computer). In yet other embodiments, information handling system 102 may comprise a storage enclosure configured to house a plurality of physical disk drives and/or other computer-readable media for storing data (which may generally be referred to as physical storage resources). As shown in FIG. 1, information handling system 102 may comprise a processor 103, a memory 104 communicatively coupled to processor 103, a BIOS 105 (e.g., a UEFI BIOS) communicatively coupled to processor 103, a network interface 108 communicatively coupled to processor 103, and a management controller 112 communicatively coupled to processor 103.

[0026] In operation, processor 103, memory 104, BIOS 105, and network interface 108 may comprise at least a portion of a host system 98 of information handling system 102. In addition to the elements explicitly shown and described, information handling system 102 may include one or more other information handling resources.

[0027] Processor 103 may include any system, device, or apparatus configured to interpret and/or execute program instructions and/or process data, and may include, without limitation, a microprocessor, microcontroller, digital signal processor (DSP), application specific integrated circuit (ASIC), or any other digital or analog circuitry configured to interpret and/or execute program instructions and/or process data. In some embodiments, processor 103 may interpret and/or execute program instructions and/or process data stored in memory 104 and/or another component of information handling system 102.

[0028] Memory 104 may be communicatively coupled to processor 103 and may include any system, device, or apparatus configured to retain program instructions and/or data for a period of time (e.g., computer-readable media). Memory 104 may include RAM, EEPROM, a PCMCIA card, flash memory, magnetic storage, opto-magnetic storage, or any suitable selection and/or array of volatile or non-volatile memory that retains data after power to information handling system 102 is turned off.

[0029] As shown in FIG. 1, memory 104 may have stored thereon an operating system 106. Operating system 106 may comprise any program of executable instructions (or aggregation of programs of executable instructions) configured to manage and/or control the allocation and usage of hardware resources such as memory, processor time, disk space, and input and output devices, and provide an interface between such hardware resources and application programs hosted by operating system 106. In addition, operating system 106 may include all or a portion of a network stack for network communication via a network interface (e.g., network interface 108 for communication over a data network). Although operating system 106 is shown in FIG. 1 as stored in memory 104, in some embodiments operating system 106 may be stored in storage media accessible to processor 103, and active portions of operating system 106 may be transferred from such storage media to memory 104 for execution by processor 103.

[0030] Network interface 108 may comprise one or more suitable systems, apparatuses, or devices operable to serve as an interface between information handling system 102 and one or more other information handling systems via an in-band network. Network interface 108 may enable information handling system 102 to communicate using any suitable transmission protocol and/or standard. In these and other embodiments, network interface 108 may comprise a network interface card, or NIC. In these and other embodiments, network interface 108 may be enabled as a local area network (LAN)-on-motherboard (LOM) card.

[0031] Management controller 112 may be configured to provide management functionality for the management of information handling system 102. Such management may be made by management controller 112 even if information handling system 102 and/or host system 98 are powered off or powered to a standby state. Management controller 112 may include a processor 113, memory, and a network interface 118 separate from and physically isolated from network interface 108.

[0032] As shown in FIG. 1, processor 113 of management controller 112 may be communicatively coupled to processor 103. Such coupling may be via a Universal Serial Bus (USB), System Management Bus (SMBus), and/or one or more other communications channels.

[0033] Network interface 118 may be coupled to a management network, which may be separate from and physically isolated from the data network as shown. Network interface 118 of management controller 112 may comprise any suitable system, apparatus, or device operable to serve as an interface between management controller 112 and one or more other information handling systems via an out-of-band management network. Network interface 118 may enable management controller 112 to communicate using any suitable transmission protocol and/or standard. In these and other embodiments, network interface 118 may comprise a network interface card, or NIC. Network interface 118 may be the same type of device as network interface 108, or in other embodiments it may be a device of a different type.

[0034] As discussed above, embodiments of this disclosure provide improvements in the physical security of information handling system 102 by providing detection and alerts based on tampering. It should be noted that while the scenario of an edge deployment is discussed in detail herein for the sake of concreteness, other embodiments are also specifically contemplated within the scope of this disclosure.

[0035] FIG. 2 illustrates an example system for detecting and alerting against hardware tampering attempts on edge device 202. Physical sensors and tamper-evident mechanisms may be used to detect and notify an administrator about potential hardware tampering or unauthorized access, ensuring the integrity and security of the hardware components.

[0036] The tamper detection system may provide early detection of hardware tampering attempts on edge devices, and it may in some embodiments be implemented (in whole or in part) via firmware on edge devices to monitor physical sensors and detect tampering. The alerting mechanism may also store security events in a security database, which may be accessible via a management interface.

[0037] The device firmware may also establish communication between edge devices 202 and a central monitoring system configured to receive tampering alerts and analyze the data.

[0038] Embodiments may provide integration of physical sensors to monitor and detect physical indicators of tampering attempts. By leveraging physical sensors such as vibration sensors, accelerometers, temperature sensors, switches that actuate when a chassis panel is removed, tilt sensors, etc., the system can provide early detection of tampering events, enhancing the security of the hardware components.

[0039] Tamper-evident mechanisms such as seals, tamper-resistant screws, or special coatings on the edge devices may also be incorporated. These mechanisms help detect any physical changes or unauthorized access to the hardware components, providing an additional layer of security.

[0040] The firmware running on the edge devices may be implemented to monitor the physical sensors and detect tampering attempts. This may act as the first line of defense, continuously analyzing sensor data and triggering alerts when tampering events are detected.

[0041] The central monitoring system may receive tampering alerts from multiple edge devices. This central monitoring system then analyzes the data, determines the severity of tampering attempts, and provides a unified interface for managing and responding to these alerts.

[0042] A customizable alerting mechanism may promptly notify administrators about detected tampering attempts. The alerting mechanism can be tailored to different severity levels of tampering events, ensuring appropriate actions can be taken in response. For example, an accelerometer event may be classified as relatively low-severity, while a chassis opening event may be classified as higher-severity, etc.

[0043] Embodiments thus provide an integrated and proactive approach to detect and alert an administrator against hardware tampering attempts on edge devices. Embodiments provide early detection, enhanced security, and the ability to respond effectively to tampering events, safeguarding the integrity and security of the hardware components in edge computing environments. For example, in addition to sending alerts, some embodiments may also be operable to take additional remedial actions such as shutting down the edge system, encrypting data, etc.

[0044] FIG. 3 provides a high-level architecture diagram. As shown, edge device 302 includes physical sensors and tamper-evident mechanisms which are communicatively coupled to its firmware. The firmware is configured to communicate with central monitoring system 310, which provides an alerting mechanism that generates real-time alerts and notifies stakeholders, a management interface that allows monitoring/managing alerts and taking remedial actions, and a security database that stores alerts and security event logs.

[0045] This architecture ensures continuous monitoring, early detection, and swift response to tampering attempts. It safeguards edge devices and strengthens system security.

[0046] FIG. 4 provides a flow chart of an example method. As shown, the method may include a portion to be carried out at the edge device (shown on the left) and a portion to be carried out at the central monitoring system (shown on the right).

[0047] At step 402, the edge device firmware is initialized. Likewise, at step 414, the central monitoring system is initialized.

[0048] At step 404, the edge device may continuously or continually monitor its physical sensors for indicators such as vibration, acceleration, and temperature. The sensor data is captured at step 406 and transmitted to the edge device firmware. The edge device firmware analyzes the sensor data at step 408 for any tampering attempts.

[0049] If a tampering attempt is detected at step 410, the edge device firmware triggers an alert. Otherwise, the edge device's method loops back to step 404.

[0050] If an alert is generated at step 412, it is sent to the central monitoring system, which receives it at step 416 and stores it in the security database at step 418.

[0051] The alerting mechanism in the central monitoring system may then notify the relevant stakeholders (e.g., administrators and/or security personnel) about the tampering attempt at step 420.

[0052] The management interface may also allow security personnel to view and manage the tampering alerts at step 422. Remedial actions (e.g., prompted by the security personnel and/or undertaken autonomously) may occur at step 424 based on the severity of the tampering event. The central monitoring system then continuously monitors for new alerts and manages the security database.

[0053] One of ordinary skill in the art with the benefit of this disclosure will understand that the preferred initialization points for the method depicted in FIG. 4 and the order of the steps comprising the method may depend on the implementation chosen. In these and other embodiments, the method may be implemented as hardware, firmware, software, applications, functions, libraries, or other instructions. Further, although FIG. 4 discloses a particular number of steps to be taken with respect to the disclosed method, the method may be executed with greater or fewer steps than depicted. The method may be implemented using any of the various components disclosed herein (such as the components of FIG. 1), and/or any other system operable to implement the methods.

[0054] This disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the exemplary embodiments herein that a person having ordinary skill in the art would comprehend. Similarly, where appropriate, the appended claims encompass all changes, substitutions, variations, alterations, and modifications to the exemplary embodiments herein that a person having ordinary skill in the art would comprehend. Moreover, reference in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, or component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative.

[0055] Further, reciting in the appended claims that a structure is configured to or operable to perform one or more tasks is expressly intended not to invoke 35 U.S.C. 112(f) for that claim element. Accordingly, none of the claims in this application as filed are intended to be interpreted as having means-plus-function elements. Should Applicant wish to invoke 112(f) during prosecution, Applicant will recite claim elements using the means for [performing a function] construct.

[0056] All examples and conditional language recited herein are intended for pedagogical objects to aid the reader in understanding the invention and the concepts contributed by the inventor to furthering the art, and are construed as being without limitation to such specifically recited examples and conditions. Although embodiments of the present inventions have been described in detail, it should be understood that various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the disclosure.