GB2462442A

GB2462442A - A remote server centrally controls access to data stored in a data container in an encrypted form

Info

Publication number: GB2462442A
Application number: GB0814371A
Authority: GB
Inventors: Richard Zybert; Eric Genevier
Original assignee: ZYBERT COMPUTING Ltd
Current assignee: ZYBERT COMPUTING Ltd
Priority date: 2008-08-06
Filing date: 2008-08-06
Publication date: 2010-02-10
Also published as: GB0814371D0

Abstract

Disclosed is a method providing secure storage and transportation of secret, confidential or private data. The data is stored in encrypted form on a portable data container 5 such as a removable USB flash drive or an optical disk. Access to decryption keys is controlled by a central system regardless of the whereabouts of the data container, thus protecting secure information if the actual data containers are lost or stolen. The central system preferably comprises an authentication server 10 which sends decryption keys to a user's application 6 upon authentication of the user 1. The system avoids delays and bandwidth issues associated with 'Host-Based' systems as only keys and authentication information are transmitted via potentially slow links and large volumes of data are kept fully encrypted on the data container.

Description

Title: Centrally-Controlled Strong Encryption system

Background

This invention relates to secure storage and transportation of secret and confidential data.

Protection of confidential, secret and personal data is critical to the operation of computer-based systems. Advancements in networking infrastructure and changes in working practices make it essential to access the data either remotely or outside the controlled environment.

Standard encryption practices do not protect managers from losing control over files once the data leave the controlled environment. Stolen computers and media carrying sensitive information may be subjected to attempts to break the encryption systems over a prolonged period, increasing the chances of obtaining unauthorized access to data that may become harmful or outright dangerous as well as unlawful.

More secure, "Host-Based" systems are based on secure, encrypted data remaining on the server while the authorized user can access the data through a secure remote connection.

However, the increase in the necessary volume of the transmitted data makes these systems very inefficient, slow and increasingly cumbersome. Central data storage also has the disadvantage that once unauthorized access is achieved, all the data becomes accessible which means that these systems represent particularly alluring targets for attack.

The data security is frequently compromised by the use of encryption keys that are too short or easy to break. The rapid proliferation of inexpensive computing power employed to break encryption keys requires the use of long and complex keys, making the system inconvenient and tedious to use. This often is the cause of users breaking the prescribed rules, leading to loss of confidential, secret or commercially critical data.

There is a clear need for a system which would allow administrators to control access to data even when the data containers are misplaced, stolen or lost.

Statement of invention

To overcome this, the present invention proposes a Centrally-Controlled Strong Encryption system (referred to hereafter as the CCSE system).

In contrast to previous methods, the CCSE system addresses the situation where there is a need to access data in remote locations outside prescribed procedures, but access to data needs to be controlled. It also implies that once the authorization has been obtained, access to data should be possible via standard and commonly used applications.

The CCSE system provides flexibility of implementation on several levels. The modular design of secure access from remote and uncontrollable locations becomes possible and manageable.

1. Encrypted data containers are kept wherever they need to be accessed, independently of the storage mechanism. Typical examples are computer disks, optical disks, removable USB or Firewire storage etc. Forthcoming different types or mechanisms for storage can use the same principle of the CCSE system.

2. Keys are randomly generated and sufficiently long to make the breaking of the encryption code impracticable.

3. The keys, when enabled, can be accessed and used by the authorized users every time the container with the encrypted data is opened. However, the decrypted data are only opened temporarily and subsequent access requires new authentication for an access to obtain the key for the decryption. Therefore, if the data container is ost or stolen, the corresponding key can be disabled making it practically impossible to decrypt the information. The strength of the encryption is not pre-determined and can be adapted with changing technology.

4. As the encryption is at the container' level, the applications used to read/write data files do not need to be aware of encryption.

5. The contents -potentially large volumes of data to be read/written -are not transmitted and as such do not depend on the form of communication between the server and the user in contrast to the "Host-Based" system described above in the background section. Only the encryption keys reside on the centrally-controlled server but the server itself contains no data for decryption or information about the location of the data.

6. The CCSE system does not rely on any sing'e and particular type of computer technology involved in data security and as such can be used in unlimited applications using either freely available Open Source type solutions to individual tasks or proprietary hardware/software solutions. It allows the freedom to develop specific applications at the stage of the implementation of the CCSE system.

7. The CCSE can be utilized in corporate as well as personal environments, where different implementation rules need to be adopted but the choice does not require any changes to the concept of the CCSE.

Preferably, the implementation of the system should include the following: 1. Secure connection to the server, which holds the encryption keys 2. Enhanced security of the server itself 3. Audit system to allow connection monitoring 4. Enhanced authentication system, for instance including biometrics, one-time passwords or third party authentication Advantages 1. The CCSE system protects sensitive data from unauthorised access more securely than the prior art because the keys required for access are not stored outside of the central control 2. The system allows for transportation of very strongly encrypted data but the access to encryption keys is controlled by the central system regardless of the whereabouts of the managed data, thus protecting secure information if the actual data containers are lost or stolen 3. Storing keys on the central system allows the use of very strong, long and random cryptographic keys that would be impractical were they to be provided by a user. The use of very strong encryption makes it impracticable to break the code if access to the keys is denied 4. Ease and speed of use for authorized users means the users are less likely to contravene the prescribed security rules.

5. The system avoids delays and bandwidth issues associated with Host-Based' systems as only keys and authentication information are transmitted via potentially slow links and large volumes of data are kept fully encrypted on any type of medium.

6. The Centrally-Controlled Encryption System is flexible, modular and designed to absorb different implementations with changing needs and technology Examples and explanation of drawings Example of the invention will now be described by referring to the accompanying drawings: Figure 1 shows a typical example of the CCSE system The user 1 in Figure 1 is in possession of a strongly encrypted data container 5. The user 1 then connects via any kind of available Internet communication 7 to a central secure server 10 and the authentication process 8 starts. Authorization for an access can now be established. It is be possible to limit the access, for example access may be restricted to some part of the data or the type of actions allowed to be performed on the data could be restricted. The dedicated administration application 6 on the users computer obtains the necessary keys 9 from the server and temporarily decrypts 4 the data container 5 in the user's possession, giving access to the data 3 as predetermined by the administration. The type of access and restrictions of use as well as logging of access can be controlled by the administration tools. All keys kept on the server are additionally encrypted and the authentication process can require additional information, e.g. biometrics, passwords etc. No information regarding the data -including the address where the data are actually stored -is kept on the server that contains the encryption keys, rendering breaking into the central key storage useless by itself. The server may apply penalties on repeated failed authentication and/or time-lock" procedures" or other controls, which restrict access to the keys. In some applications the server may be able to additionally detect unusual usage patterns to provide more protection of stored keys.

Figure 2 shows an example of a managed system for corporate users. The data storage and user access are identical to those in Figure 1, however the appointed administrator 11 manages the keys, permissions and user access, and determines which, if any, of the keys may be shared or should be disabled or modified. The Administration is performed via an independent secure connection 12.

Figure 3 shows an example of a public service designed for individual usage. There is no administrator; new users create accounts by registering 13 through an Internet service 14 to a dedicated registration server 15.

Claims

Claims 1. Centrally-Controlled Strong Encryption system where locally kept data in a container are encrypted and where user's access to the data container is centrally controlled by a remote secure server.
2. Centrally-Controlled Strong Encryption system in Claim 1 in which the data container is a disk file.
3. Centrally-Controlled Strong Encryption system in Claim 1 in which the data container is a hardware or firmware device.
4. Centrally-Controlled Strong Encryption system in Claim 1 in which the data container is a computer program.
5. Centrally-Controlled Strong Encryption system in Claim 1 in which the data container is a combination of files and programs or hardware or firmware devices.
6. Centrally-Controlled Strong Encryption system in Claim 1 in which the data container is is a distributed storage system comprising multiple files and/or programs and/or hardware or firmware devices on a single or multiple computers.
7. Centrally-Controlled Strong Encryption system in Claim 1 in which the encryption is provided by a dedicated hardware device.
8. Centrally-Controlled Strong Encryption system in Claim 1 in which the remote server provides authentication services.
9. Centraily-Controlled Strong Encryption system in Claim 1 in which the remote server provides authorization services
10. Centraly-ControUed Strong Encryption system in Claim 1 in which the remote server provides encryption services.
11.Centrally-Controlled Strong Encryption system in Claim 1 in which access to the contents of the data container is limited depending on time, date, location or software used.
12.Centrally-Controlled Strong Encryption system in Claim 1 in which access to the contents of the data container is unrestricted once the access to the data container is granted.
13.Centrally-Controlled Strong Encryption system as in Claim 1 in which access to the remote server is through any secure access connection technology.
14. Centrally-Controlled Strong Encryption system as in Claim 1 in which the user is replaced by a computer program or a hardware or firmware device.