Security surveillance system and security surveillance method

Abstract

A security surveillance system for a mobile device with a wireless interface and a control unit that is connected to the wireless interface comprises a security controller that is coupled to the wireless interface and that inspects at least data traffic incoming via the wireless interface at the mobile device according to a number, i.e. one or more, of predefined data rules, wherein the security controller generates a warning signal if the data traffic violates one of the predefined data rules, and a warning indicator that is coupled to the security controller and that generates a warning indication based on the warning signal.

Claims

1. A security surveillance system for a mobile device with a wireless interface and a control unit that is connected to the wireless interface and that controls further elements of the mobile device based on wireless data traffic received by the wireless interface, the security surveillance system comprising: a security controller included in the mobile device, wherein the security controller is implemented as a dedicated device and the security controller is coupled to the wireless interface, and the security controller receives the data traffic provided to the control unit and inspects at least the received data traffic incoming via the wireless interface at the mobile device according to a number of predefined data rules, wherein the security controller generates a warning signal if the data traffic violates one of the predefined data rules, and a warning indicator that is coupled to the security controller and that generates a warning indication based on the warning signal, wherein the security controller comprises a virtual machine with a dedicated processing device for emulating hardware of the control unit, said virtual machine executes at least part of an operating system that is in parallel executed by the control unit of the mobile device, and wherein the security controller comprises a behavior monitor that is arranged external to the virtual machine, and configured to inspect and monitor a behavior of software executed in the virtual machine in view of the received data traffic incoming via the wireless interface, wherein the security controller is arranged between an RF circuit of the wireless interface and a digital interface of the wireless interface such as to intercept the data traffic before it arrives at the digital interface of the wireless interface, and wherein the security controller comprises an analog-to-digital converter for coupling the security controller to the RF circuit, a digital analysis circuity coupled between the RF circuit and the digital interface to analyze the digitized data traffic such to controllably block data traffic that violates one of the predefined data rules, and a digital-to-analog converter to provide an analog signal received from the RF circuit to the digital interface of the wireless interface, wherein the security surveillance system further comprises an external network emulator that emulates a communication network and controllably transmits data traffic to the mobile device that violates at least one of the data rules.

2. The security surveillance system of claim 1, wherein the security controller comprises a computer program that is executed by the control unit of the mobile device.

3. The security surveillance system of claim 2, wherein the security controller comprises a hardware driver for the wireless interface for an operating system of the control unit of the mobile device.

4. The security surveillance system of claim 2, wherein the security controller comprises a communication stack function of a communication software stack of an operating system of the control unit of the mobile device.

5. The security surveillance system of claim 1, wherein the virtual machine is provided in the control unit.

6. The security surveillance system of claim 1, wherein the security controller comprises a configuration interface for receiving data rules, and a configuration memory for storing the received data rules.

7. A security surveillance method for a mobile device with a wireless interface and a control unit that is connected to the wireless interface and that controls further elements of the mobile device based on wireless data traffic received by the wireless interface, the security surveillance method comprising: receiving the data traffic provided to the control unit by a security controller, inspecting, by the security controller, at least the received data traffic incoming via the wireless interface at the mobile device according to a number of predefined data rules with a security controller that is coupled to the wireless interface, and generating a warning signal with the security controller if the data traffic violates one of the predefined data rules, wherein the security surveillance method is executed in the mobile device, wherein the security controller is implemented as a dedicated device, wherein the security controller is arranged between an RF circuit of the wireless interface and a digital interface of the wireless interface such as to intercept the data traffic before it arrives at the digital interface of the wireless interface, and wherein the security controller comprises an analog-to-digital converter for coupling the security controller to the RF circuit, a digital analysis circuity coupled between the RF circuit and the digital interface to analyze the digitized data traffic such to controllably block data traffic that violates one of the predefined data rules, and a digital-to-analog converter to provide an analog signal received from the RF circuit to the digital interface of the wireless interface; wherein a virtual machine comprises a dedicated processing device for emulating hardware of the control unit, said virtual machine executes at least part of an operating system that is in parallel executed by the control unit of the mobile device implements the functionality of the security controller, and wherein a behavior monitor of the security controller that is arranged external to the virtual machine inspects and monitors a behavior of software executed in the virtual machine in view of the received data traffic incoming via the wireless interface, wherein the security surveillance method further comprises emulating a communication network and controllably transmitting data traffic to the mobile device that violates at least one of the data rules.

8. The security surveillance method of claim 7, wherein the control unit of the mobile device executes a computer program that implements the functionality of the security controller.

9. The security surveillance method of claim 8, wherein a hardware driver for the wireless interface for an operating system of the control unit of the mobile device implements the functionality of the security controller.

10. The security surveillance method of claim 8, wherein the security controller is implemented by a communication stack function of a communication software stack of an operating system of the control unit of the mobile device.

11. The security surveillance method of claim 7, wherein the virtual machine is provided in the control unit.

12. The security surveillance method of claim 7, wherein the security controller comprises a configuration interface for receiving data rules, and a configuration memory for storing the received data rules.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) For a more complete understanding of the present invention and advantages thereof, reference is now made to the following description taken in conjunction with the accompanying drawings. The invention is explained in more detail below using exemplary embodiments which are specified in the schematic figures of the drawings, in which:

(2) FIG. 1 shows a block diagram of an embodiment of a security surveillance system according to the present invention;

(3) FIG. 2 shows a flow diagram of an embodiment of a security surveillance method according to the present invention;

(4) FIG. 3 shows a block diagram of another embodiment of a security surveillance system according to the present invention;

(5) FIG. 4 shows a block diagram of another embodiment of a security surveillance system according to the present invention;

(6) FIG. 5 shows a block diagram of another embodiment of a security surveillance system according to the present invention; and

(7) FIG. 6 shows a block diagram of another embodiment of a security surveillance system according to the present invention.

(8) The appended drawings are intended to provide further understanding of the embodiments of the invention. They illustrate embodiments and, in conjunction with the description, help to explain principles and concepts of the invention. Other embodiments and many of the advantages mentioned become apparent in view of the drawings. The elements in the drawings are not necessarily shown to scale.

(9) In the drawings, like, functionally equivalent and identically operating elements, features and components are provided with like reference signs in each case, unless stated otherwise.

DETAILED DESCRIPTION OF THE DRAWINGS

(10) FIG. 1 shows a block diagram of a security surveillance system 100 for a mobile device 101. The mobile device 101 comprises a wireless interface 102 and a control unit 103. The mobile device 101 receives wireless data traffic 104 via the wireless interface 102. The wireless interface 102 provides the data traffic 104 to the control unit 103 for further processing.

(11) The control unit 103 may be seen as the central processing unit of the mobile device 101 that e.g. executes an operating system software for the mobile device 101 and controls further elements of the mobile device 101. Although not explicitly shown, such further elements may e.g. comprise a user interface like a touch screen, input devices like e.g. buttons, and output devices like e.g. LEDs, speakers and the like. It is understood, that further elements may be present in the mobile device 101, like e.g. data memories coupled to the control unit 103 that store e.g. the instructions that form the operating system, driver circuits and the like. It is understood, that the control unit 103 may e.g. comprise a processor and respective peripherals, like e.g. an energy supply, memory elements, peripheral controllers and the like. The control unit 103 may also comprise a system-on-chip that comprises the necessary elements on a single chip.

(12) The security surveillance system 100 comprises the security controller 105 that is coupled to the wireless interface 102 and a warning indicator 109.

(13) During normal operation, the security controller 105 receives the data traffic 104 that is also provided to the control unit 103. It is understood, that although in the security surveillance system 100 the data traffic 104 is provided to the control unit 103 and the security controller 105 in parallel, the data traffic 104 may also be provided first to the security controller 105 and from the security controller 105 to the control unit 103.

(14) The security controller 105 comprises a verification logic 107 that verifies if the data traffic 104 matches at least one of a number of predefined data rules 106. As indicated above, the data rules 106 may either be positive or negative data rules. For processing of the single data rules 106 the verification logic 107 may e.g. comprise one or more state machines. Such state machines may each implement a respective data rule 106. As alternative the data rules 106 may be provided as a description that may be parsed by a respective state machine. It is understood, that the verification logic 107 may also be implemented in any other adequate form. The verification logic 107 may e.g. be implemented in hardware, especially in a configurable logic device, like e.g. a FPGA or a CPLD, or as an ASIC, or in software or as a combination of both.

(15) In case that the data traffic 104 matches one of the data rules 106, the security controller 105, e.g. the verification logic 107, generates a warning signal 108. The warning signal 108 is then provided to the warning indicator 109. The warning indicator 109 then generates a respective warning indication 110. The warning indication 110 may e.g. be a flashing light or a buzzing sound or the like, that may be perceived by the user. The warning indicator 109 may comprise a respective driver.

(16) As alternative, the warning indicator 109 may e.g. be a software component of an operating system that is executed on the control unit 103. Such a warning indicator 109 may then e.g. generate a modal dialog that overlays the main display to indicate to the user that a potentially harmful data traffic 104 was received. The modal dialog may allow a user to accept or discard the respective data traffic 104.

(17) For sake of clarity in the following description of the method based FIG. 2 the reference signs used in the description of the apparatus based figures will be maintained.

(18) FIG. 2 shows a flow diagram of an embodiment of a security surveillance method for a mobile device 101, 201, 301, 401, 501 with a wireless interface 102, 202, 302, 402, 502 and a control unit 103, 203, 303, 403, 503 that is connected to the wireless interface 102, 202, 302, 402, 502.

(19) The security surveillance method comprises inspecting at least data traffic 104, 204, 304, 404, 504 incoming via the wireless interface 102, 202, 302, 402, 502 at the mobile device 101, 201, 301, 401, 501 according to a number of predefined data rules 106, 206, 306, 506 with a security controller 105, 205, 305, 405, 505 that is coupled to the wireless interface 102, 202, 302, 402, 502, and generating a warning signal 108, 208, 308, 408, 508 with the security controller 105, 205, 305, 405, 505 if the data traffic 104, 204, 304, 404, 504 violates one of the predefined data rules 106, 206, 306, 506.

(20) If data traffic 104, 204, 304, 404, 504 violates one of the predefined data rules 106, 206, 306, 506 it may in addition to generating the warning indication 110, 210, 310, 510 also be controllably blocked by the security controller 105, 205, 305, 405, 505.

(21) The control unit 103, 203, 303, 403, 503 of the mobile device 101, 201, 301, 401, 501 may e.g. execute a computer program that implements the functionality of the security controller 105, 205, 305, 405, 505. The computer program may e.g. be a user space application 215, 315 that implements the functionality of the security controller 105, 205, 305, 405, 505 and is executed by an operating system of the control unit 103, 203, 303, 403, 503 of the mobile device 101, 201, 301, 401, 501. As an alternative, the computer program may e.g. be a hardware driver for the wireless interface 102, 202, 302, 402, 502 for an operating system of the control unit 103, 203, 303, 403, 503 of the mobile device 101, 201, 301, 401, 501 that implements the functionality of the security controller 105, 205, 305, 405, 505. As further, alternative the security controller 105, 205, 305, 405, 505 may be implemented by a communication stack function of a communication software stack of an operating system of the control unit 103, 203, 303, 403, 503 of the mobile device 101, 201, 301, 401, 501. It is further possible, to distribute the functionality of the security controller 105, 205, 305, 405, 505 in different components of the operating system.

(22) At least part of the functionality of the security controller 105, 205, 305, 405, 505 may also be implemented by a virtual machine 318 that executes at least part of an operating system that is in parallel executed by the control unit 103, 203, 303, 403, 503 of the mobile device 101, 201, 301, 401, 501. The part of the operating system that is executed by the virtual machine 318 may e.g. be a part of the communication stack of the operating system.

(23) The virtual machine 318 may be implemented on a dedicated processing unit. As alternative, the virtual machine 318 may be provided in the control unit 103, 203, 303, 403, 503.

(24) The security controller 105, 205, 305, 405, 505 may also comprise digital analysis circuitry 107, 207, 307, 507 that is coupled between a RF circuit of the wireless interface 102, 202, 302, 402, 502 and digital circuitry of the wireless interface 102, 202, 302, 402, 502 or the control unit 103, 203, 303, 403, 503 of the mobile device 101, 201, 301, 401, 501.

(25) The security surveillance method may further comprise emulating a communication network and controllably transmitting data traffic 104, 204, 304, 404, 504 to the mobile device 101, 201, 301, 401, 501 that violates at least one of the data rules 106, 206, 306, 506 with an external network emulator 530.

(26) Finally, the security controller 105, 205, 305, 405, 505 may comprise a configuration interface for receiving data rules 106, 206, 306, 506, and a configuration memory for storing the received data rules 106, 206, 306, 506.

(27) FIG. 3 shows a block diagram of a security surveillance system 200. The security surveillance system 200 is based on the security surveillance system 100. However, in the security surveillance system 200 the security controller 205 is implemented as a software component 205 that is executed by the control unit 203 of the mobile device 201. The data traffic 204 may therefore be directly provided from the wireless interface 202 to the control unit 203, where the data traffic 204 is provided to the security controller 205.

(28) Although not explicitly shown, it is understood, that the control unit 203 may comprise an operating system that executes the security controller 205 as an application, e.g. a user space application. It is however understood, that the security controller 205 may also be implemented in the operating system e.g. as a hardware driver of the operating system or as a component of a communication stack in the operating system. It can be seen, that the control unit 203, or the operating system, may also execute further applications 215.

(29) FIG. 4 shows a block diagram of another security surveillance system 300. The security surveillance system 300 is based on the security surveillance system 200. In contrast to the security surveillance system 200, the security surveillance system 300 implements the security controller 305 inside of a virtual machine 318. The virtual machine 318 is shown as being executed inside of the control unit 303. This means, that the control unit 303 may e.g. comprise a dedicated processing core for executing the virtual machine 318. As an alternative, the control unit 303 may execute the virtual machine 318 as an application within the operating system of the control unit 303.

(30) It is understood, that the virtual machine 318 may also be implemented on a dedicated processing device. This implementation totally separates the virtual machine 318 from the control unit 303. Security is therefore increased, because the data traffic 304 is analysed in the dedicated processing device and may not directly try to attack the control unit 303.

(31) FIG. 5 shows a block diagram of another security surveillance system 400. In the security surveillance system 400 the security controller 405 is implemented as dedicated device, e.g. as ASIC, FPGA or the like, that is connected between the wireless interface 402 and the control unit 403. The wireless interface 402 comprises an antenna 420 that receives the data traffic 404 and a communication controller 421 that processes the incoming wireless signals of the data traffic 404.

(32) The security controller 405 may intercept the data traffic 404 that is provided from the communication controller 421 to the control unit 403. This means that the security controller 405 may analyze the control unit 403 according to the data rules prior to forwarding the data traffic 404 to the control unit 403. This arrangement allows the security controller 405 to provide the warning signal 408 to the control unit 403 prior to forwarding potentially harmful data traffic 404 to the processing unit 403. The processing unit 403 may e.g. ask a user if the data traffic 404 should be forwarded or not and instruct the security controller 405 accordingly.

(33) In the security surveillance system 400 the security controller 405 is arranged between the communication controller 421 and the security controller 405. It is however understood, that the security controller 405 may also be arranged between the antenna 420 and the communication controller 421. In this case the security controller 405 may comprise respective converters that allow the security controller 405 to process the analog signals that are received by the antenna 420.

(34) FIG. 6 shows a block diagram of an embodiment of a security surveillance system 500. The security surveillance system 500 comprises an exemplary mobile device 501 as it is also shown in FIG. 1. It is understood, that any other embodiment of the mobile device according to the present invention may be used. Further, the security surveillance system 500 comprises a network emulator 530 with an antenna 531 for emitting data traffic 504. The network emulator 530 may e.g. emit data traffic 504 that emulates a malicious data source and provides data traffic 504 that violates at least one of the predefined data rules.

(35) The combination of the security controller 505 in the mobile device 501 and the network emulator 530 allows performing extensive testing of the functionality of the mobile device 501 and the security controller 505.

(36) It is for example possible to provide data traffic 504 that specifically triggers the warning signal 508 for specific data rules. It may then be verified if the mobile device 501 provides the respective warning indication 510.

(37) Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that a variety of alternate and/or equivalent implementations exist. It should be appreciated that the exemplary embodiment or exemplary embodiments are only examples, and are not intended to limit the scope, applicability, or configuration in any way. Rather, the foregoing summary and detailed description will provide those skilled in the art with a convenient road map for implementing at least one exemplary embodiment, it being understood that various changes may be made in the function and arrangement of elements described in an exemplary embodiment without departing from the scope as set forth in the appended claims and their legal equivalents. Generally, this application is intended to cover any adaptations or variations of the specific embodiments discussed herein.

(38) In the foregoing detailed description, various features are grouped together in one or more examples or examples for the purpose of streamlining the disclosure. It is understood that the above description is intended to be illustrative, and not restrictive. It is intended to cover all alternatives, modifications and equivalents as may be included within the scope of the invention. Many other examples will be apparent to one skilled in the art upon reviewing the above specification.

(39) Specific nomenclature used in the foregoing specification is used to provide a thorough understanding of the invention. However, it will be apparent to one skilled in the art in light of the specification provided herein that the specific details are not required in order to practice the invention. Thus, the foregoing descriptions of specific embodiments of the present invention are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed; obviously many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. Throughout the specification, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein,” respectively. Moreover, the terms “first,” “second,” and “third,” etc., are used merely as labels, and are not intended to impose numerical requirements on or to establish a certain ranking of importance of their objects.

LIST OF REFERENCE SIGNS

(40) 100, 200, 300, 400, 500 security surveillance system

(41) 101, 201, 301, 401, 501 mobile device

(42) 102, 202, 302, 402, 502 wireless interface

(43) 103, 203, 303, 403, 503 control unit

(44) 104, 204, 304, 404, 504 data traffic

(45) 105, 205, 305, 405, 505 security controller

(46) 106, 206, 306, 506 data rules

(47) 107, 207, 307, 507 verification logic

(48) 108, 208, 308, 408, 508 warning signal

(49) 109, 209, 309, 509 warning indicator

(50) 110, 210, 310, 510 warning indication

(51) 215, 315 application

(52) 318 virtual machine

(53) 420 antenna

(54) 421 communication controller

(55) 530 network emulator

(56) 531 antenna

(57) S1, S2 method steps