US20150019881A1

US20150019881A1 - Accelerated cryptography with an encryption attribute

Info

Publication number: US20150019881A1
Application number: US14/502,875
Authority: US
Inventors: Yen Hsiang Chew
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2008-09-04
Filing date: 2014-09-30
Publication date: 2015-01-15
Also published as: KR20120065972A; EP2472426B1; EP2166479A1; JP2010063105A; US8880879B2; KR20100028516A; EP2472426A1; JP5417092B2; US20100054477A1; KR101405720B1

Abstract

Methods and systems for encrypting and decrypting are presented. In one embodiment, the method comprises encrypting one or more segments of a data with a key. The data is associated with at least one encryption attribute and having a plurality of segments. The encryption attribute includes information to identify one or more segments of the data to encrypt. The method further comprises encrypting the encryption attribute and storing the data including the partly encrypted data and the encrypted encryption attribute.

Description

FIELD OF THE INVENTION

Embodiments of the invention relate to the field of content security, in particular, for encrypting and decrypting a data.

BACKGROUND OF THE INVENTION

Symmetric cryptography is a cryptography method in which both the encryption and decryption operations share the same key (or, less commonly, in which their keys are different, but related in an easily computable way). Examples of symmetric cryptography algorithms include Data Encryption Standard (DES) and Advanced Encryption Standard (AES).
On the other hand, public key encryption algorithms use asymmetric keys for encryption and decryption. The asymmetric keys comprise a private key (which is held only by its owner) and a public key (which is available to other entities). The two keys are separate but complementary in function. Information that is encrypted with the public key can be decrypted only with the corresponding private key. The two keys together are called a key pair or a key set. RSA algorithm is an example of public key encryption algorithms.
Encrypting File System (EFS) is a file system with encryption services. The technology transparently allows files to be encrypted and decrypted on a file system to protect confidential data from attackers with physical access to the computer. An EFS uses public key cryptography to ensure that decrypting a file without a correct key is in theory impossible, or requires an unreasonable length of time to crack.
An EFS works by encrypting a file with a symmetric key, also known as File Encryption Key (FEK). The FEK is then encrypted with a public key that is usually associated with a user and is available to third parties. To decrypt the encrypted file, the EFS uses a private key, accessed only by the user, to decrypt the encrypted FEK. The EFS then decrypts the file which is encrypted with the FEK. In general, these encryption and decryption operations are performed at a layer below an operating system so that it is transparent to users and to applications running thereon.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention will be understood more fully from the detailed description given below and from the accompanying drawings of various embodiments of the invention, which, however, should not be taken to limit the invention to the specific embodiments, but are for explanation and understanding only.

FIG. 1 is a data flow diagram illustrating the encryption of data in accordance with one embodiment of the invention.

FIG. 2 is a data flow diagram illustrating the decryption of data in accordance with one embodiment of the invention.

FIG. 3 is a flow diagram of one embodiment of a encryption process

FIG. 4 is a flow diagram of one embodiment of a decryption process.

FIG. 5 shows a directory structure in an encrypting file system (EFS) in accordance with one embodiment of the invention.

FIG. 6 is a block diagram of one embodiment of a cryptography system.

FIG. 7 illustrates a computer system in which one embodiment of the invention may be used.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments of methods and systems for encrypting and decrypting with encryption attributes are presented. An encryption attribute contains information to identify one or more segments of a file to be encrypted. An encryption process encrypts those one or more segments to generate a partly encrypted file instead of encrypting the entire file. That is, the file includes some data that are encrypted and some data that are not. In one embodiment, the encryption attribute is encrypted and stored together with the partly encrypted file.
In one embodiment, the decryption operation identifies those segments that are encrypted in the partly encrypted file with the information contained in the encryption attribute. In one embodiment, an authorized user, for example the owner of the file, sets the encryption attribute associated with a file to identify segments of the file that should be encrypted during an encryption operation.
In the following description, numerous specific details are set forth to provide a more thorough explanation of embodiments of the present invention. However, it is understood that embodiments may be practiced without these specific details. In other instances, well-known elements, specifications, and protocols have not been discussed in detail in order to avoid obscuring the embodiments of the present invention.
Some portions of the detailed descriptions which follow are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
Embodiments of present invention also relate to apparatuses for performing the operations herein. Some apparatuses may be specially constructed for the required purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, DVD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, NVRAMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.
The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will appear from the description below. In addition, embodiments of the present invention are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein.
A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, a machine-readable medium includes read only memory (“ROM”); random access memory (“RAM”); magnetic disk storage media; optical storage media; flash memory devices; electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.); etc.

Overview

FIG. 1 is a data flow diagram illustrating the encryption of data in accordance with one embodiment of the invention. Referring to FIG. 1, in one embodiment, the elements in an encryption process include data 100, file encryption key (FEK) 104, encryption attribute 105, encryption engines 121-122, public key 112, and encrypted data 120.
In one embodiment, data 100 is a plaintext such as, for example, a media file, a text file, a data record of a database, or any form of digital information content. To encrypt data 100, encryption engine 121 receives FEK 104 as an encryption key and encryption attribute 105. Encryption attribute 105 contains information to identify one or more segments of data 100 to be encrypted. The result of encryption engine 121 is partly encrypted data 101. In one embodiment, FEK 104 and encryption attribute 105 are encrypted using encryption engine 122 with public key 112 which is associated with a user. The outputs from encryption engine 122 are encrypted FEK 107 and encrypted encryption attribute 111 respectively. In one embodiment, partly encrypted data 103, encrypted FEK 108, and encrypted encryption attribute 110 are stored together in encrypted data 120. In one embodiment, the overall time for performing the encryption operation is reduced because not all segments of the data are encrypted. The increase of performance depends on how many segments of the data are identified for encryption based on the information in encryption attribute 105. In one embodiment, encrypted data 120 is stored on an EFS or a file system, or is transmitted to be stored/used in another computer system.
In one embodiment, data 100 is divided into segments where each segment is M-bit in length such that the length is equal to one of the block sizes of encryption engine 121. In one embodiment, block ciphers in encryption engine 121 process a 128-bit segment in each round of an operation. It will be appreciated by one skilled in the art that, any block size suitable for implementing encryption can be used to determine the length of a segment for segmenting data 100 for the encryption purpose.
In one embodiment, encryption attribute 105 is set to a default setting based on a category or a file type of data 100. The default setting can be modified by users, administrators, or both. In one embodiment, encryption attribute 105 contains information such as, for example: a list of numbers corresponds to the list of segments to encrypt, a rule or a set of rules to describe which segment(s) to encrypt, an identifier corresponds to such rule(s), a pointer to a location storing such rule(s) or such list of numbers, or any combinations thereof. It will be appreciated by one skilled in the art that information can present in encryption attribute 105 in different ways to identify which segments of data 100 are to encrypt. In one embodiment, encryption attribute 105 includes additional information such as information about authorized users and designated recovery agents.
In one embodiment, data 100 is an instance of certain types of files. Encrypting the header (or the first N segments) of the file is sufficient to protect the file from unauthorized usages. For example, the header includes information crucial to interpret the file format, such as, for example: parameters associated with a video encoding algorithm, parameters associated with an image encoding algorithm, data fields of a data structure, or other security measures in place to protect the file.
In one embodiment, encrypting certain segments of data 100 renders the data useless unless the encrypted segments are recovered. For example, a patient's medical history record is useless if the patient name and his/her identifier number are encrypted and hence protected from unauthorized access. The medical history record is not useful if one can not associate it with a particular patient.
In one embodiment, data 100, such as a file, is encrypted by encrypting several segments in every N segments of the file. For example, a video file encrypted with this pattern has some of the video frames protected from viewing. The viewer of the encrypted file is not able to enjoy the entire length of the video without interruption. The encrypted file is deemed to be not usable because of the discontinuity. In comparison, encrypting some segments of the video file saves a lot of computational time than encrypting the entire video file. The performance of the encrypting file system increases as the burden of encrypting and decrypting the entire media files is reduced.
In one embodiment, data 100 is a file. Encryption engine 121 encrypts a plurality of segments of the file, for example: the header of the file, segments of important parts of the file, alternate N segments of the file, or any combinations thereof, to protect the file from unauthorized access.
In one embodiment, encryption attribute 105 is attached to partly encrypted data 103 without being encrypted. In one embodiment, encryption attribute 105 is encrypted with FEK 104 instead of with public key 112.
In one embodiment, encrypted encryption attribute 111 is appended to partly encrypted data 103. In one embodiment, encrypted encryption attribute 111 prepends partly encrypted data 103. In one embodiment, encrypted encryption attribute 110 is stored at a location associated to the partly encrypted data 103 according to the structure of a file system.
In one embodiment, encryption engine 121-122 are able to perform symmetric cryptography operations, asymmetric cryptography operations, or a combination thereof based on various cryptography algorithms (for example, AES, DES, RSA, etc.). The cryptography operations are implemented in block ciphers, stream ciphers, or any other cipher architectures known in the art.
FIG. 2 is a data flow diagram illustrating the decryption of data. Referring to FIG. 2, in one embodiment, the elements in a decryption process include private key 204, decryption engines 221-222, and encrypted data 220 which further includes partly encrypted data 208, encrypted FEK 209, and encrypted encryption attribute 210. In one embodiment, private key 204 belongs to a user and is only known to person who has authorization to read/access encrypted data 220.
In one embodiment, encrypted FEK 206 and encrypted encryption attribute 207 are extracted from encrypted data 220. Decryption engine 221 decrypts encrypted encryption attribute 207 with private key 204 to retrieve encryption attribute 203. Decryption engine 221 decrypts encrypted FEK 206 with private key 204 to retrieve FEK 202.
In one embodiment, decryption engine 222 decrypts partly encrypted data 205 with FEK 202 by referring to encryption attribute 203 to identify which segments of partly encrypted data 205 are encrypted. The output of decryption engine 222 is data 201, which may be a text file, a media file, or a data record of a database, or any form of digital information content. In one embodiment, encryption attribute 203 is attached to data 201 when stored on computer storages.
In one embodiment, the overall time for performing the decryption operation is reduced because decryption engine 222 does not need to decrypt all segments of partly encrypted data 205. The increase of performance depends on how many segments of partly encrypted data 205 that are identified for decryption based on the information in encryption attribute 203. In one embodiment, encrypted data 220 is stored on an EFS, or a file system, or is received from another computer system.
In one embodiment, partly encrypted data 205 is segmented into segments where each segment is M-bit in length such that the length equal to one of the block sizes of decryption engines 222. In one embodiment, block ciphers in decryption engine 222 process a 128-bit segment/block in each round of an operation. It will be appreciated by one skilled in the art that, any block size suitable for implementing decryption can be used to determine the length of a segment when segmenting partly encrypted data 205 for the encryption/decryption purpose.
In one embodiment, encryption attribute 203 is the same encryption attribute 105 of FIG. 1. It will be appreciated by one skilled in the art that information in encryption attribute 203 can be represented in different ways to identify which segments of partly encrypted data 205 to decrypt. Different types of data can be protected by encrypting segments of different parts of the data as explained above with reference to FIG. 1. In one embodiment, decryption engine 222 decrypts a plurality of segments, for example: the header of the file, segments of important parts of the file, alternate N segments of the file, or any combinations thereof, which are encrypted to protect from unauthorized access.
In one embodiment, encryption attribute 203 is attached to partly encrypted data 208 without being encrypted. In one embodiment, encryption attribute 203 is decrypted with FEK 202 instead of with private key 204.
In one embodiment, encrypted encryption attribute 210 is appended to partly encrypted data 208. In one embodiment, encrypted encryption attribute 210 prepends partly encrypted data 208. In one embodiment, encrypted encryption attribute 210 is stored at a location associated to partly encrypted data 208 according to the structure of a file system.
In one embodiment, decryption engines 221-222 are able to perform symmetric cryptography operations, asymmetric cryptography operations, or combinations thereof based on various cryptography algorithms (for example, AES, DES, RSA, etc.). The cryptography operations are implemented in block ciphers, stream ciphers, or any other cipher architectures known in the art.
FIG. 3 shows a flow diagram of one embodiment of an encryption process. The process is performed by processing logic that may comprise hardware (circuitry, dedicated logic, etc.), software (such as one that is run on a general purpose computer system or a dedicated machine), or a combination of both. Referring to FIG. 3, in one embodiment, processing logic receives a request to encrypt a file (processing block 300). Processing logic reads an encryption attribute associated with the file (processing block 301). Processing logic segments the file into a plurality of segments (processing block 302) where the length of each segment is suitable for processing by an M-bit encryption engine.
In one embodiment, processing logic identifies one or more segments of the file to encrypt based on the information contained in the encryption attribute (processing block 303). Processing logic determines whether a segment of the file is to be encrypted (processing block 310). If a segment is identified for encryption, an encryption engine encrypts the segment (processing block 304) with a FEK (a symmetric key). Otherwise, the encryption engine does not encrypt the segment (processing block 305). Processing logic repeats the operation for all the segments of the file (processing block 311).
In one embodiment, processing logic encrypts the FEK and the encryption attribute with a public key (processing block 306). In another embodiment, processing logic encrypts the encryption attribute with the FEK and encrypts the FEK with a public key. In one embodiment, processing logic encrypts only the FEK. In one embodiment, processing logic uses the same encryption engine to encrypt the FEK and the encryption attribute. In one embodiment, different encryption engines are used to encrypt the FEK and the encryption attribute.
In one embodiment, processing logic stores the partly encrypted file, the encrypted encryption attribute, and the encrypted FEK in a file (processing block 307). In one embodiment, processing logic transmits the file for use in another computer system. In one embodiment, processing logic stores the partly encrypted file, the encrypted encryption attribute, and the encrypted FEK according to the structure of a file system.
FIG. 4 is a flow diagram of one embodiment of a decryption process. The process is performed by processing logic that may comprise hardware (circuitry, dedicated logic, etc.), software (such as one that is run on a general purpose computer system or a dedicated machine), or a combination of both. Referring to FIG. 4, in one embodiment, processing logic receives a request to decrypt an encrypted file (processing block 400).
In one embodiment, the encrypted file contains a partly encrypted file, an encrypted encryption attribute associated with the partly encrypted file, and an encrypted FEK. In one embodiment, processing logic decrypts the encrypted encryption attribute to retrieve an encryption attribute and decrypts the encrypted FEK to retrieve a FEK (processing block 401). Processing logic segments the partly encrypted file into a plurality of segments (processing block 403) where the length of each segment is suitable for processing by an M-bit decryption engine.
In one embodiment, processing logic identifies one or more segments of the partly encrypted file to decrypt based on the information contained in the encryption attribute (processing block 404). Processing logic determines whether a segment of the file has to be decrypted (processing block 410). If a segment is identified for decryption, a decryption engine decrypts the segment with the FEK (processing block 405). Otherwise, the decryption engine does not decrypt the segment (processing block 406). Processing logic repeats the operation for all the segments of the partly encrypted file (processing block 411). Processing logic stores the decrypted file in a file on computer storages (processing block 407).
In one embodiment, processing logic decrypts the encrypted FEK and the encrypted encryption attribute with a private key (processing block 401). In one embodiment, processing logic decrypts the encrypted FEK with a private key and then decrypts the encrypted encryption attribute with the FEK. In one embodiment, processing logic decrypts only the FEK and the encryption attribute is not encrypted. In one embodiment, processing logic uses the same decryption engine to decrypt the encrypted FEK and the encrypted encryption attribute. In one embodiment, different decryption engines are used to decrypt the encrypted FEK and the encrypted encryption attribute.
In one embodiment, processing logic receives the partly encrypted file, the encrypted encryption attribute, and the encrypted FEK in a file. In one embodiment, processing logic receives the encrypted file from another computer system. In one embodiment, the partly encrypted file, the encrypted encryption attribute, and the encrypted FEK are stored associatively according to the structure of a file system.
FIG. 5 shows a directory structure in an encrypting file system (EFS) in accordance with one embodiment of the invention. Referring to FIG. 5, Each file comprises a number of segments. Segments indicated with a cross-hatching pattern are encrypted. The encryption attribute and the FEK of a file are not shown in the figure to avoid obscuring the description of the embodiment. The files do not have to be in the same length.
In one embodiment, the file system stores files under root directory 501 or other sub-directories (e.g., directories 502, 550). A sub-directory can further include other sub-directories such as sub-directory 520. In one embodiment, files under a same directory (e.g., root directory 501, directory 520) can be encrypted in different ways. Different segments of file 510, file 511, and file 513 are encrypted based on the encryption attributes associated with each of the file. For example, every alternate segment starting from the second segment of file 511 is encrypted. Two segments of every three segments of file 513 are encrypted. In one embodiment, the files (files 511, 513) are under different categories of file types and are assigned with different encryption attributes. In one embodiment, the files (files 511, 513) are under the same category of file types and the encryption attributes are modified by users.
In one embodiment, files 503-506 in a same directory (directory 502) are encrypted with the same encryption attributes. In one embodiment, files 503-506 are encrypted with the same encryption attributes because the files are under the same category of file types or belong to the same user. In one embodiment, files 551-554 in directory 550 are encrypted with different encryption attributes set by users based on the desired levels of security.
In one embodiment, a file does not have a default encryption attribute. For example, each encryption attribute of files 520-522 is created by users separately. In one embodiment, segments of an important part of file 521 such as, for example: a credit card number, a patient's name, etc., are encrypted. In one embodiment, segments from the header of file 504 are encrypted so that file 504 can not be decoded/read properly based on the encoding information in the header.
FIG. 6 is a block diagram of one embodiment of a cryptography system. Referring to FIG. 6, in one embodiment, a cryptography system comprises controller 600, encryption attribute logic 601, file segmenting logic 603, encryption engine using FEK 610, encryption engine using public keys 611, decryption engine using FEK 630, decryption engine using private keys 631, and FEK key generator 606. In one embodiment, storage drive 620 and non-volatile disk 621 stores the files operated on by the cryptography system. In one embodiment, storage drive 620 and non-volatile disk 621 are managed by controller 600. In one embodiment, controller 600 runs an operating system with services to manage storage drive 620 and non-volatile disk 621.
In one embodiment, controller 600 receives a file to encrypt. Encryption attribute logic 601 accesses the encryption attribute of the file. In one embodiment, encryption attribute logic 601 assigns an encryption attribute to a file based on the file type. In one embodiment, an encryption attribute is stored in association with the file. Encryption attribute logic 601 determines which segments of a file to encrypt based on the information in the encryption attribute.
In one embodiment, file segmenting logic 603 segments the file into a plurality of segments. Each segment is M-bit in length corresponds to one of the block sizes of encryption engine using FEK 610. Encryption engine using FEK 610 encrypts the segments identified by encryption attribute logic 601 in conjunction with file segmenting logic 603. In one embodiment, encryption engine using FEK 610 is an M-bit encryption engine implementing symmetric cryptography algorithms. In one embodiment, encryption engine using public keys 611 encrypts the encryption attribute and the FEK with a public key. In one embodiment, encryption engine using public keys 611 performs asymmetric cryptography algorithms.
In one embodiment, controller 600 stores the partly encrypted data, the encrypted encryption attribute and the encrypted FEK to a file on storage drive 620. In one embodiment, controller 600 stores the partly encrypted data, the encrypted encryption attribute, the encrypted FEK, or the combinations thereof to different locations (of a file system) that are associated to each others by the file system.
In one embodiment, controller 600 receives a file to decrypt. The file includes a partly encrypted file, an encrypted encryption attribute associated with the file, and an encrypted FEK. In one embodiment, decryption engine using private keys 631 decrypts the encrypted encryption attribute and the encrypted FEK with a private key to generate an encryption attribute and an FEK respectively. In one embodiment, decryption engine using private keys 631 performs asymmetric cryptography algorithms.
In one embodiment, encryption attribute logic 601 determines which segments of the partly encrypted file to decrypt based on the information in encryption attribute. In one embodiment, file segmenting logic 603 segments the partly encrypted file into a plurality of segments. Each segment is M-bit in length corresponds to one of the block sizes of decryption engine using FEK 630. Decryption engine using FEK 630 decrypts the segments identified by encryption attribute logic 601 in conjunction with file segmenting logic 603. In one embodiment, decryption engine using FEK 630 is an M-bit decryption engine implementing symmetric cryptography algorithms
In one embodiment, controller 600 stores the decrypted file, the encryption attribute, and the FEK to a file on storage drive 620. In one embodiment, controller 600 stores the decrypted file, the encryption attribute, the FEK, or the combinations thereof to different locations (of a file system) that are associated to each others by the file system.
In one embodiment, FEK key generator 606 generates a series of keys based on the initial FEK for different rounds in encryption engine using FEK 610 and decryption engine using FEK 630.
Although described herein as processing logic, each logic unit, each encryption engine, and each decryption engine can be implemented independently, separately or externally in different combinations. Embodiments of the invention may be implemented in a variety of electronic devices and logic circuits. Furthermore, devices or circuits that include embodiments of the invention may be included within a variety of computer systems. Embodiments of the invention may also be included in other computer system topologies and architectures.
FIG. 7 illustrates a computer system in which one embodiment of the invention may be used. A processor 705 accesses data from a level 1 (L1) cache memory 706, a level 2 (L2) cache memory 710, and main memory 715. In other embodiments of the invention, the cache memory 706 may be a multi-level cache memory comprise of an L1 cache together with other memory such as an L2 cache within a computer system memory hierarchy and cache memory 710 are the subsequent lower level cache memory such as an L3 cache or more multi-level cache. Furthermore, in other embodiments, the computer system may have the cache memory 710 as a shared cache for more than one processor core.
The processor 705 may have any number of processing cores. Other embodiments of the invention, however, may be implemented within other devices within the system or distributed throughout the system in hardware, software, or some combination thereof.
In one embodiment, main memory 715 loads operating system 750 to provide a file system via application programming interfaces (APIs). The file system connects through a device driver to communicate with solid state disk 725, HDD 720, or both. In one embodiment, main memory 715 loads an application program that interfaces with operating system 750 and the file system through APIs. The file system connects through a device driver to communicate with solid state disk 725 or HDD 720 to manage the files thereon. In one embodiment, the file system contains methods for (1) storing, referencing, sharing, and securing files, (2) accessing file data, and (3) maintaining file integrity. Notwithstanding, there is not always a clear distinction between a file system and its associated operating system, particularly with those file systems contained within an operating system.
The main memory 715 may be implemented in various memory sources, such as dynamic random-access memory (DRAM), a hard disk drive (HDD) 720, a solid state disk 725 based on NVRAM technology, or a memory source located remotely from the computer system via network interface 730 or via wireless interface 740 containing various storage devices and technologies. The cache memory may be located either within the processor or in close proximity to the processor, such as on the processor's local bus 707. Furthermore, the cache memory may contain relatively fast memory cells, such as a six-transistor (6T) cell, or other memory cell of approximately equal or faster access speed.
Other embodiments of the invention, however, may exist in other circuits, logic units, or devices within the system of FIG. 7. Furthermore, in other embodiments of the invention may be distributed throughout several circuits, logic units, or devices illustrated in FIG. 7.
Whereas many alterations and modifications of the present invention will no doubt become apparent to a person of ordinary skill in the art after having read the foregoing description, it is to be understood that any particular embodiment shown and described by way of illustration is in no way intended to be considered limiting. Therefore, references to details of various embodiments are not intended to limit the scope of the claims which in themselves recite only those features regarded as essential to the invention.

Claims

1-54. (canceled)

55. A method comprising:

encrypting one or more segments of first data with a first key, and lowering overall encryption time by selectively encrypting the one or more segments of a plurality of segments of the first data associated with an encryption attribute, wherein the encryption attribute to identify the one or more segments of the plurality of segments based on one or more rules describing each of the one or more segments as candidates for encryption;

encrypting the encryption attribute with a second key to create an encrypted encryption attribute; and

storing at least a part of second data, wherein the second data includes partly encrypted data and the encrypted encryption attribute.

56. The method of claim 55, further comprising encrypting the first key via the second key, wherein the second data further includes an encrypted version of the first key, wherein the first key includes a symmetric encryption key, and the second key includes a public key.

57. The method of claim 55, wherein the one or more segments of the plurality of segments are further based on a set of numbers corresponding to the one or more segments, an identifier corresponding to the one or more rules, and a pointer to a location storing the one or more rules.

58. The method of claim 55, wherein the encryption attribute is based on a file type of the data or a categorization of the data, and wherein the encryption attribute comprises a user-defined attribute or a default setting that is modifiable by a user, wherein the encryption attribute is associated with a file to identify the two or more segments of the file that are to be subsequently encrypted during the encryption process, wherein the encryption attribute is set to a setting based on a category or a file type to protect unauthorized usages such that the two or more segments include one or more of headers of the file, segments of important parts of the file, and alternate N segments of the file.

59. The method of claim 55, wherein each segment of the plurality of segments is M-bit in length such that the length is equal to one of block sizes of an M-bit encryption engine, and wherein each segment is processed by the M-bit encryption engine.

60. At least one machine-readable medium comprising instructions which, when accessed by a processing device, causes the processing device to perform one or more operations comprising:

61. The machine-readable medium of claim 60, wherein the one or more operations further comprise encrypting the first key via the second key, wherein the second data further includes an encrypted version of the first key, wherein the first key includes a symmetric encryption key, and the second key includes a public key.

62. The machine-readable medium of claim 60, wherein the one or more segments of the plurality of segments are further based on a set of numbers corresponding to the one or more segments, an identifier corresponding to the one or more rules, and a pointer to a location storing the one or more rules.

63. The machine-readable medium of claim 60, wherein the encryption attribute is based on a file type of the data or a categorization of the data, and wherein the encryption attribute comprises a user-defined attribute or a default setting that is modifiable by a user, wherein the encryption attribute is associated with a file to identify the two or more segments of the file that are to be subsequently encrypted during the encryption process,

64. The machine-readable medium of claim 63, wherein the encryption attribute is set to a setting based on a category or a file type to protect unauthorized usages such that the two or more segments include one or more of headers of the file, segments of important parts of the file, and alternate N segments of the file.

65. The machine-readable medium of claim 60, wherein each segment of the plurality of segments is M-bit in length such that the length is equal to one of block sizes of an M-bit encryption engine, and wherein each segment is processed by the M-bit encryption engine, and

wherein the one or more segments comprise at least one segment of N segments of partly encrypted data, wherein N represents a positive integer.

66. The machine-readable medium of claim 60, wherein the one or more operations further comprise receiving a request to encrypt the first data, wherein the first data includes the plurality of segments.

67. A system comprising:

a first encryption engine to encrypt one or more segments of first data with a first key, and lowering overall encryption time by selectively encrypting the one or more segments of a plurality of segments of the first data associated with an encryption attribute, wherein the encryption attribute to identify the one or more segments of the plurality of segments based on one or more rules describing each of the one or more segments as candidates for encryption;

a second encryption engine to encrypt the encryption attribute with a second key to create an encrypted encryption attribute; and

a storage medium to store at least a part of second data, wherein the second data includes partly encrypted data and the encrypted encryption attribute.

68. The system of claim 67, further comprises a third encryption engine to encrypt the first key via the second key, wherein the second data further includes an encrypted version of the first key, wherein the first key includes a symmetric encryption key, and the second key includes a public key.

69. The system of claim 67, wherein the one or more segments of the plurality of segments are further based on a set of numbers corresponding to the one or more segments, an identifier corresponding to the one or more rules, and a pointer to a location storing the one or more rules.

70. The system of claim 67, wherein the encryption attribute is based on a file type of the data or a categorization of the data, and wherein the encryption attribute comprises a user-defined attribute or a default setting that is modifiable by a user, wherein the encryption attribute is associated with a file to identify the two or more segments of the file that are to be subsequently encrypted during the encryption process,

71. The system of claim 70, wherein the encryption attribute is set to a setting based on a category or a file type to protect unauthorized usages such that the two or more segments include one or more of headers of the file, segments of important parts of the file, and alternate N segments of the file.

72. The system of claim 67, wherein each segment of the plurality of segments is M-bit in length such that the length is equal to one of block sizes of an M-bit encryption engine, and wherein each segment is processed by the M-bit encryption engine, and

73. The system of claim 67, further comprising a controller to receive a request to encrypt the first data, wherein the first data includes the plurality of segments.

74. A system comprising:

a first decryption engine to decrypt one or more segments of first data with a first key, the first data including an encrypted encryption attribute, wherein the encryption attribute to identify the one or more segments of the plurality of segments based on one or more rules describing each of the one or more segments as candidates for encryption; and

a second decryption engine to decrypt the encryption attribute with a second key to create an encrypted encryption attribute.

75. The system of claim 74, further comprising a controller to access the first data with the first key, the first data including a plurality of segments having the one or more segments.

76. The system of claim 74, further comprising a third decryption engine to decrypt an encryption version of a second key with the first key, wherein the first data further includes the second key, wherein the second key includes a symmetric encryption key, and the first key includes a private key.

77. The system of claim 74, wherein the one or more segments comprise at least one segment of N segments of partly encrypted data, wherein N represents a positive integer.