WO2009018481A1 - Multi-level key manager - Google Patents
Multi-level key manager Download PDFInfo
- Publication number
- WO2009018481A1 WO2009018481A1 PCT/US2008/071821 US2008071821W WO2009018481A1 WO 2009018481 A1 WO2009018481 A1 WO 2009018481A1 US 2008071821 W US2008071821 W US 2008071821W WO 2009018481 A1 WO2009018481 A1 WO 2009018481A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- key
- keys
- classification
- cryptographic
- processing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/105—Multiple levels of security
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
- G06F21/72—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information in cryptographic circuits
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
- G06F21/74—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information operating in dual or compartmented mode, i.e. at least one secure mode
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2113—Multi-level security, e.g. mandatory access control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0485—Networking architectures for enhanced packet encryption processing, e.g. offloading of IPsec packet processing or efficient security association look-up
Definitions
- This disclosure relates in general to secure computing systems and, more specifically to high-assurance access to keys at different classification levels amongst other things.
- a cryptographic device and method for processing different levels of classified information.
- a memory caches keys for use in a cryptographic processor.
- the cryptographic processor requests a key associated with a particular classification level when processing a packet of the particular classification level.
- the cryptographic device confirms that the key and the packet are of the same classification level in a high-assurance manner. Checking header information of the keys one or more times is performed in one embodiment. Some embodiments authenticate the stored key in a high-assurance manner prior to providing the key to the cryptographic device.
- a cryptographic device for processing classified information having a number of different classification levels.
- the cryptographic device includes a memory, a cryptographic processor and a key manager.
- the memory holds a number of keys outside of an integrated circuit, The plurality of keys are for the plurality of different classification levels.
- the cryptographic processor is part of the integrated circuit and uses the plurality of keys to process packets of information that are categorized according to the number of different classification levels.
- the key manager can access a plurality of rules associated with the plurality of different classification levels that regulate interaction with the plurality of keys. A first rule of the number of rules is used by the key manager in a first classification level of the number of different classification levels.
- a second rule of the number of rules is used by the key manager in a second classification level of the number of different classification levels.
- a method for processing classified information in a high- assurance manner is disclosed.
- a request is received for a first key by a cryptographic processor.
- a first rule from a number of rules is applied to a first sterile key retrieved from a memory.
- the first sterile key is decrypted with a first protection key to produce the first key.
- the first key is also checked with the first rule.
- the first key is provided to the cryptographic processor if the checking the first sterile key step and the checking the first key step are completed successfully.
- a request is received for a second key by the cryptographic processor.
- a second rule from the number of rules is applied to a second sterile key retrieved from the memory.
- the second sterile key is decrypted with a second protection key to produce the second key.
- the second key is also checked with the second rule.
- the second key is provided to the cryptographic processor if the checking the second sterile key step and the checking the second key step are completed successfully.
- a cryptographic device for processing information with a plurality of classification levels.
- the cryptographic device includes a memory, a cryptographic processor and a key manager.
- the memory holds a number of keys that are used by a cryptographic processor to process packets of information that are correlated to the plurality of classification levels.
- the key manager includes a rule enforcement circuit and a key decryption circuit.
- the key manager retrieves a first key for a first packet being processed by the cryptographic processor.
- the first packet and the first key are of a first classification level.
- the rule enforcement circuit checks that the first key is designated for the first classification level before providing the first key to the cryptographic processor for processing the first packet.
- the key manager retrieves a second key for a second packet being processed by the cryptographic processor.
- the second packet and the second key are of a second classification level.
- the rule enforcement circuit checks that the second key is designated for the second classification level before providing the second key to the cryptographic processor for processing the second packet.
- FIG. 1 depicts a block diagram of an embodiment of a cryptographic device
- FIG. 2 depicts a block diagram of an embodiment of a partitioned key cache
- FIG. 3 depicts a block diagram of an embodiment of a key manager
- FIG. 4 depicts a diagram of an embodiment of a key unscrambling process
- FIG. 5 illustrates a flowchart of an embodiment of a process for operating the cryptographic device.
- FIG. 1 a block diagram of an embodiment of a cryptographic device 100 is shown.
- the cryptographic device 100 processes information of different classifications. Information in each classification level is kept separate or partitioned from information of other classification levels throughout the cryptographic device 100.
- each classification level can use different cryptographic algorithms and/or keys.
- Several integrated circuits could be used to implement the cryptographic device 100 where at least a cryptographic processor 120 is in one integrated circuit and the partitioned key cache 116 is in another. Other embodiments could have the partitioned key cache 116 and cryptographic processor 120 as part of the same integrated circuit.
- a cryptographic processor 120 is the circuit that performs encryption, decryption and/or bypass for the information that passes through it.
- Information may be a stream or packetized in cryptographic processor 120.
- the packets or streams are of different classification levels.
- the cryptographic processor 120 can reconfigure itself for the appropriate processing on a packet-by-packet basis. Different processing steps are set up for each classification level in a pipeline fashion by the cryptographic processor 120.
- the processing steps perform formatting and cryptographic processing with a number of different algorithms and/or keys. Some of these processing steps can be common to multiple classification levels such that the cryptographic processor 120 can potentially reuse the sub-circuits performing processing steps for the multiple classification levels.
- a system bus 124 allows the processor 108 to communicate with a key manager 104, a partitioned key cache 116, an input/output (IO) access controller 112, and other peripherals that are not shown in the figure.
- the processor 108 communicates with the key manager 104, via the IO access controller 112, to access the partitioned key cache 116. Keys are loaded into the partitioned key cache 116 by the processor 104 in this embodiment and read by the cryptographic processor 120. Other embodiments could load the keys from an external source, for example.
- the IO access controller 112 checks that the processor 108 or anything else using the system bus 124 is operating as expected.
- the processor 108 writes a state to the IO access controller 112.
- Each state is able to access peripherals defined by addresses or ranges of addresses.
- the IO access controller 112 checks that only the designated addresses are accessed by the processor 108 in a given state to assure that the interaction with the key manager 104 and partitioned key cache 116 to write keys is authorized.
- Each address or range of addresses can be designated for read only, write only or read and write accessible.
- the IO access controller 112 further understands how states transition through the state machine such that state transitions are also checked when the processor 108 is using the system bus 124.
- the cryptographic processor 120 performs certain key operations in certain states.
- the IO access controller 112 checks if an address range of a partitioned key cache 116 has been properly written by the processor based upon the current state.
- Table I gives an example of the states used for various classification levels. Additionally, the algorithm and key address is given in the table. These entries in the table serve as rules. For example, states four, seven and nine operate in a CONFIDENTIAL classification level using a DES cryptographic algorithm and the key at address forty-three in the partitioned key cache.
- the IO access controller 112 in this example would make sure the current states were one of states four, seven or nine when the processor 108 writes the key at address forty-three in the partitioned key cache 116. Where a violation were determined the IO access controller 112, the key could be zeroized and/or other remedial action could be taken.
- the partitioned key cache 116 holds keys in a sterile or encrypted form. Sterilization puts the keys in a form that protects the encapsulated key even if recovered improperly. Various encryption algorithms could be used for sterilizing the keys.
- a key manager 104 is capable of deriving the key from the sterilized version.
- the partitioned key cache 116 could use dynamic random access memory (DRAM) or static random access memory (SRAM). This embodiment uses volatile RAM for the partitioned key cache 116 that is in a separate integrated circuit, but could be integral with the integrated circuit of the key manager 104 and/or cryptographic processor 120.
- the partitioned key cache 116 could be a segment of a larger memory used for other purposes in other embodiments.
- a key manager 104 receives requests from the cryptographic processor 120 for keys used to process the various packets.
- the key manager 104 checks the requests, retrieves the sterilized key, reconstitutes the key, performs checks, and returns the key to the cryptographic processor 120.
- the key manager 104 is implemented in logic that is not reprogrammable during normal operation.
- the processor 108 interacts with the key manager 104 under the supervision of the IO access controller 112.
- FIG. 2 a block diagram of an embodiment of a partitioned key cache 116 is shown.
- the partitioned key cache 116 has a number of partitions 204 defined. Those partitions map to peripherals or address ranges used by the IO access controller 112.
- a given classification level stores its keys in one partition 204 and is prevented from accessing other partitions 204.
- the partitioned key cache 116 is a single integrated circuit with a common interface in this embodiment, the partitioning enforces a logical separation in a high-assurance manner.
- Table II gives an example of the mapping between state, classification and partition 204. These mappings serve as rules. For example, state one operates at a TOP SECRET classification level and has access to partition B 204-2, which includes addresses eleven through twenty.
- FIG. 3 a block diagram of an embodiment of a key manager 104 is shown, hi a high-assurance manner, the key manager enforces logical separation of the partitioned key cache 116 where no physical separation of the interface to the partitioned key cache 116 exists.
- a key request interface 332 is coupled to the cryptographic processor 120 to receive requests for one or more particular key located at specified addresses in the partitioned key cache 116.
- This embodiment includes a request validator 336 that checks the request to make sure the request is formatted correctly.
- Other embodiments of the request validator 336 could check that the classification level of the requesting packet matches the classification level of the partition 204 of the requested key.
- a key memory interface 132 couples to the partitioned key cache 116 to retrieve the requested key. The sterile key is returned to a key buffer 308.
- a rule enforcement circuit 336 includes a sterile key validator 304, a key decoder 324 and a reconstituted key validator 328. Multiple levels of checks are performed on the key before the key is provided to the cryptographic processor 120. [0027]
- the sterile key validator 304 checks the classification level of the sterile key against the classification level of the packet that precipitated the request of the key. Essentially, the sterile key is checked to make sure it matches the type of processing being performed in the cryptographic processor 120 to provide high-assurance.
- the sterile key validator 304 could also match the algorithm and/or state as further rule checks in some embodiments.
- a CRC, checksum or other validity value is appended to the sterile key in this embodiment when stored in the partitioned key cache 116.
- the software determines the validity value when writing the sterile key into the partitioned key cache 116.
- a check of the validity value allows conformation that information stored by the processor 108 was delivered accurately to the sterile key validator 304.
- a key map database 316 holds information to validate the keys in their sterile or reconstituted form.
- the state, classification, address, algorithm, key length, header information, and/or other information could be stored in the key map database 316.
- a look- up table is used in one embodiment of the key map database 316. Where several keys are used for a given classification level, the finer granularity of state can confirm that the key is the correct one for a particular situation. For example, there could be a different state for each key. Other embodiments could provide granularity using two or more partitions 204 for a particular classification level.
- a key decoder 324 converts the sterilized key from the partitioned key cache 116 into a reconstituted key that is ready for use by the cryptographic processor 120.
- a payload of the sterilized key is decrypted to produce a reconstituted key.
- a cache protection key store 320 holds a cache protection key for each classification level. Table III shows an example of the information stored in the cache protection key store 320. Other embodiments could have a different cache protection key for each sterilized key or one cache protection key for all keys.
- a sterile key 416 includes a sterile key header, a sterile key payload and a sterile key CRC, which serves as a validity value. All this information is stored in the partitioned key cache 116 by the processor 108.
- the sterile key header holds the classification level, the applicable encryption algorithm(s), and any additional key identifiers. Some embodiments may also include the memory address of the sterile key.
- the sterile key CRC is a validity value that is calculated on the whole sterile key header and sterile key payload such that any corruption can be discerned.
- the sterile key payload is exclusive-ORed 324 with a cache protection key 420 from the cache protection key store 320 to decrypt the reconstituted key header, reconstituted key payload and reconstituted key CRC. Those items along with the sterile key header and sterile key CRC form the reconstituted key 404.
- the reconstituted key payload is the actual key that will be used by the cryptographic processor 120.
- the reconstituted key CRC is a validity value that allows checking that the fields of the reconstituted key 404 has not changed.
- the exclusive-OR key decoder 324 is just one example of a simple decryption function. Other embodiments may use any type of decryption function(s).
- FIG. 5 a flowchart of an embodiment of a process 500 for operating the cryptographic device 100 is shown.
- the depicted portion of the process is initiated in block 504 where the cryptographic processor 120 has a packet that uses a particular key, which is requested from the key manager 104. Some embodiments check the key request. In any event, the key is requested from the partitioned key cache 116 by the key manager 104. The address of the key requested falls within a particular partition 204.
- the sterile key 416 is retrieved in block 516 from the partitioned key cache 116 in block 516.
- the sterile key header is checked in block 520 to determine if the classification matches the classification of the packet requesting the key. Additional checks are possible, for example, the sterile key CRC or validity value could be checked. Presuming the check in block 520 is successful, processing continues to block 524 where the sterile key payload is decrypted.
- the reconstituted key header is checked in block 528. Prior to the decoding block 524, the reconstituted key header was scrambled. Additionally, a reconstituted key CRC or validity value can be checked in some embodiments. If the check in block 528 passes, processing continues to block 532 where the key is returned the cryptographic processor 120.
- the partitioned key cache 116 is erased and/or the cache protection key store 320 in block 536. Without the cache protection keys, the keys remain in a sterile form. Erasure of the cache protection keys can typically be performed much more quickly than the partitioned key cache 116. Further remedial action can be taken in block 540.
- classification levels could be government classification levels, but need not be necessarily so.
- a classification level is just a logical partition in the information passed. Any information that needs to be kept separate from other information could be in a separate classification level or logical partition.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Computing Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Storage Device Security (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
A cryptographic device and method are disclosed for processing different levels of classified information. A memory caches keys for use in a cryptographic processor. The cryptographic processor requests a key associated with a particular classification level when processing a packet of the particular classification level. The cryptographic device confirms that the key and the packet are of the same classification level in a high-assurance manner. Checking header information of the keys one or more times is performed in one embodiment. Some embodiments authenticate the stored key in a high-assurance manner prior to providing the key to the cryptographic device.
Description
MULTI-LEVEL KEY MANAGER
CROSS-REFERENCES TO RELATED APPLICATIONS
[0001] This application claims the benefit of and is a non-provisional of co-pending: US Provisional Application Serial No. 60/962,848 filed on July 31, 2007; US Provisional Application Serial No. 61/026,438 filed on February 5, 2008; US Provisional Application Serial No. 60/962,821 filed on July 31, 2007; and US Provisional Application Serial No. 60/962,822 filed on July 31, 2007; which are all hereby expressly incorporated by reference in their entirety for all purposes.
[0002] This application expressly incorporates by reference: US Application Serial No. , filed on an even day herewith, entitled "INPUT OUTPUT ACCES S
CONTROLLER" (temporarily referenced by Attorney Docket No. 017018-017210US/VS-
0245); and, US Application Serial No. , filed on an even day herewith, entitled "TRUSTED LABELER" (temporarily referenced by Attorney Docket No. 017018- 014610US/VS-0246); in their entirety for all purposes.
BACKGROUND
[0003] This disclosure relates in general to secure computing systems and, more specifically to high-assurance access to keys at different classification levels amongst other things.
[0004] Governments classify information at different levels generally according to their sensitivity, for example, SECRET versus TOP SECRET. Users of the information are also classified by what level they are able to get access to. For example, someone with a SECRET clearance is not given access to TOP SECRET information. Procedures are put in place to avoid exposure to persons without the proper classification level.
[0005] In processing systems, physical security is used to prevent information of different classification levels from bleeding over to a different classification level. To process at multiple classification levels, there may be several devices running in parallel for each classification level. Devices that may be capable of running at multiple classification levels are run at one classification level, cleared out and then run at a different classification level. Intermixing of different classified information is generally taboo in these systems.
[0006] There are situations that require smaller cryptographic devices that can process different classification levels. Switching between classification levels takes time and slows down processing. Some have proposed trusted operating systems that can process information with more flexibility, but these solutions are avoided due to a lack of trust. [0007] Different keys are required for each classification level to maintain the security of information in each classification level. The keys may be simply different values or could be used with different algorithms. Even if security is breached for one classification level, the unique keys and algorithms can keep information protected in the other classification levels safe.
SUMMARY
[0008] In an embodiment, a cryptographic device and method are disclosed for processing different levels of classified information. A memory caches keys for use in a cryptographic processor. The cryptographic processor requests a key associated with a particular classification level when processing a packet of the particular classification level. The cryptographic device confirms that the key and the packet are of the same classification level in a high-assurance manner. Checking header information of the keys one or more times is performed in one embodiment. Some embodiments authenticate the stored key in a high-assurance manner prior to providing the key to the cryptographic device.
[0009] In one embodiment, a cryptographic device for processing classified information having a number of different classification levels is disclosed. The cryptographic device includes a memory, a cryptographic processor and a key manager. The memory holds a number of keys outside of an integrated circuit, The plurality of keys are for the plurality of different classification levels. The cryptographic processor is part of the integrated circuit and uses the plurality of keys to process packets of information that are categorized according to the number of different classification levels. The key manager can access a plurality of rules associated with the plurality of different classification levels that regulate interaction with the plurality of keys. A first rule of the number of rules is used by the key manager in a first classification level of the number of different classification levels. A second rule of the number of rules is used by the key manager in a second classification level of the number of different classification levels.
[0010] In another embodiment, a method for processing classified information in a high- assurance manner is disclosed. In one step, a request is received for a first key by a cryptographic processor. A first rule from a number of rules is applied to a first sterile key retrieved from a memory. The first sterile key is decrypted with a first protection key to produce the first key. The first key is also checked with the first rule. The first key is provided to the cryptographic processor if the checking the first sterile key step and the checking the first key step are completed successfully. A request is received for a second key by the cryptographic processor. A second rule from the number of rules is applied to a second sterile key retrieved from the memory. The second sterile key is decrypted with a second protection key to produce the second key. The second key is also checked with the second rule. The second key is provided to the cryptographic processor if the checking the second sterile key step and the checking the second key step are completed successfully.
[0011] In yet another embodiment, a cryptographic device for processing information with a plurality of classification levels is disclosed. The cryptographic device includes a memory, a cryptographic processor and a key manager. The memory holds a number of keys that are used by a cryptographic processor to process packets of information that are correlated to the plurality of classification levels. The key manager includes a rule enforcement circuit and a key decryption circuit. The key manager retrieves a first key for a first packet being processed by the cryptographic processor. The first packet and the first key are of a first classification level. The rule enforcement circuit checks that the first key is designated for the first classification level before providing the first key to the cryptographic processor for processing the first packet. The key manager retrieves a second key for a second packet being processed by the cryptographic processor. The second packet and the second key are of a second classification level. The rule enforcement circuit checks that the second key is designated for the second classification level before providing the second key to the cryptographic processor for processing the second packet.
[0012] Further areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples, while indicating various embodiments, are intended for purposes of illustration only and are not intended to necessarily limit the scope of the disclosure.
BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The present disclosure is described in conjunction with the appended figures: FIG. 1 depicts a block diagram of an embodiment of a cryptographic device; FIG. 2 depicts a block diagram of an embodiment of a partitioned key cache; FIG. 3 depicts a block diagram of an embodiment of a key manager;
FIG. 4 depicts a diagram of an embodiment of a key unscrambling process; and FIG. 5 illustrates a flowchart of an embodiment of a process for operating the cryptographic device.
[0014] In the appended figures, similar components and/or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.
DETAILED DESCRIPTION
[0015] The ensuing description provides preferred exemplary embodiment(s) only, and is not intended to limit the scope, applicability or configuration of the disclosure. Rather, the ensuing description of the preferred exemplary embodiment(s) will provide those skilled in the art with an enabling description for implementing a preferred exemplary embodiment. It being understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope as set forth in the appended claims.
[0016] Referring first to FIG. 1, a block diagram of an embodiment of a cryptographic device 100 is shown. The cryptographic device 100 processes information of different classifications. Information in each classification level is kept separate or partitioned from information of other classification levels throughout the cryptographic device 100.
Additionally, each classification level can use different cryptographic algorithms and/or keys. Several integrated circuits could be used to implement the cryptographic device 100 where at least a cryptographic processor 120 is in one integrated circuit and the partitioned key cache 116 is in another. Other embodiments could have the partitioned key cache 116 and cryptographic processor 120 as part of the same integrated circuit.
[0017] A cryptographic processor 120 is the circuit that performs encryption, decryption and/or bypass for the information that passes through it. Information may be a stream or
packetized in cryptographic processor 120. The packets or streams are of different classification levels. The cryptographic processor 120 can reconfigure itself for the appropriate processing on a packet-by-packet basis. Different processing steps are set up for each classification level in a pipeline fashion by the cryptographic processor 120. The processing steps perform formatting and cryptographic processing with a number of different algorithms and/or keys. Some of these processing steps can be common to multiple classification levels such that the cryptographic processor 120 can potentially reuse the sub-circuits performing processing steps for the multiple classification levels.
[0018] A system bus 124 allows the processor 108 to communicate with a key manager 104, a partitioned key cache 116, an input/output (IO) access controller 112, and other peripherals that are not shown in the figure. The processor 108 communicates with the key manager 104, via the IO access controller 112, to access the partitioned key cache 116. Keys are loaded into the partitioned key cache 116 by the processor 104 in this embodiment and read by the cryptographic processor 120. Other embodiments could load the keys from an external source, for example.
[0019] The IO access controller 112 checks that the processor 108 or anything else using the system bus 124 is operating as expected. The processor 108 writes a state to the IO access controller 112. Each state is able to access peripherals defined by addresses or ranges of addresses. The IO access controller 112 checks that only the designated addresses are accessed by the processor 108 in a given state to assure that the interaction with the key manager 104 and partitioned key cache 116 to write keys is authorized. Each address or range of addresses can be designated for read only, write only or read and write accessible. The IO access controller 112 further understands how states transition through the state machine such that state transitions are also checked when the processor 108 is using the system bus 124.
[0020] There are states defined exclusive to the various classification levels. The cryptographic processor 120 performs certain key operations in certain states. The IO access controller 112 checks if an address range of a partitioned key cache 116 has been properly written by the processor based upon the current state. Table I gives an example of the states used for various classification levels. Additionally, the algorithm and key address is given in the table. These entries in the table serve as rules. For example, states four, seven and nine operate in a CONFIDENTIAL classification level using a DES
cryptographic algorithm and the key at address forty-three in the partitioned key cache. The IO access controller 112 in this example would make sure the current states were one of states four, seven or nine when the processor 108 writes the key at address forty-three in the partitioned key cache 116. Where a violation were determined the IO access controller 112, the key could be zeroized and/or other remedial action could be taken.
Table I. State Enforcement Rules
State(s) Classification Algorithm Key Address
1 TS AES 256 11
2, 19 S AES 196 5
3, 21 NC Triple DES 21
4, 7, 9 C DES 43
[0021] As a packet passes through the cryptographic processor 120 certain algorithms use keys to perform the desired processing for that packet. The partitioned key cache 116 holds keys in a sterile or encrypted form. Sterilization puts the keys in a form that protects the encapsulated key even if recovered improperly. Various encryption algorithms could be used for sterilizing the keys. A key manager 104 is capable of deriving the key from the sterilized version. The partitioned key cache 116 could use dynamic random access memory (DRAM) or static random access memory (SRAM). This embodiment uses volatile RAM for the partitioned key cache 116 that is in a separate integrated circuit, but could be integral with the integrated circuit of the key manager 104 and/or cryptographic processor 120. The partitioned key cache 116 could be a segment of a larger memory used for other purposes in other embodiments.
[0022] A key manager 104 receives requests from the cryptographic processor 120 for keys used to process the various packets. The key manager 104 checks the requests, retrieves the sterilized key, reconstitutes the key, performs checks, and returns the key to the cryptographic processor 120. The key manager 104 is implemented in logic that is not reprogrammable during normal operation. To load keys into the partition key cache 116, the processor 108 interacts with the key manager 104 under the supervision of the IO access controller 112. [0023] With reference to FIG. 2, a block diagram of an embodiment of a partitioned key cache 116 is shown. The partitioned key cache 116 has a number of partitions 204 defined.
Those partitions map to peripherals or address ranges used by the IO access controller 112. A given classification level stores its keys in one partition 204 and is prevented from accessing other partitions 204. Although the partitioned key cache 116 is a single integrated circuit with a common interface in this embodiment, the partitioning enforces a logical separation in a high-assurance manner. Table II gives an example of the mapping between state, classification and partition 204. These mappings serve as rules. For example, state one operates at a TOP SECRET classification level and has access to partition B 204-2, which includes addresses eleven through twenty.
Table II. State to Partition Mapping
State(s) Classification Partition Addresses
1 TS 11-20
2, 19 S 1-10
3, 21 NC 21-30
4, 7, 9 C 31-45
[0024] Referring next to FIG. 3, a block diagram of an embodiment of a key manager 104 is shown, hi a high-assurance manner, the key manager enforces logical separation of the partitioned key cache 116 where no physical separation of the interface to the partitioned key cache 116 exists. A key request interface 332 is coupled to the cryptographic processor 120 to receive requests for one or more particular key located at specified addresses in the partitioned key cache 116.
[0025] This embodiment includes a request validator 336 that checks the request to make sure the request is formatted correctly. Other embodiments of the request validator 336 could check that the classification level of the requesting packet matches the classification level of the partition 204 of the requested key. With a specified key location, a key memory interface 132 couples to the partitioned key cache 116 to retrieve the requested key. The sterile key is returned to a key buffer 308.
[0026] A rule enforcement circuit 336 includes a sterile key validator 304, a key decoder 324 and a reconstituted key validator 328. Multiple levels of checks are performed on the key before the key is provided to the cryptographic processor 120.
[0027] The sterile key validator 304 checks the classification level of the sterile key against the classification level of the packet that precipitated the request of the key. Essentially, the sterile key is checked to make sure it matches the type of processing being performed in the cryptographic processor 120 to provide high-assurance. The sterile key validator 304 could also match the algorithm and/or state as further rule checks in some embodiments.
[0028] A CRC, checksum or other validity value is appended to the sterile key in this embodiment when stored in the partitioned key cache 116. The software determines the validity value when writing the sterile key into the partitioned key cache 116. A check of the validity value allows conformation that information stored by the processor 108 was delivered accurately to the sterile key validator 304.
[0029] A key map database 316 holds information to validate the keys in their sterile or reconstituted form. The state, classification, address, algorithm, key length, header information, and/or other information could be stored in the key map database 316. A look- up table is used in one embodiment of the key map database 316. Where several keys are used for a given classification level, the finer granularity of state can confirm that the key is the correct one for a particular situation. For example, there could be a different state for each key. Other embodiments could provide granularity using two or more partitions 204 for a particular classification level. [0030] A key decoder 324 converts the sterilized key from the partitioned key cache 116 into a reconstituted key that is ready for use by the cryptographic processor 120. A payload of the sterilized key is decrypted to produce a reconstituted key. A cache protection key store 320 holds a cache protection key for each classification level. Table III shows an example of the information stored in the cache protection key store 320. Other embodiments could have a different cache protection key for each sterilized key or one cache protection key for all keys.
Table III. Cache Protection Keys
State(s ) Classification Random Key
1 TS 19A5E9F45609DC90h
2, 19 S AA5119A456870190h
3, 21 N 78A5E49B56A093D0h
4, 7, 9 C 15E456894309AE9F0h
[0031] Within the decrypted payload of the sterilized key is information that is checked by a reconstituted key validator 328. Additionally, a CRC, checksum or other validity value is embedded in the decrypted payload as a second validity value. The reconstituted key validator 328 also checks the second validity value. This additional check provides a further layer of high-assurance. Should the process pass all of its checks, the decrypted key is provide to the cryptographic processor 120 for use in processing the particular packet that requested the key.
[0032] With reference to FIG. 4, a diagram demonstrating an embodiment of a key unscrambling process 400 is shown. A sterile key 416 includes a sterile key header, a sterile key payload and a sterile key CRC, which serves as a validity value. All this information is stored in the partitioned key cache 116 by the processor 108. The sterile key header holds the classification level, the applicable encryption algorithm(s), and any additional key identifiers. Some embodiments may also include the memory address of the sterile key. The sterile key CRC is a validity value that is calculated on the whole sterile key header and sterile key payload such that any corruption can be discerned.
[0033] The sterile key payload is exclusive-ORed 324 with a cache protection key 420 from the cache protection key store 320 to decrypt the reconstituted key header, reconstituted key payload and reconstituted key CRC. Those items along with the sterile key header and sterile key CRC form the reconstituted key 404. The reconstituted key payload is the actual key that will be used by the cryptographic processor 120. The reconstituted key CRC is a validity value that allows checking that the fields of the reconstituted key 404 has not changed. The exclusive-OR key decoder 324 is just one example of a simple decryption function. Other embodiments may use any type of decryption function(s).
[0034] Referring next to FIG. 5, a flowchart of an embodiment of a process 500 for operating the cryptographic device 100 is shown. The depicted portion of the process is initiated in block 504 where the cryptographic processor 120 has a packet that uses a particular key, which is requested from the key manager 104. Some embodiments check the key request. In any event, the key is requested from the partitioned key cache 116 by the key manager 104. The address of the key requested falls within a particular partition 204.
[0035] The sterile key 416 is retrieved in block 516 from the partitioned key cache 116 in block 516. The sterile key header is checked in block 520 to determine if the classification matches the classification of the packet requesting the key. Additional checks are possible, for example, the sterile key CRC or validity value could be checked. Presuming the check in block 520 is successful, processing continues to block 524 where the sterile key payload is decrypted.
[0036] In the reconstituted key 404, the reconstituted key header is checked in block 528. Prior to the decoding block 524, the reconstituted key header was scrambled. Additionally, a reconstituted key CRC or validity value can be checked in some embodiments. If the check in block 528 passes, processing continues to block 532 where the key is returned the cryptographic processor 120.
[0037] Should any of the checks fail in blocks 520 or 528, the partitioned key cache 116 is erased and/or the cache protection key store 320 in block 536. Without the cache protection keys, the keys remain in a sterile form. Erasure of the cache protection keys can typically be performed much more quickly than the partitioned key cache 116. Further remedial action can be taken in block 540.
[0038] The above embodiments discuss processing at different classification levels. These classification levels could be government classification levels, but need not be necessarily so. A classification level is just a logical partition in the information passed. Any information that needs to be kept separate from other information could be in a separate classification level or logical partition.
[0039] While the principles of the disclosure have been described above in connection with specific apparatuses and methods, it is to be clearly understood that this description is made only by way of example and not as limitation on the scope of the disclosure.
Claims
CLAIMS WHAT IS CLAIMED IS: L A cryptographic device for processing classified information having a plurality of different classification levels, the cryptographic device comprising: a memory holding a plurality of keys outside of an integrated circuit, wherein the plurality of keys are for the plurality of different classification levels; a cryptographic processor that is part of the integrated circuit, wherein the cryptographic processor uses the plurality of keys to process packets of information that are categorized according to the plurality of different classification levels; and a key manager, wherein: the key manager can access a plurality of rules associated with the plurality of different classification levels, the plurality of rules regulate interaction with the plurality of keys, a first rule of the plurality of rules is used by the key manager in a first classification level of the plurality of different classification levels, and a second rule of the plurality of rules is used by the key manager in a second classification level of the plurality of different classification levels.
2. The cryptographic device for processing classified information having the plurality of different classification levels as recited in claim 1 , wherein: a first key accessed in the first classification level includes a header that is checked against the first rule, and the first key includes a coded header that is checked against the first rule.
3. The cryptographic device for processing classified information having the plurality of different classification levels as recited in claim 1 , wherein the first and second keys are encrypted in the memory.
4. The cryptographic device for processing classified information having the plurality of different classification levels as recited in claim 1 , wherein the plurality of keys are stored in an encrypted state.
5. The cryptographic device for processing classified information having the plurality of different classification levels as recited in claim 1 , wherein the key manager further comprises a key decoder, which decrypts the plurality of keys before passing them to the cryptographic processor.
6. The cryptographic device for processing classified information having the plurality of different classification levels as recited in claim 1, further comprising an access controller, wherein the access controller checks that a predetermined state of operation is active while writing the first key to a partition of the memory.
7. A method for processing classified information in a high-assurance manner, the method comprising steps of: receiving a request for a first key by a cryptographic processor; choosing a first rule from a plurality of rules; retrieving a first sterile key from a memory; checking the first sterile key with the first rule; decrypting the first sterile key with a first protection key to produce the first key; checking the first key with the first rule; providing the first key to the cryptographic processor if the checking the first sterile key step and the checking the first key step are completed successfully; receiving a request for a second key by a cryptographic processor; choosing a second rule from the plurality of rules; retrieving the second sterile key from the memory; checking the second sterile key with the second rule; decrypting the second sterile key with a second protection key to produce a second key; checking the second key with the second rule; and providing the second key to the cryptographic processor if the checking the second sterile key step and the checking the second key step are completed successfully.
8. The method for processing classified information in the high- assurance manner as recited in claim 7, further comprising a step of erasing the first and second protection keys to zeroize utility of the first and second keys.
9. The method for processing classified information in the high- assurance manner as recited in claim 7, wherein the cryptographic processor is capable of processing multiple classification levels simultaneously in different packets.
10. The method for processing classified information in the high- assurance manner as recited in claim 7, wherein the first rule requires a classification level of a packet being processed with the cryptographic processor to match the classification level of the first key.
11. The method for processing classified information in the high- assurance manner as recited in claim 7, wherein: the first and second sterile keys are stored in a second integrated circuit, and the decrypting steps are performed in a first integrated circuit.
12. A cryptographic device for processing information with a plurality of classification levels, the cryptographic device comprising: a memory holding a plurality of keys; a cryptographic processor that uses the plurality of keys to process packets of information that are correlated to the plurality of classification levels; and a key manager that comprises a rule enforcement circuit and a key decryption circuit, wherein: the key manager retrieves a first key for a first packet being processed by the cryptographic processor, the first packet is of a first classification level, the first key is associated with the first classification level, the rule enforcement circuit checks that the first key is designated for the first classification level before providing the first key to the cryptographic processor for processing the first packet, the key manager retrieves a second key for a second packet being processed by the cryptographic processor, the second packet is of a second classification level, the second key is associated with the second classification level, and the rule enforcement circuit checks that the second key is designated for the second classification level before providing the second key to the cryptographic processor for processing the second packet.
13. The cryptographic device for processing information with the plurality of classification levels as recited in claim 12, wherein at least one of the first and second keys are stored in the memory in an unusable form.
14. The cryptographic device for processing information with the plurality of classification levels as recited in claim 12, wherein the key manager further comprises a key decoder that descrambles the first key before providing the first key to the cryptographic processor.
15. The cryptographic device for processing information with the plurality of classification levels as recited in claim 12, wherein the memory and the cryptographic processor are in different integrated circuit.
16. The cryptographic device for processing information with the plurality of classification levels as recited in claim 12, wherein: the plurality of keys are divided among a plurality of partitions in the memory, and each classification level has a different partition to logically separate keys of different classification levels.
17. The cryptographic device for processing information with the plurality of classification levels as recited in claim 12, wherein the plurality of classification levels includes a plurality of protection values that are each used to descramble the plurality of keys.
18. The cryptographic device for processing information with the plurality of classification levels as recited in claim 12, wherein the rule enforcement circuit checks the first key twice to confirm that the first classification level of the key matches the first classification level of the packet.
19. The cryptographic device for processing information with the plurality of classification levels as recited in claim 12, wherein the first and second keys are decrypted in the key manager.
20. The cryptographic device for processing information with the plurality of classification levels as recited in claim 12, wherein a header is used to designate the first key for the first classification level.
Applications Claiming Priority (8)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US96282107P | 2007-07-31 | 2007-07-31 | |
| US96282207P | 2007-07-31 | 2007-07-31 | |
| US96284807P | 2007-07-31 | 2007-07-31 | |
| US60/962,848 | 2007-07-31 | ||
| US60/962,821 | 2007-07-31 | ||
| US60/962,822 | 2007-07-31 | ||
| US2643808P | 2008-02-05 | 2008-02-05 | |
| US61/026,438 | 2008-02-05 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2009018481A1 true WO2009018481A1 (en) | 2009-02-05 |
Family
ID=39832694
Family Applications (3)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/US2008/071823 Ceased WO2009018483A1 (en) | 2007-07-31 | 2008-07-31 | Input output access controller |
| PCT/US2008/071818 Ceased WO2009018479A1 (en) | 2007-07-31 | 2008-07-31 | Trusted labeler |
| PCT/US2008/071821 Ceased WO2009018481A1 (en) | 2007-07-31 | 2008-07-31 | Multi-level key manager |
Family Applications Before (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/US2008/071823 Ceased WO2009018483A1 (en) | 2007-07-31 | 2008-07-31 | Input output access controller |
| PCT/US2008/071818 Ceased WO2009018479A1 (en) | 2007-07-31 | 2008-07-31 | Trusted labeler |
Country Status (2)
| Country | Link |
|---|---|
| US (3) | US20090034734A1 (en) |
| WO (3) | WO2009018483A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8312292B2 (en) | 2007-07-31 | 2012-11-13 | Viasat, Inc. | Input output access controller |
| WO2018153559A1 (en) * | 2017-02-21 | 2018-08-30 | Siemens Aktiengesellschaft | Method and validation unit for controlling the loading of crypto keys, in particular "key blobs", usable in it systems, in particular embedded systems |
Families Citing this family (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7391865B2 (en) | 1999-09-20 | 2008-06-24 | Security First Corporation | Secure data parser method and system |
| CN101855860B (en) * | 2007-09-14 | 2013-01-09 | 安全第一公司 | System and method for managing encryption keys |
| US8494168B1 (en) | 2008-04-28 | 2013-07-23 | Netapp, Inc. | Locating cryptographic keys stored in a cache |
| US20100132047A1 (en) * | 2008-11-24 | 2010-05-27 | Honeywell International Inc. | Systems and methods for tamper resistant memory devices |
| US8275996B1 (en) | 2010-04-12 | 2012-09-25 | Stephen Waller Melvin | Incremental encryption of stored information |
| US8812875B1 (en) * | 2010-04-12 | 2014-08-19 | Stephen Melvin | Virtual self-destruction of stored information |
| US8478997B2 (en) * | 2010-09-10 | 2013-07-02 | Raytheon Company | Multi-level security software architecture |
| US20120069995A1 (en) * | 2010-09-22 | 2012-03-22 | Seagate Technology Llc | Controller chip with zeroizable root key |
| WO2013055872A2 (en) * | 2011-10-12 | 2013-04-18 | Raytheon Company | An integrated circuit for cyber security processing |
| US9798899B1 (en) | 2013-03-29 | 2017-10-24 | Secturion Systems, Inc. | Replaceable or removable physical interface input/output module |
| US9374344B1 (en) | 2013-03-29 | 2016-06-21 | Secturion Systems, Inc. | Secure end-to-end communication system |
| US9317718B1 (en) | 2013-03-29 | 2016-04-19 | Secturion Systems, Inc. | Security device with programmable systolic-matrix cryptographic module and programmable input/output interface |
| US9355279B1 (en) | 2013-03-29 | 2016-05-31 | Secturion Systems, Inc. | Multi-tenancy architecture |
| US9524399B1 (en) * | 2013-04-01 | 2016-12-20 | Secturion Systems, Inc. | Multi-level independent security architecture |
| US9990503B2 (en) * | 2015-08-04 | 2018-06-05 | Ge Aviation Systems, Llc | Cryptographic key server embedded in data transfer system |
| US11283774B2 (en) | 2015-09-17 | 2022-03-22 | Secturion Systems, Inc. | Cloud storage using encryption gateway with certificate authority identification |
| US10708236B2 (en) | 2015-10-26 | 2020-07-07 | Secturion Systems, Inc. | Multi-independent level secure (MILS) storage encryption |
| US11310198B2 (en) | 2017-05-31 | 2022-04-19 | Crypto4A Technologies Inc. | Integrated multi-level or cross-domain network security management appliance, platform and system, and remote management method and system therefor |
| US11321493B2 (en) * | 2017-05-31 | 2022-05-03 | Crypto4A Technologies Inc. | Hardware security module, and trusted hardware network interconnection device and resources |
| CN110233723B (en) * | 2019-04-28 | 2023-02-14 | 新大陆(福建)公共服务有限公司 | Secondary key management method and security chip |
| US11288404B2 (en) * | 2019-06-14 | 2022-03-29 | Infineon Technologies Ag | Resource protection |
| US11968187B2 (en) * | 2020-10-23 | 2024-04-23 | Secturion Systems, Inc. | Multi-independent level security for high performance computing and data storage systems |
| FR3118504B1 (en) * | 2020-12-28 | 2024-05-17 | St Microelectronics Rousset | Electronic system comprising several microprocessors |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0876026A2 (en) * | 1997-04-30 | 1998-11-04 | Motorola, Inc. | Programmable crypto processing system and method |
| EP1326157A2 (en) * | 2001-12-12 | 2003-07-09 | Pervasive Security Systems Inc. | Method and apparatus for securing digital assets |
| US6836548B1 (en) * | 1991-10-29 | 2004-12-28 | The Commonwealth Of Australia | Communications security and trusted path method and means |
Family Cites Families (69)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4442484A (en) * | 1980-10-14 | 1984-04-10 | Intel Corporation | Microprocessor memory management and protection mechanism |
| US4683532A (en) | 1984-12-03 | 1987-07-28 | Honeywell Inc. | Real-time software monitor and write protect controller |
| US5495533A (en) * | 1994-04-29 | 1996-02-27 | International Business Machines Corporation | Personal key archive |
| US5905725A (en) * | 1996-12-16 | 1999-05-18 | Juniper Networks | High speed switching device |
| US6704871B1 (en) * | 1997-09-16 | 2004-03-09 | Safenet, Inc. | Cryptographic co-processor |
| US5991519A (en) | 1997-10-03 | 1999-11-23 | Atmel Corporation | Secure memory having multiple security levels |
| US6378072B1 (en) * | 1998-02-03 | 2002-04-23 | Compaq Computer Corporation | Cryptographic system |
| US6751729B1 (en) * | 1998-07-24 | 2004-06-15 | Spatial Adventures, Inc. | Automated operation and security system for virtual private networks |
| US6408001B1 (en) * | 1998-10-21 | 2002-06-18 | Lucent Technologies Inc. | Method for determining label assignments for a router |
| US7660986B1 (en) * | 1999-06-08 | 2010-02-09 | General Instrument Corporation | Secure control of security mode |
| US6654888B1 (en) * | 1999-12-31 | 2003-11-25 | International Business Machines Corporation | Installing and controlling trial software |
| JP4522548B2 (en) | 2000-03-10 | 2010-08-11 | 富士通フロンテック株式会社 | Access monitoring device and access monitoring method |
| US6604147B1 (en) * | 2000-05-09 | 2003-08-05 | Lucent Technologies Inc. | Scalable IP edge router |
| US6986046B1 (en) * | 2000-05-12 | 2006-01-10 | Groove Networks, Incorporated | Method and apparatus for managing secure collaborative transactions |
| US6615329B2 (en) * | 2001-07-11 | 2003-09-02 | Intel Corporation | Memory access control system, apparatus, and method |
| US6901491B2 (en) * | 2001-10-22 | 2005-05-31 | Sun Microsystems, Inc. | Method and apparatus for integration of communication links with a remote direct memory access protocol |
| US7089419B2 (en) * | 2002-04-18 | 2006-08-08 | International Business Machines Corporation | Control function with multiple security states for facilitating secure operation of an integrated system |
| US7356147B2 (en) | 2002-04-18 | 2008-04-08 | International Business Machines Corporation | Method, system and program product for attaching a title key to encrypted content for synchronized transmission to a recipient |
| US7103914B2 (en) * | 2002-06-17 | 2006-09-05 | Bae Systems Information Technology Llc | Trusted computer system |
| US7322043B2 (en) * | 2002-06-20 | 2008-01-22 | Hewlett-Packard Development Company, L.P. | Allowing an electronic device accessing a service to be authenticated |
| JP4338946B2 (en) * | 2002-07-03 | 2009-10-07 | 日本電気株式会社 | MPLS switch and MPLS switching method used therefor |
| US7773754B2 (en) * | 2002-07-08 | 2010-08-10 | Broadcom Corporation | Key management system and method |
| US7441262B2 (en) * | 2002-07-11 | 2008-10-21 | Seaway Networks Inc. | Integrated VPN/firewall system |
| US7539185B2 (en) | 2002-10-07 | 2009-05-26 | Broadcom Corporation | Fast-path implementation for an uplink double tagging engine |
| US7274696B1 (en) | 2002-10-21 | 2007-09-25 | Force10 Networks, Inc. | Scalable redundant switch fabric architecture |
| GB0229647D0 (en) * | 2002-12-19 | 2003-01-22 | Zarlink Semiconductor Ltd | Packet classifer |
| WO2004068314A2 (en) * | 2003-01-27 | 2004-08-12 | Raza Microelectronics, Inc. | Method and device for the classification and redirection of data packets in a heterogeneous network |
| JP4103611B2 (en) * | 2003-02-03 | 2008-06-18 | ソニー株式会社 | Wireless ad hoc communication system, terminal, authentication method, encryption method, terminal management method in terminal, and program for causing terminal to execute these methods |
| US7322042B2 (en) * | 2003-02-07 | 2008-01-22 | Broadon Communications Corp. | Secure and backward-compatible processor and secure software execution thereon |
| JP4157403B2 (en) * | 2003-03-19 | 2008-10-01 | 株式会社日立製作所 | Packet communication device |
| US7515717B2 (en) * | 2003-07-31 | 2009-04-07 | International Business Machines Corporation | Security containers for document components |
| US20050031119A1 (en) * | 2003-08-04 | 2005-02-10 | Yuying Ding | Method and communications device for secure group communication |
| WO2005024568A2 (en) | 2003-08-19 | 2005-03-17 | General Dynamics Advanced Information Systems, Inc. | Trusted interface unit (tiu) and method of making and using the same |
| US7596086B2 (en) * | 2003-11-05 | 2009-09-29 | Xiaolin Wang | Method of and apparatus for variable length data packet transmission with configurable adaptive output scheduling enabling transmission on the same transmission link(s) of differentiated services for various traffic types |
| US7210051B2 (en) * | 2003-11-07 | 2007-04-24 | Via Technologies, Inc. Of Taiwan | System and method for handling state change conditions by a program status register |
| US20050132186A1 (en) * | 2003-12-11 | 2005-06-16 | Khan Moinul H. | Method and apparatus for a trust processor |
| US7636858B2 (en) * | 2003-12-11 | 2009-12-22 | Intel Corporation | Management of a trusted cryptographic processor |
| JP4130799B2 (en) * | 2003-12-24 | 2008-08-06 | 三星電子株式会社 | Multi-beam semiconductor laser |
| US7542567B2 (en) * | 2004-06-10 | 2009-06-02 | Freescale Semiconductor, Inc. | Method and apparatus for providing security in a data processing system |
| US7739501B2 (en) | 2004-07-29 | 2010-06-15 | Infoassure, Inc. | Cryptographic key construct |
| JP2006060579A (en) | 2004-08-20 | 2006-03-02 | Fujitsu Ltd | Communication device that uses multiple paths simultaneously according to application characteristics |
| US7546512B2 (en) | 2004-09-23 | 2009-06-09 | Intel Corporation | Techniques to perform error detection |
| US7774619B2 (en) * | 2004-11-17 | 2010-08-10 | Broadcom Corporation | Secure code execution using external memory |
| US8000324B2 (en) | 2004-11-30 | 2011-08-16 | Broadcom Corporation | Pipeline architecture of a network device |
| US7408947B2 (en) * | 2005-01-06 | 2008-08-05 | Enigma Semiconductor | Method and apparatus for scheduling packets and/or cells |
| US7681226B2 (en) * | 2005-01-28 | 2010-03-16 | Cisco Technology, Inc. | Methods and apparatus providing security for multiple operational states of a computerized device |
| JP4376233B2 (en) * | 2005-02-04 | 2009-12-02 | 株式会社エヌ・ティ・ティ・ドコモ | Client apparatus, device verification apparatus, and verification method |
| KR100695146B1 (en) * | 2005-04-12 | 2007-03-14 | 삼성전자주식회사 | Method and device for sending message in network mixed with private network and public network |
| US20060294596A1 (en) * | 2005-06-27 | 2006-12-28 | Priya Govindarajan | Methods, systems, and apparatus to detect unauthorized resource accesses |
| US7761674B2 (en) * | 2005-12-30 | 2010-07-20 | Intel Corporation | Identifier associated with memory locations for managing memory accesses |
| US8190877B2 (en) | 2005-07-05 | 2012-05-29 | Viasat, Inc. | Trusted cryptographic processor |
| US20070245413A1 (en) | 2005-07-05 | 2007-10-18 | Viasat, Inc. | Trusted Cryptographic Switch |
| JP5202312B2 (en) | 2005-07-06 | 2013-06-05 | インターナショナル レクティフィアー コーポレイション | Group III nitride enhancement type devices |
| US20070014399A1 (en) * | 2005-07-15 | 2007-01-18 | Scheidt Edward M | High assurance key management overlay |
| US20070067826A1 (en) * | 2005-09-19 | 2007-03-22 | Texas Instruments Incorporated | Method and system for preventing unsecure memory accesses |
| US7532633B2 (en) * | 2005-10-12 | 2009-05-12 | Juniper Networks, Inc. | Spoof checking within a label switching computer network |
| KR100723864B1 (en) * | 2005-11-12 | 2007-05-31 | 한국전자통신연구원 | Method and apparatus for preventing network attack using information contained in packet |
| US9081981B2 (en) * | 2005-12-29 | 2015-07-14 | Nextlabs, Inc. | Techniques and system to manage access of information using policies |
| US8719526B2 (en) * | 2006-01-05 | 2014-05-06 | Broadcom Corporation | System and method for partitioning multiple logical memory regions with access control by a central control agent |
| US20070226795A1 (en) * | 2006-02-09 | 2007-09-27 | Texas Instruments Incorporated | Virtual cores and hardware-supported hypervisor integrated circuits, systems, methods and processes of manufacture |
| US8051299B2 (en) * | 2006-03-20 | 2011-11-01 | Hewlett-Packard Development Company, L.P. | Computer security method and computer system |
| US8041947B2 (en) * | 2006-03-23 | 2011-10-18 | Harris Corporation | Computer architecture for an electronic device providing SLS access to MLS file system with trusted loading and protection of program execution memory |
| GB2437558B (en) * | 2006-04-19 | 2010-12-15 | Thales Holdings Uk Plc | Privacy protection system |
| US7779258B2 (en) * | 2006-09-22 | 2010-08-17 | International Business Machines Corporation | Method for controlling security function execution with a flexible, extendable, and non-forgable block |
| JP4374015B2 (en) * | 2006-11-30 | 2009-12-02 | 株式会社東芝 | Data transmitting apparatus, data receiving apparatus, and data communication system |
| US8218761B2 (en) * | 2007-04-06 | 2012-07-10 | Oracle International Corporation | Method and apparatus for generating random data-encryption keys |
| US20090034734A1 (en) * | 2007-07-31 | 2009-02-05 | Viasat, Inc. | Multi-Level Key Manager |
| US20090214044A1 (en) * | 2008-02-21 | 2009-08-27 | Hitachi, Ltd. | Data archiving technique for encrypted data |
| US9003197B2 (en) * | 2008-03-27 | 2015-04-07 | General Instrument Corporation | Methods, apparatus and system for authenticating a programmable hardware device and for authenticating commands received in the programmable hardware device from a secure processor |
-
2008
- 2008-07-31 US US12/184,062 patent/US20090034734A1/en not_active Abandoned
- 2008-07-31 US US12/184,079 patent/US8312292B2/en active Active
- 2008-07-31 WO PCT/US2008/071823 patent/WO2009018483A1/en not_active Ceased
- 2008-07-31 US US12/184,048 patent/US8392983B2/en active Active
- 2008-07-31 WO PCT/US2008/071818 patent/WO2009018479A1/en not_active Ceased
- 2008-07-31 WO PCT/US2008/071821 patent/WO2009018481A1/en not_active Ceased
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6836548B1 (en) * | 1991-10-29 | 2004-12-28 | The Commonwealth Of Australia | Communications security and trusted path method and means |
| EP0876026A2 (en) * | 1997-04-30 | 1998-11-04 | Motorola, Inc. | Programmable crypto processing system and method |
| EP1326157A2 (en) * | 2001-12-12 | 2003-07-09 | Pervasive Security Systems Inc. | Method and apparatus for securing digital assets |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8312292B2 (en) | 2007-07-31 | 2012-11-13 | Viasat, Inc. | Input output access controller |
| US8392983B2 (en) | 2007-07-31 | 2013-03-05 | Viasat, Inc. | Trusted labeler |
| WO2018153559A1 (en) * | 2017-02-21 | 2018-08-30 | Siemens Aktiengesellschaft | Method and validation unit for controlling the loading of crypto keys, in particular "key blobs", usable in it systems, in particular embedded systems |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2009018479A4 (en) | 2009-04-30 |
| US20090037631A1 (en) | 2009-02-05 |
| US20090158050A1 (en) | 2009-06-18 |
| US20090034734A1 (en) | 2009-02-05 |
| WO2009018479A1 (en) | 2009-02-05 |
| US8312292B2 (en) | 2012-11-13 |
| WO2009018483A1 (en) | 2009-02-05 |
| US8392983B2 (en) | 2013-03-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20090034734A1 (en) | Multi-Level Key Manager | |
| US10868679B1 (en) | Nonvolatile memory device with regions having separately programmable secure access features and related methods and systems | |
| CN1331056C (en) | Control function based on requesting master id and a data address within an integrated system | |
| US8839001B2 (en) | Infinite key memory transaction unit | |
| CN101673251B (en) | Device with privileged memory and applications thereof | |
| US5224166A (en) | System for seamless processing of encrypted and non-encrypted data and instructions | |
| US9483664B2 (en) | Address dependent data encryption | |
| US20050283566A1 (en) | Self testing and securing ram system and method | |
| KR20080100673A (en) | Encryption-based security protection method for processor and apparatus thereof | |
| CN106383790A (en) | Bus management unit and high safety system on chip | |
| US9152576B2 (en) | Mode-based secure microcontroller | |
| EP2228988B1 (en) | Circuit for restricting data access | |
| US8612774B2 (en) | Secure OTP using external memory | |
| EP2990953B1 (en) | Periodic memory refresh in a secure computing system | |
| US8127145B2 (en) | Computer architecture for an electronic device providing a secure file system | |
| US20210011994A1 (en) | Device and method for managing an encrypted software application | |
| US12512964B2 (en) | Memory controller cryptographic data quantization using a cache | |
| US20240080193A1 (en) | Counter integrity tree | |
| US12248409B2 (en) | Apparatus and method of controlling access to data stored in a non-trusted memory | |
| CN114237492A (en) | Non-volatile memory protection method and device | |
| US20080120481A1 (en) | Methods For Protection Of Data Integrity Of Updatable Data Against Unauthorized Modification | |
| US20250165584A1 (en) | Data processing system with secure memory sharing | |
| CN115185879A (en) | Control device, data processing method, storage system, SOC |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 08796992 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 08796992 Country of ref document: EP Kind code of ref document: A1 |