Wearable secure data device

Abstract

A method for a wearable secure data device is disclosed. The method includes setting an operating mode of a wearable secure data device for storing a plurality of secure data items. The method also includes receiving a request for at least one secure data item from a client device in communication with a third-party device. Furthermore, the method includes determining whether the operating mode is associated with allowing access to the secure data item. Further, the method includes providing a response based on the determination.

Description

Technical Field

[0001] The present disclosure relates to secure data, and more particularly to wearable secure data devices. Background Art

[0002] Nowadays, people exchange relatively large amounts of their data with different entities over the Internet, and much of this data is private or sensitive. However, the security of data on the Internet is usually entrusted to the security on the client device (e.g., phone). Alternatively, the security of the data may be entrusted to websites that store such data on their own servers. Therefore, there is a need to solve the above problems. Summary of the invention

[0003] From a first aspect, the present invention provides a computer-implemented method comprising: setting an operating mode of a security data device for storing multiple security data items; receiving a request for at least one of the security data items from a client device that communicates with a third-party device; determining whether the operating mode is associated with allowing access to the security data item; and providing a response based on the determination.

[0004] From another aspect, the present invention provides a computer program product, comprising program instructions stored on a computer-readable storage medium, wherein the computer-readable storage medium is not the transient signal itself, and the program instructions can be executed by a processor to enable the processor to perform a method, the method comprising: setting an operating mode of a security data device for storing multiple security data items; receiving a request for at least one of the security data items from a client device that communicates with a third-party device; determining whether the operating mode is associated with allowing access to the security data items; providing a response based on the determination, wherein: the operating mode is associated with allowing access to the security data items; and providing the response comprises: retrieving the at least one security data item from a secure storage device of the security data device; decrypting the at least one security data item; and generating a response including the at least one security data item.

[0005] From another aspect, the present invention provides a system comprising: a communication interface; a security sensor; a computer processing circuit; a portable housing that surrounds the communication interface, the security sensor and at least a portion of the computer processing circuit; and a computer-readable storage medium storing instructions, wherein the instructions, when executed by the computer processing circuit, are configured to: cause the computer processing circuit to perform a method, the method comprising: setting an operating mode of a security data device for storing multiple security data items; receiving a request for at least one of the security data items from a client device that communicates with a third-party device; determining whether the operating mode is associated with allowing access to the security data items; and providing a response based on the determination, wherein: the operating mode is not associated with allowing access to the security data items; and providing the response comprises generating a shutdown response that does not include the at least one security data item.

[0006] Viewed from another aspect, the invention provides a computer program product for a secure data device, the computer program product comprising a computer readable storage medium readable by a processing circuit and storing instructions for execution by the processing circuit to perform a method for performing the steps of the invention.

[0007] Viewed from another aspect, the invention provides a computer program stored on a computer readable medium and loadable into the internal memory of a digital computer, the computer program comprising software code portions for performing the steps of the invention when said program is run on a computer.

[0008] Embodiments of a method for a wearable secure data device are disclosed. The method includes setting an operating mode of a wearable secure data device for storing a plurality of secure data items. The method also includes receiving a request for at least one secure data item from a client device in communication with a third-party device. Furthermore, the method includes determining whether the operating mode is associated with allowing access to the secure data item. Further, the method includes providing a response based on the determination.

[0009] Further aspects of the present disclosure relate to systems and computer program products having functionality similar to that described above with respect to the computer-implemented method.This summary is not intended to illustrate every aspect, every implementation, and / or every implementation of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings included in this application are incorporated into the specification and form a part of the specification. They illustrate embodiments of the present disclosure and are used to explain the principles of the present disclosure together with the description. The accompanying drawings only illustrate certain embodiments and do not limit the present disclosure.

[0011] Figure 1is a block diagram of a system for protecting data according to some embodiments of the present disclosure.

[0012] Figure 2 is a block diagram of an exemplary wearable secure data device according to some embodiments of the present disclosure.

[0013] Figure 3 is a block diagram of a network proxy system according to some embodiments of the present disclosure.

[0014] Figure 4 is a block diagram of a client device plug-in system according to some embodiments of the present disclosure.

[0015] Figure 5 is a process flow diagram of a method for a wearable secure data device according to some embodiments of the present disclosure.

[0016] Figures 6A-6C is a block diagram of an example wearable secure data device according to some embodiments of the present disclosure.

[0017] Figure 7 is a block diagram of an example wearable secure data device according to some embodiments of the present disclosure.

[0018] Although the present disclosure is subject to different modifications and alternative forms, its details have been shown by the examples in the drawings and will be described in detail. However, it should be understood that the present invention is not limited to the specific embodiments described. On the contrary, it is intended to cover all modifications, equivalents and replacements that fall within the scope of the present disclosure. DETAILED DESCRIPTION

[0019] Because the security of private and / or sensitive data may be left to the client device used to connect to the Internet and the service provider on the Internet, vulnerabilities in such client devices and / or servers may result in exposure of the private and / or sensitive data. Private and / or sensitive data stored in the cloud may be vulnerable to attacks on the cloud. Further, trusting data to be secure on the client device depends on the security of the client device. The client device may be a mobile computing device, such as a smartphone or tablet. However, the client device may be multifunctional, which may make these devices vulnerable to cyber attacks. Therefore, it is challenging to provide a reliable security mechanism to protect private and / or sensitive data in the control of a user that is independent of the client device or service provider.

[0020] Therefore, some embodiments of the present disclosure may provide a wearable secure data device that is a wearable secure repository for private and / or sensitive data. The wearable secure data device may store and maintain encrypted copies of private and / or sensitive data. Further, the wearer of the wearable secure data device may manually operate sensors on the wearable secure data device, for example, to release private and / or sensitive data when the wearer determines that the private and / or sensitive data can be safely released. In addition, the wearer may make specific choices about which data to release from the secure data.

[0021] Figure 1 1 is a block diagram of a system 100 for protecting data according to some embodiments of the present disclosure. The system 100 may include a network 102, a client device 104, a content server 106, and a wearable secure data device 108 hosting secure data 110. The network 102 may be one or more computer communication networks, including a local area network (LAN) and a wide area network (WAN). In some embodiments, the network 102 includes the Internet. The network 102 may enable communication between the client device 104, the content server 106, and the wearable secure data device 108.

[0022] The client device 104 may be a computing device with a computer processor and memory, such as a laptop computer, a tablet computer, a smart watch, a smart speaker, a smart phone device, etc. The client device 104 may be connected to the network 102 to access the content server 106 via the Internet. The content server 106 may include servers that provide different services, including web servers, streaming video, chat, email, etc.

[0023] As previously mentioned, the security of the data is important for the client device 104 and / or content server 106 that may be entrusted with processing personal data. In contrast, in some embodiments of the present disclosure, the wearable secure data device 108 may protect secure data 110. The secure data 110 may include different types of personal and / or sensitive information, including name, address, age, social security number, bank account number, credit card number, etc. According to some embodiments of the present disclosure, the secure data 110 may be stored in the secure data storage device 108. For example, the secure data storage device 108 may utilize encryption to store the secure data 110.

[0024] Further, the wearable security data device 108 may be a wearable computer including, for example, a processor (not shown), a storage device (not shown), a sensor (e.g., a security sensor) 112, and a network interface (not shown). The sensor 112 may be a physical interface of the wearable security data device 108 that may be used to change the security mode of the wearable security data device 108. Examples of the sensor 112 include, but are not limited to, a button, a biometric scanner, a touch sensor, a switch, and a microphone. In different modes, the wearable security data device 108 may operate differently. For example, in the closed operation mode, the wearable security data device 108 may not reveal the security data 110 to any other computing device (including the client device 104 and the content server 106). In contrast, during the open operation mode, the wearable security data device 108 may expose specific data from the security data 110 to other devices. According to some embodiments of the present invention, the physical operation of the sensor 112 may change the operation mode between open and closed. For example, pressing a button of the sensor 112 may cause the wearable security data device 108 to switch from the open mode to the closed mode, and vice versa.

[0025] Further, the wearable security data device 108 can be paired with a computer application (app) running on the client device 104. In this way, the operation of the wearable security data device 108 can be defined. The app can enable the owner of the security data 110 to configure the behavior of the wearable security data device 108 to allow certain types of information (e.g., spouse's birthday) to be revealed to predetermined types of websites (bank or travel websites). When in open mode, the application can also define and enforce the permitted data release for the wearable security data device 108. More specifically, when the wearable security data device 108 examines communications from the client device 104 to other devices (such as the content server 106), the app can define the types of personal information that can be collected from the wearable security data device 108.

[0026] According to some embodiments of the present disclosure, the wearable secure data device 108 may be a wearable garment, jewelry, or accessory that includes a processor and secure data storage. The wearable secure data device 108 may store and maintain an encrypted copy of the secure data 110. Further, a simple operation on the wearable secure data device 108, such as a button or sensor, may enable the wearable secure data device 108 to release the secure data 110 to an application on the client device 104 or to an external entity, such as a content server 106. In this way, the wearable secure data device 108 may provide control over the secure data 110 itself and who gains access.

[0027] For example, client device 104 may request a service, such as a streaming service of a popular movie, from content server 106. However, as a condition of providing the service, content server 106 may request information stored in secure data 110, such as a form of payment. Thus, in response to the pressing of a button on wearable secure data device 108, wearable secure data device 108 may read and decrypt the name, address, and credit card number from secure data 110. Further, wearable secure data device 108 may provide the requested data directly or indirectly (e.g., via client device 104) to a streaming video content server.

[0028] Figure 2 is a block diagram of an example wearable secure data device 200 according to some embodiments of the present disclosure. The wearable secure data device 200 may be similar to the Figure 1 The wearable secure data device 108 is described. Return to reference Figure 2 , the wearable secure data device 200 can be portable and small enough to be a wearable secure data vault. The wearable secure data device 200 includes a housing 202 for a flash drive 204, a processor 206, a secure sensor 208, a network interface 210, a battery 212, and a connector 214. The flash drive 204 can be an electronic data storage device without moving parts. The flash drive 204 can be, for example, an integrated circuit memory chip. According to some embodiments of the present disclosure, the flash drive 204 can store encrypted data. The processor 206 can be a computer processing circuit configured to perform the techniques described herein. More specifically, the processor 206 can run software to encrypt and decrypt data on the flash drive 204. The secure sensor 208 can be an operable physical interface that sends a configuration control request to the processor 206 to change the operating mode. The network interface 210 can be a wireless computer communication network interface. According to some embodiments of the present disclosure, the network interface 210 can enable the wearable secure data device 200 to communicate with an external client device (such as a computer device with respect to a computer). Figure 1 Communications between client devices 104 described herein.

[0029] Return to reference Figure 2, the battery 212 can be coupled to the flash drive 204, the processor 206, the sensor 208, and the network interface 210. In addition, the battery 212 can be charged by an external power source through the connector 214. The external power source can be, for example, a power outlet or a photovoltaic charging panel that is wired to the connector 214 (e.g., a micro USB port). Therefore, the flash drive 204, the processor 206, the security sensor 208, the network interface 210, the battery 212, and the connector 214 can be arranged in the housing 202 and on the housing 202, and electrically interconnected. In addition, the housing 202 can therefore be incorporated into a wearable item (such as a ring, a watch, a bracelet, a glove, etc.), thereby making it possible to have secure data 110 (about Figure 1 A user of the device 200 can wear a wearable secure data device 200. In this way, the wearable secure data device 200 can give such a user physical control over the security of their secure data 110.

[0030] According to some embodiments of the present disclosure, the security sensor 208 may be a fingerprint scanner that scans the fingerprint of the authenticated user to place the wearable security data device 200 in different operating modes. In the closed mode, the wearable security data device 200 may protect the security data 110 by not allowing access to the security data 110. In other words, the request for the security data 110 is rejected. In contrast, in the open operating mode, the wearable security data device 200 may allow the security data 110 to be read according to a predetermined access control policy. Alternatively or additionally, the security sensor 208 may include a touch sensor that triggers a change in the operating mode in response to a predetermined number of touches on the security sensor 208. Alternatively or additionally, the security sensor 208 may be a physical switch that can be moved to different positions for different modes. Alternatively or additionally, the security sensor 208 may include a small cross-over switch that can be configured for multiple possible combinations of operating modes. Alternatively or additionally, the security sensor 208 may be an audio microphone that can trigger different operating modes in response to predetermined verbal commands.

[0031] In some embodiments, the secure data 110 may be classified based on data type, and privacy and / or sensitivity level. Thus, in such embodiments, physical separation may be used to enforce control of the type and level of data to be released according to different operating modes. For example, the locations where data of different types and levels are stored in the flash drive 204 may be physically separated. In addition, the communication circuits on which data of different types and levels are read and written may be physically separated. According to some embodiments of the present disclosure, control may be implemented by electrical and digital devices, wherein digital logic circuits and gates are used to implement strategies under which the secure data 110 may be released.

[0032] Figure 3 3 is a block diagram of a client device plug-in system 300 according to some embodiments of the present disclosure. The client device plug-in system 300 may include a client device 302, a wearable secure data device 304, and a network router 306. The client device 302, the wearable secure data device 304, and the network router 306 may be similar to the Figure 4 Client device 402, wearable secure data device 404, and network router 406 are depicted.

[0033] Return to reference Figure 3 In the client device plug-in system 300, the client device 302 may include a computer application (app) 308, such as a driver or software development kit. The application 308 may make a request 310 to the wearable secure data device 304 for the secure data 110. The wearable secure data device 304 may be paired with the client device 302 so that the wearable secure data device 304 may provide a response 312 in response to the request 310. In the open mode of operation, the wearable secure data device 304 may include the requested information (about the secure data 110) from the secure data 110. Figure 1 ). In the closed mode of operation, the wearable secure data device 304 may provide a closed response, e.g., providing the response 312, but with a blank or zeroed value in place of the requested secure data. Alternatively, in the closed mode of operation, the wearable secure data device 304 may not generate the response 312. Thus, for example, the client device 302 may generate a request to the content server 106 (regarding the request to the content server 106) without the secure data 110 from the wearable secure data device 304. Figure 1 The client device 302 may use the network router 306 to send the request 314 to the content server 106. In addition, the content server 106 may generate a response 316 to the network router 306, and the network router 306 may provide the response 316 to the client device 302.

[0034] Because the wearable secure data device 304 is used as a client device plug-in rather than a network proxy, the wearable secure data device 304 cannot modify requests to external servers such as the content server 106. However, the wearable secure data device 304 can ensure that the request 314 does not include the secure data 110 stored in the wearable secure data device 304. Further, as a client device attachment, the wearable secure data device 304 cannot modify the response 316 from the content server 106. Therefore, in the client device attachment system 300, the wearable secure data device 304 can only protect the privacy of the secure data 110, but cannot protect the privacy of the client device 302.

[0035] Figure 4 4 is a block diagram of a network proxy system 400 according to some embodiments of the present disclosure. The network proxy system 400 may include a client device 402, a wearable security data device 404, and a network router 406. The client device 402 and the wearable security data device 404 may be similar to those described with respect to Figure 1 The wearable secure data device 404 may be similar to the client device 104 described above. Figure 1 The wearable secure data device 108 described herein and the Figure 2 The wearable secure data device 200 is described. Return to reference Figure 4 The network router 406 may be a computer communication device that physically routes data packets to a network. Thus, the client device 402 and the wearable secure data device 404 may be connected to the Internet, for example, via the network router 406.

[0036] According to some embodiments of the present disclosure, the client device 402 can be used with the wearable safety data device 404 in one of two network topologies: a network proxy and a client device attachment. In the network proxy system 400, the wearable safety data device 404 uses its network interface to become a proxy for the client device 402. In other words, the wearable safety data device 404 can act as a Wi-Fi access point for the client device 402, thereby enabling the client device 402 to connect to the Internet through the wearable safety data device 404. In this way, the wearable safety data device 404 can intercept the request 408-1 from the client device 402. Further, the wearable safety data device 404 can modify the request 408-1, for example, replace the personally identifiable information in the request 408-1 with some other type of information. Alternatively or additionally, the wearable safety data device 404 can add some additional information. Therefore, the wearable safety data device 404 can forward the modified request 408-2 with the replacement and / or additional data. Similarly, the wearable security data device 404 can intercept the response 410-1 from the network router 406. In some scenarios, for example, some websites can place tracking tags within the response 410-1. These tracking tags can track the activities of the client device 402. In some cases, the tracking tags can include images to be downloaded, or cookies that identify the client device 402 during repeated interactions. The wearable security data device 404 can remove such tags so that the privacy of the individual is better protected. Therefore, for example, the wearable security data device 404 can modify the response 410-1 from the website and generate a modified response 410-2. Further, the wearable security data device 404 can send the modified response 410-2 to the client device 402. Therefore, in the network proxy system 400, the wearable security data device 404 can protect the privacy of the security data 110 and the client device 402.

[0037] Figure 5 is a process flow diagram of a method 500 for a wearable secure data device according to some embodiments of the present disclosure. The method 500 may be performed by a wearable secure data device, such as Figure 1 A wearable secure data device 108 is described.

[0038] Return to reference Figure 5 At operation 502, the wearable safety data device 108 may configure an operating mode. In some embodiments of the present disclosure, the operating mode may be configured as an open mode in which safety data may be released. Alternatively, the operating mode may be configured as a closed mode in which safety data is not released. The wearable safety data device 108 may configure the operating mode in response to an input detected by a safety sensor (such as sensor 112).

[0039] At operation 504, the wearable secure data device 108 may receive a request for access to information from the secure data 110. The request may be received from a client device, such as the client device 104. In a network proxy system, the request may include a request from the client device to a content server, such as the content server 106. In a client device plug-in system, the request may simply be a request for the secure data 110.

[0040] At operation 506 , the wearable safety data device 108 may determine whether the operating mode is on or off. If the operating mode is on, control may flow to operation 508 . If the operating mode is off, control may flow to operation 512 .

[0041] At operation 508, the wearable secure data device 108 may store the data from a secure storage device (such as a Figure 2 The flash drive 204 described herein retrieves the requested information. Return to Reference Figure 5 In operation 508 , the wearable secure data device 108 may also decrypt the data read from the flash drive 204 .

[0042] At operation 510, the wearable secure data device 108 may provide the secure data in a response. The wearable secure data device 108 may encapsulate the decrypted data in the response and provide the response based on the network system. In a network proxy system, the wearable secure data device 108 may augment the original request from the client device 104 with the requested secure data 110 and forward the request to the content server 106. In a client device attachment system, the wearable secure data device 108 may send the requested secure data 110 in response to the client device 104.

[0043] As previously described, if the operating mode is off, control flows to operation 512. At operation 512, the wearable secure data device 108 may provide a shut down response to the original request. In the shut down mode, the wearable secure data device 108 may not release the secure data 110.

[0044] Thus, in a network proxy system, the wearable secure data device 108 may generate a modified request from the client device 104 to the content server 106. The modified request may include a blank or empty field in place of the requested secure data. Additionally, the wearable secure data device 108 may send the modified request to the content server 106. In a client device attachment system, the wearable secure data device 108 may provide a close response to the client device 104. Alternatively, the wearable secure data device 108 may not respond to the request for secure data 110.

[0045] Fig. 6A is a block diagram of an example wearable secure data device 600A according to some embodiments of the present disclosure. As previously described, the structure of a wearable secure data device (such as wearable secure data device 600A) can vary. The example wearable secure data device 600A includes a housing 602A, which includes a finger ring with a retainer 604A that can be worn by a male, female and / or child. The retainer 604A can be similar to the structure used to retain gemstones or markers on a ring. In such an embodiment, the retainer 604A may include a system on a chip (SOC) 606A. The system on a chip 606A may include a flash drive, a processor, sensors, a network interface, a battery, and connections, such as with respect to Figure 2 Depicted flash drive 204, processor 206, sensor 208, network interface 210, battery 212, and connector 214. In some embodiments, wearable secure data device 600A may include a jewel or other decoration on holder 604A above SOC 606A. In some embodiments, connector 214 may be configured within the jewel.

[0046] As previously described, the data owner can put the wearable safety data device 600A into an operating mode (on or off) by using a security sensor, such as by tapping the touch sensor multiple times. In addition, the wearable safety data device 600A may include one or more light emitting diode (LED) lights that illuminate to visually indicate the operating mode. Therefore, each possible color of the LED light may represent a different operating mode. In other embodiments, the operating mode of the wearable safety data device 600A can be displayed and controlled on an application running on the client device 104, wherein the state and control commands of the operating mode are communicated between the wearable safety data device 600A and the client device 104 through an isolated security control communication channel that is physically or logically separated from the communication method for releasing the safety data 110.

[0047] Figure 6B600B is a block diagram of an example wearable security data device 600B according to some embodiments of the present disclosure. The example wearable security data device 600B may be similar to the example wearable security data device 600A, but has a different configuration. For example, the example wearable security data device 600B includes an annular housing 602B, and a retainer 604B that can be used to retain a gem or a marker on a ring. In such an embodiment, the retainer 604B may include a system on a chip (SOC) 606B. The system on a chip 606B may include a flash drive 204, a processor 206, a sensor 208, a network interface 210, and a battery 212. However, instead of placing the connector 214 on the SOC 606B, the annular housing 602B is configured with a connection 608B. Therefore, the annular housing 602B may include an electrical connector 610B that provides power to the battery of the SOC 606B.

[0048] Figure 6C 602C. 602C is a block diagram of an example wearable secure data device 600C according to some embodiments of the present disclosure. The example wearable secure data device 600C can be similar to the example wearable secure data devices 600A and 600B, but has a different configuration. In the example wearable secure data device 600C, the same set of components from the example wearable secure data devices 600A, 600B can be distributed at other locations along the annular housing 602C.

[0049] For example, the example wearable secure data device 600C includes an annular housing 602C and a retainer 604C that can be used to retain gemstones or markers on the ring. In such an embodiment, the retainer 604C may include a sensor 606C and a processor 608C. Further, the housing 602C may also include a flash drive 610C, a network interface 612C, a battery 614C, and a connection 616C. In addition, the annular housing 602C may include an electrical connection 618C that conducts power from the connection 616C to the battery 614C and from the battery to other electrical components of the wearable secure data device 600C.

[0050] Figure 7 700 according to some embodiments of the present disclosure. As previously described, the structure of a wearable secure data device such as the wearable secure data device 700 can vary. For example, the wearable secure data device 700 has a watch band housing 702 with a retainer 704. The retainer 704 can be similar to the structure that retains a watch dial in the watch band housing 702. In this embodiment, the retainer 704 may include a SOC 706, which may include information about Figure 2 Flash drive 204, processor 206, sensor 208, network interface 210, battery 212, and connector 214 are depicted.

[0051] The present disclosure may be a system, method and / or computer program product of any possible technical detail integration level. The computer program product may include a computer-readable storage medium (or media) having computer-readable program instructions thereon for causing a processor to execute aspects of the present invention.

[0052] Computer readable storage media can be a tangible device that can retain and store instructions for use by instruction execution devices. Computer readable storage media can be, for example but not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination of the above. A non-exhaustive list of more specific examples of computer readable storage media includes the following: portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), static random access memories (SRAM), portable compact disk read-only memories (CD-ROM), digital versatile disks (DVD), memory sticks, floppy disks, mechanical encoding devices such as punch cards, or protruding structures in the grooves with instructions recorded thereon, and any suitable combination of the above. Computer readable storage media as used herein should not be interpreted as temporary signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagated by waveguides or other transmission media (e.g., light pulses passing through fiber optic cables), or electrical signals emitted by wires.

[0053] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to a corresponding computing / processing device via a network (e.g., the Internet, a local area network, a wide area network, and / or a wireless network), or downloaded to an external computer or external storage device. The network can include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in a computer-readable storage medium in the corresponding computing / processing device.

[0054] The computer-readable program instructions for performing the operation of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, configuration data of an integrated circuit, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Smalltalk, C++, etc.) and process programming languages ​​(such as "C" programming languages ​​or similar programming languages). The computer-readable program instructions may be executed completely on a user's computer, partially on a user's computer, executed as an independent software package, partially on a user's computer, partially on a remote computer, or completely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network (including a local area network (LAN) or a wide area network (WAN)), or may be connected to an external computer (e.g., using an Internet service provider via the Internet). In some embodiments, an electronic circuit including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) may be personalized to execute computer-readable program instructions by utilizing the state information of the computer-readable program instructions to perform various aspects of the present disclosure.

[0055] Various aspects of the present disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of boxes in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0056] These computer-readable program instructions can be provided to a processor of a computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions / actions specified in one or more boxes of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, which instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable storage medium in which the instructions are stored includes a manufactured product containing instructions for implementing aspects of the functions / actions specified in one or more boxes of the flowchart and / or block diagram.

[0057] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device, so that a series of operational steps are performed on the computer, other programmable apparatus, or other device to produce computer-implemented processing, so that the instructions executed on the computer, other programmable apparatus, or other device implement the functions / actions specified in or in multiple boxes in the flowchart and / or block diagram.

[0058] The flowcharts and block diagrams in the accompanying drawings show the architecture, functions and operations of possible implementations of the system, method and computer program product according to different embodiments of the present disclosure. To this end, each box in the flowchart or block diagram may represent a module, segment or part of an instruction, which includes one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the box may not occur in the order marked in the figure. For example, the two boxes shown in succession can actually be completed as a step, and are executed simultaneously, substantially simultaneously, in a partially or completely overlapping manner in time, or the boxes can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action or performs a combination of dedicated hardware and computer instructions.

Claims

1. A computer-implemented method for a secure data device, comprising: responsive to the security sensor detecting a manual user input, changing an operating mode of a secure data device storing a plurality of secure data items from a closed operating mode to an open operating mode; receiving a request for at least one of the secure data items from a client device in communication with a third-party device; and providing a response to the request for the at least one security data item, wherein the response includes at least one of the security data items for the open mode of operation, and wherein the response includes a blank response for the closed mode of operation, wherein providing the response to the request includes providing the response directly to a third party device; The secure data device is capable of intercepting requests from a client device, modifying the requests and forwarding the modified requests to a third-party device, and the secure data device is also capable of intercepting responses from a third-party device to remove tracking tags therein, modifying the responses and sending the modified responses to the client device.

2. The method according to claim 1, wherein: The operating mode is associated with allowing access to the secure data item; as well as Providing the response includes: retrieving the at least one secure data item from a secure storage device of the secure data device; decrypting the at least one secure data item; and The response is generated including the at least one security data item.

3. The method according to claim 1 or 2, wherein: The operating mode is not associated with allowing access to the secure data item; and Providing the response includes generating a close response that does not include the at least one security data item.

4. The method according to claim 1 or 2, wherein: The operating mode of the security data device is set in response to use of a sensor of the security data device.

5. The method of claim 1 or 2, further comprising illuminating the secure data device based on the operating mode.

6. The method according to claim 1 or 2, wherein: The request for the at least one secure data item comprises a request from the client device to the third party device.

7. The method according to claim 6, wherein: Providing the response includes modifying the request such that the request includes the at least one security data item.

8. A system for a secure data device, the system comprising: Communication interface; Safety sensors; Computer processing circuits; a portable housing enclosing the communication interface, the security sensor, and at least a portion of the computer processing circuitry; as well as A computer-readable storage medium storing instructions which, when executed by the computer processing circuit, are configured to cause the computer processing circuit to perform a method comprising: responsive to the security sensor detecting a manual user input, changing an operating mode of a secure data device storing a plurality of secure data items from a closed operating mode to an open operating mode; receiving a request for at least one of the secure data items from a client device in communication with a third-party device; providing a response to a request for at least one secure data item based on the operating mode, wherein providing the response to the request comprises providing the response directly to a third party device, and wherein: The response includes at least one of the security data items for opening the operating mode; The response comprises a blank response for the shutdown mode of operation; and Providing responses include: retrieving at least one secure data item from a secure storage device of a secure data device; decrypting the at least one secure data item; and generating a response including the at least one security data item; The secure data device is capable of intercepting requests from a client device, modifying the requests and forwarding the modified requests to a third-party device, and the secure data device is also capable of intercepting responses from a third-party device to remove tracking tags therein, modifying the responses and sending the modified responses to the client device.

9. The system of claim 8, wherein: The operating mode is associated with allowing access to the secure data item.

10. The system of claim 8 or 9, wherein: The operating mode of the secure data device is set in response to use of the secure sensor of the secure data device.

11. The system of claim 8 or 9, further comprising illuminating the secure data device based on the operating mode.

12. The system according to claim 8 or 9, wherein: The request for the at least one secure data item comprises a request from the client device to the third party device.

13. The system according to claim 12, wherein: Providing the response includes modifying the request such that the request includes the at least one security data item.

14. The system according to claim 8 or 9, wherein: The security sensor is selected from the group consisting of a touch sensor, a button, a biometric sensor, a switch, and a microphone.

15. A computer program product for a secure data device, the computer program product comprising: A computer readable storage medium readable by a processing circuit and storing instructions for execution by the processing circuit to perform the method according to any one of claims 1 to 7.

16. A computer-readable medium on which is stored a computer program loadable into the internal memory of a digital computer, the computer program comprising software code portions for executing the method according to any one of claims 1 to 7 when the program is run on a computer.

Images