US 8,060,744 B2Grant
Computer architecture for an electronic device providing single-level secure access to multi-level secure file system
Issue Date:2011-11-15
•35 Claims
•6 Drawing Sheets
Abstract
Method for providing a single level secure (SLS) user processor (402, 502) with access to a multi-level secure (MLS) file system (300). The method begins by authenticating a user to a cryptographic processor (302) by communicating one or more types of user authentication information to the cryptographic processor. Based on such authentication, the MLS file system services are provided such that the SLS user processor (402, 502) has access to files (306, 308, 310, 312, 314) at only one defined security classification level at a time. The method also includes zeroizing one or more data stores used by the SLS user processor each time the SLS user processor transitions between accessing classified data files at a first security classification level and a second security classification level.
Metadata
Assignee
- Harris Corporation
Inventors
- Terence W. O'Brien
- Richard Schmalbach
- John Blessing
- Jeffrey Murray
Application Information
Application Number:US 11/387,991
Filing Date:2006-03-23
Priority Date:2006-03-23
Art Unit:2436
Classifications
IPC:
H04L29/00
Patent Drawings (6 sheets)
Description
Background of the Invention
[0001] 1. Statement of the Technical Field
[0002] The inventive arrangements relate to electronic devices for storing and accessing sensitive/classified data.
[0003] 2. Description of the Related Art
[0004] Electronic computers have the ability to store and process data. Computers typically include some kind of microprocessor with a commercially available operating system such as Linux, Unix, or Microsoft Windows. Many computers also have displays and keyboards for the human/machine interface. The foregoing capabilities make these devices highly useful for a various business and personal applications.
[0005] Currently, there exist a wide variety of computing devices with conventional operating systems and architectures. These commercially available computers with commercial-off-the-shelf (COTS) operating systems and COTS application programs generally satisfy the processing and data storage requirements of most users. For example, they include applications for word processing, data storage, spreadsheets, time management, and contact management. These applications generally function quite well and have interfaces that are familiar to many users.
[0006] Some commercially available computing devices and/or software applications incorporate various security measures in an effort to protect data which is stored or processed using the device. For example, encryption technology and password protection features are known in the art. Still, this level of security can be inadequate for managing information that is of a Confidential, Secret, or Top Secret nature, particularly when such information relates to matters of national security. For example, COTS operating systems and applications may not be sufficiently trustworthy for handling this type of information. Such programs can be susceptible to being compromised by various means including hacker attacks, viruses, worms, Trojan horses, and a wide variety of other means that are known to those skilled in the art.
[0007] Finally, notwithstanding the security limitations of COTS operating systems and applications, the basic architecture and interface systems of many commercial computing devices may leave these devices vulnerable to intrusion. For example, COTS devices do not employ trusted microprocessors, do not employ physical separation of classified and unclassified data processing, nor do they employ physical tamper detection and subsequent memory zeroization. Consequently, transport or processing of classified data using a commercial computer is not generally permitted.
[0008] Trusted operating systems and applications are generally designed to more rigorously address the problem of computer security. Trusted operating systems undergo evaluation of their overall design, verification of the integrity and reliability of their source code, and systematic, independent penetration evaluation. In contrast, non-trusted operating systems are generally not designed to an equally high level with regard to security precautions.
[0009] Single-level secure (SLS) is a class of systems that contain information with a single sensitivity (classification). SLS systems permit access by a user to data at a single sensitivity level without compromising data. Thus, SLS data file systems allow information at a single classification to be stored in an information system. The level of access can be limited by the current user security classification sign-on level and a security classification assigned to the secure user processor.
[0010] Multi-level secure (MLS) is a class of systems that contain information with different sensitivities (classifications). MLS systems permit simultaneous access by a user to data at multiple classification levels without compromising security. Thus, MLS data file systems allow information with different classifications to be stored in an information system. These systems are also designed to provide a user with the ability to process information in the same system. Significantly, however, these systems prevent a user from accessing information for which he is not cleared, does not have proper authorization, or does not have a need-to-know.
[0011] Users of non-trusted COTS operating systems, as may be found in commercial computers, are not generally allowed access to classified data found in secure file systems. Computers that utilize a trusted operating system (OS) which includes support for an SLS or MLS file system have been developed that are specifically designed to allow for storage of classified data. However, these devices are not generally designed to physically secure the data and zeroize the data upon tamper detection. Nor are they designed to be embedded as a secure component of a host computer system.
Summary of the Invention
[0012] The invention concerns a method for providing a single level secure (SLS) user processor with multi-level secure (MLS) file system services. The method begins by authenticating a user to a cryptographic processor by communicating one or more types of user authentication information to the cryptographic processor. Based on such authentication, the MLS file system services are provided such that the SLS user processor has access to files at only one defined security classification level at a time. The method also includes zeroizing one or more data stores used by the SLS user processor each time the SLS user processor transitions between accessing classified data files at a first security classification level and a second security classification level.
[0013] According to one aspect of the invention, an MLS file services module can receives a request from an SLS user processor for a classified data file. In response to the request, a cryptographic processor associated with the MLS file services module accesses an MLS file system containing the classified data file. Thereafter the cryptographic processor decrypts the classified data file and the file is served to the SLS user processor in decrypted form.
[0014] The term “cryptographic processor” as used herein generally refers to a processor that is specifically designed to facilitate cryptographic processing. Such processors generally include one or more hardware based encryption services that facilitate the encryption and decryption of classified data files. For example, the hardware encryption services can include a hardware implemented cryptographic algorithm, a random number generator, and/or an exponentiator.
[0015] It should be understood that the method disclosed herein includes exclusively limiting concurrent access of the SLS user processor to files defined within a single security classification level within the MLS file system. This process is accomplished by utilizing a client zeroizer that is responsive to the cryptographic processor to automatically zeroize at least one data store used by the SLS user processor. According to one aspect of the invention, this zeroizing step is performed when the SLS user processor transitions between a first state in which it has access to the multi-level secure file system at a first security classification level, and a second state in which it has access to the multi-level secure file system at a second security classification level. The method also includes communicating the classified data file from the MLS file service module to the SLS user processor over a secure path.
[0016] The method also includes generating the request for the classified data file at a secure human/machine interface and communicating the request to the SLS user processor. The information contained in the classified data file is thereafter displayed to a user with the secure human/machine interface. When any necessary file operations are complete the classified data file is communicated from the SLS user processor to the MLS file services module. There, the cryptographic processor encrypts the classified data file. After encryption, the method continues by accessing the MLS file system with the cryptographic processor to store the classified data file.
[0017] The method can also include receiving at a MLS file service module a request from the SLS user processor for a non-encrypted unclassified data file. In response to such request, the MLS file services module accesses the MLS file system containing the unclassified data file. The unclassified data file is then served to the SLS user processor in plain-text form.
[0018] The method can further include selecting the cryptographic processor to include a trusted microprocessor and a trusted operating system executing on the trusted cryptographic processor. The SLS user processor can also be chosen so as to include trusted microprocessor hardware. According to one aspect of the invention, the SLS user processor can be selected so as to include a single level trusted operating system. Alternatively, the SLS user processor can be chosen so as to include an untrusted operating system.
[0019] The invention disclosed herein also includes a system for providing a secure file service. The basic building block of the system is an MLS file services module, which includes a cryptographic processor comprising suitable hardware and software for encrypting and decrypting a classified data file. The MLS file services module also includes an MLS file system hosted by the cryptographic processor. The MLS file system contains classified data files and is accessible exclusively to the cryptographic processor. The cryptographic processor is programmed so that it is responsive to a single level secure (SLS) user processor. The SLS user processor is distinct from the cryptographic processor. The SLS user processor includes suitable programming and communications hardware for requesting at least one classified data file from the MLS file service module that hosts the MLS file system. The cryptographic processor includes suitable cryptographic hardware and software to decrypt the classified data file. Once the file is decrypted by the cryptographic processor, the MLS file service module serves the classified data file to the SLS user processor in decrypted form. Depending on the configuration, the SLS user processor, the cryptographic processor, or both devices are provided with programming and data files as necessary for authenticating a user responsive to at least one user authentication information.
[0020] The cryptographic processor used in the system can exclusively limit the extent of MLS file access permitted to the SLS user processor. In particular, the cryptographic processor can limit the SLS user processor so that it can concurrently access files that are only within a single security classification level within the multi-level secure file system. The system can accomplish this by means of a client zeroizer that is responsive to the cryptographic processor. The client zeroizer is configured for automatically zeroizing at least one data store used by the SLS user processor.
[0021] According to one aspect of the invention, the cryptographic processor is programmed to cause the client zeroizer to automatically perform the zeroizing described herein under certain conditions. For example, the zeroizing can be performed when the SLS user processor transitions between a first state in which the SLS user processor has access to the multi-level secure file system at a first security classification level, and a second state in which the SLS user processor has access to the multi-level secure file system at a second security classification level.
[0022] The system provides a secure path defining a data communication link between the SLS user processor and the cryptographic processor. The system can also include a secure human/machine interface operatively connected to the SLS user processor. The secure human/machine interface is configured for communicating user commands to the SLS user processor and for displaying classified data files.
[0023] The SLS user processor described herein includes programming and communications hardware for communicating the classified data file from the SLS user processor to the cryptographic processor. The cryptographic processor includes necessary cryptographic hardware and software programming for encrypting the classified data file. The cryptographic processor is also programmed and includes suitable communication hardware for accessing the MLS file system for the purpose of storing the classified data file after encryption in the MLS file system.
[0024] The cryptographic processor can also include suitable programming and hardware so that it accesses the MLS file system responsive to a request from the SLS user processor for an unclassified data file. The MLS file service module can thereafter serve the unclassified data file to the SLS user processor.
[0025] According to one aspect of the invention, the cryptographic processor is comprised of a trusted microprocessor and a trusted operating system executing on the trusted cryptographic processor. The SLS user processor can also be comprised of trusted microprocessor hardware. According to one embodiment, the SLS user processor is comprised of a single level trusted operating system. Advantageously, however, the SLS user processor can instead be comprised of an untrusted operating system.
Brief Description of the Drawings
[0026] FIG. 1 is a block diagram of a single-level secure computing device of the prior art.
[0027] FIG. 2 is a block diagram of a multi-level secure computing device of the prior art.
[0028] FIG. 3 is a detailed block diagram of a multi-level secure file service module configured for single-level secure file access.
[0029] FIG. 4 is a block diagram of a multi-level secure computing architecture that utilizes the file service module of FIG. 3 .
[0030] FIG. 5 is an alternative embodiment of a multi-level secure computing architecture that utilizes the file service module of FIG. 3 .
Detailed Description of the Preferred Embodiments
[0031] A block diagram of a single-level secure (SLS) computing device 100 is shown in FIG. 1 . The SLS computing device 100 can include a secure user processor 102 that includes trusted hardware and single-level trusted software (operating system and application software). As used herein, the term “trusted” is used with reference to computer hardware, operating systems, and/or software applications that have been designed to ensure secure storage, processing and communication of data. Trusted hardware and trusted software can be combined to provide secure data processing. Trusted hardware and software are generally designed and tested to ensure the integrity and reliability of their source code, and their resistance to penetration. In contrast, non-trusted hardware and non-trusted software are generally not designed to an equally high level with regard to security precautions. Accordingly, when integrated into a computer system, those systems are often referred to as non-secure. Commercial-off-the-shelf (COTS) hardware and software is generally not “trusted.”
[0032] The computing device 100 also includes a user SLS file system 108 in a data store that is used for storing user executable programs and data. Classified data stored in the SLS file system 108 is stored in an encrypted format. A cryptographic engine 104 is provided with trusted hardware and trusted software for providing encryption and decryption services. A crypto file system 110 is also maintained in a data store. The crypto file system 110 is used to store classified data and files used by the cryptographic engine 104. In contrast to the user SLS file system 108, user data and applications are not generally stored in the crypto file system 110. Instead, the crypto file system 110 generally contains cryptographic algorithms, security keys and certificates, audit data, policy profiles, and application data specific to the processing performed by the cryptographic engine 104.
[0033] A secure human/machine interface (HMI) 106 is also provided for the SLS computing device 100. The secure HMI 106 can be comprised of trusted hardware and can provide a trusted path to applications executing on secure user processor 102. Consequently, secure HMI 106 can prevent invasive or unauthorized applications from monitoring user inputs and system outputs. Secure HMI devices are known in the art and typically can include one or more features to ensure trusted communications between the user and the secure user processor. For example, the secure HMI 106 can provide a suitable interface by which a user can enter data and commands to the computing device 100. Secure HMI 106 can also include a user display for showing data and information processed by the computing device 100.
[0034] A user can request access to a classified data file using the secure HMI 106. Encrypted files in the user SLS files system 108 are accessed by the secure user processor 102 and provided to the cryptographic engine 104 for decryption. After the file has been decrypted, the cryptographic engine passes the decrypted file back to the secure user processor 102. Upon completion of any necessary user processing associated with the decrypted classified date file, the secure user processor 102 passes the file back to the cryptographic engine 104 for re-encryption. Thereafter, the encrypted file is returned to the secure user processor 102, which stores the file in the user SLS file system 108.
[0035] Notably, the secure user processor 102 can generally satisfy the security requirements for accessing the single-level secure file system 108. However, the operating system and applications can be expensive as compared to COTS systems. In particular, the secure user processor must be developed specifically to include trusted software for managing classified files, and especially for managing encryption and decryption services provided by the cryptographic processor. Another disadvantage of this arrangement is that the user single-level secure file system is not generally designed to physically secure the data and zeroize the data upon tamper detection.
[0036] Referring now to FIG. 2 , there is shown a multi-level secure (MLS) computing device 200. MLS computing device 200 can include a secure user processor 202 comprised of trusted hardware and multi-level trusted software (operating system and application software). A secure human/machine interface (HMI) 206 is also provided for the MLS computing device 200. The secure human/machine interface can be similar to the secure HMI described above relative to FIG. 1
[0037] The MLS computing device 200 also includes a user MLS file system 208 in a data store that is used for storing user executable programs and data. Classified data stored in the MLS file system 208 is stored in an encrypted format. A cryptographic engine 204 is provided with trusted hardware and multi-level trusted software for providing encryption and decryption services. A crypto MLS file system 210 is used to store classified data and files used by the cryptographic engine 104. For example, the MLS file system can separately store and control access to data that is designated as Classified, Secret, or Top Secret. In contrast to the user MLS file system 208, user data and applications are not generally stored in the crypto MLS file system 210. Instead, the crypto MLS file system 210 generally contains cryptographic algorithms, security keys, and application data that is specific to the processing performed by the cryptographic engine 204.
[0038] Encrypted files in the user MLS files system 208 are accessed by the secure user processor 202 and provided to the cryptographic engine 204 for decryption. After the file has been decrypted, the cryptographic engine passes the decrypted file back to the secure user processor 202. Upon completion of any necessary user processing associated with the decrypted classified date file, the secure user processor 202 passes the file back to the cryptographic engine 204 for re-encryption. Thereafter, the encrypted file is returned to the secure user processor 202, which stores the file in the user MLS file system 208.
[0039] The secure user processor 202 can generally satisfy the security requirements for accessing the multi-level secure user file system 208. However, the operating system and applications can be expensive as compared to COTS systems. In particular, the secure user processor must be developed specifically to include trusted software for managing multiple levels of classified files, and especially for managing encryption and decryption services provided by the cryptographic processor. Another disadvantage of this arrangement is that the user multi-level secure user file system 208 is not generally designed to physically secure the data and zeroize the data upon tamper detection.
[0040] Referring now to FIG. 3 , there is shown a detailed block diagram of an MLS file service module 300. The MLS file service module 300 is configured for providing SLS file access to a user MLS file system. As shown in FIG. 3 a cryptographic processor 302 can host a crypto processor file system 304. The crypto processor file system 304 can provide storage for various file used by the cryptographic processor 304. For example, these files can include cryptographic algorithms, keys and certificates, audit data, and policy profiles. The cryptographic processor 302 can also host a user MLS file system 301 comprised of classified information at multiple classification levels. More particularly, the cryptographic processor 302 can provide SLS file access to the MLS file system. Thus, the cryptographic processor 302 can serve files at a single defined security level to a client/user that has signed on at that particular security level after appropriate authentication. Additionally, the cryptographic processor 302 can ensure that information loaded into the MLS file system has been provided by a trusted source and that the integrity of the information has been checked. For example, this can be accomplished using checksum/hashing technology.
[0041] According to one embodiment of the invention, the user MLS file system 301 can include files comprising Top Secret information 306, Secret information 308, and Confidential information 310. The files comprising Top Secret information 306, Secret information 308, and Confidential information 310 are stored in an encrypted form. These files can include classified data and classified applications. The classified information files stored in the user MLS file system 301 can be decrypted by the secure cryptographic processor 302 and served to a client processor using client SLS access interface 316. In the opposite direction, classified information processed by the client processor is presented by means of client SLS access interface 316 to the cryptographic processor 302. The cryptographic processor 302 encrypts the classified data file and stores it in the classified section of the user MLS file system 301 as Top Secret information 306, Secret information 308, or Confidential information 310. In this way, the MLS file service module with SLS access 300 can provide a client processor with unencrypted read/write access to such files at a single security classification level after user authentication.
[0042] The user MLS file system 301 can also be comprised of unclassified applications 312. Such applications can be stored in a non-encrypted format. Since a user will not normally need to modify applications software, the cryptographic processor 302 can limit access by a client processor so that the client processor is permitted read only access to the files comprising unclassified applications 312. The files included in the unclassified applications 312 can be read by the secure cryptographic processor 302 and served to the client processor through client SLS access interface 316.
[0043] The user MLS file system 301 can also contain files comprising unclassified information 314. The files comprising unclassified information 314 stored in the user MLS file system 301 can be read by the secure cryptographic processor 302 and served to the client processor by means of client SLS access interface 316. In the opposite direction, unclassified information processed by the client processor is presented through client MLS access interface 316 to the cryptographic processor 302 for storage in the unclassified section 316 of the user MLS file system. The MLS file service module with SLS access 300 can provide read/write access to files comprising unclassified information 314.
[0044] Significantly, the MLS file service module 300 can also include client zeroize/reset manager 318. The client zeroize/reset manager 318 can be controlled by cryptographic processor 302. The cryptographic processor can be programmed to cause the client zeroize/reset manager 318 to automatically zeroize and/or reset any data stores associated with the client processor served by the MLS file service module 300. The client zeroize/reset manager can zeroize or reset any memory devices or data stores used by the client processor to temporarily store application data, user data, or other file data served to the client processor by the MLS file service module 300. As will be appreciated by those skilled in the art, such memory devices can include RAM, DRAM, flash memory, video display buffers and any other memory devices used by the client processor for temporarily storing data from files served by the MLS file service module 300. This automatic process can occur each time that a client processor is transitioned from accessing files at one security classification level to another security classification level.
[0045] For example, an SLS client processor served by the MLS file service module 300 can be provided with SLS file-access to Top Secret Information 306. Such access can occur after user sign-on and authentication as appropriate for that security level. Thereafter, a user wishing to use the same SLS client processor to access files at a different defined security classification level can log off the MLS file service module 300. Once logged off, the user can log back on to the MLS file service module 300 with the client processor at a different single defined security classification level. For example, after logging off from the Top Secret level, the client processor can subsequently be permitted access to files comprising a single security classification level such as Secret Information 308, Confidential Information 310, or Unclassified Information 314.
[0046] Those skilled in the art will appreciate that a client SLS processor of the prior art is normally only able to access classified information at one level. Such SLS processors and their associated software are not designed to accommodate the security demands for handling files at multiple security classification levels. In contrast, an SLS client processor served by the MLS file service module 300 is now also able to access information at multiple levels of security classification without the possibility of access violation. An example of such an access violations might include a user attempting to downgrade the security level of information contained in files. In particular, a user who accessed files using the client processor and defined as Top Secret Information 306 could maliciously or unintentionally subsequently try to store such data as Classified Information 310. Alternatively, such a situation could arise if information from files defined as Classified Information 310 were written unencrypted to the Unclassified Information 314 storage area. SLS processors are not generally designed to address these issues. However, this problem is solved by using the MLS file service module 300 described herein to provide SLS file access.
[0047] Referring again to FIG. 3 , the cryptographic processor 302 can be one of several commercially available cryptographic engines. According to one embodiment, the cryptographic processor can be a Sierra II Crypto processor available from Harris Corporation of Melbourne, Fla. The cryptographic processor 302 can include configurable key lengths and can be programmed with one or more encryption algorithms. As illustrated in FIG. 3 , the MLS file service module 300 can include several control and data ports that are useful for controlling the operation of the cryptographic processor 302. For example, these can include a crypto ignition key port, a key and certificate fill port, a zeroize switch, and a software load port. The software load port can be used for loading software from a trusted source for executing on the cryptographic processor 302 or a client processor. The zeroize switch can be used to clear the encryption keys and/or the classified information contained in the user MLS file system and the crypto MLS file system 304. The various control and data ports can be controlled by the client processor or by any other suitable means.
[0048] The cryptographic processor 302 can include one or more security features. For example, in addition to controlling SLS access to an MLS file system, the cryptographic engine 302 can provide security auditing, security policy enforcement, file integrity checking and/or trusted boot software loading.
[0049] The client SLS access interface 316 can provide communications support for a communication path between the MLS file service module 300 and a client processor. Any suitable physically-secure data communication path can be used for this purpose. Requests from a client processor for access to files and the decrypted data files can be communicated over this interface. A file system control interface 320 can be provided for user authentication, sign on, and sign off. This interface can provide a trusted communication link with the client processor.
[0050] Referring now to FIG. 4 , there is shown a block diagram for one embodiment of a computer architecture for a multi-level secure computing device 400 with an embedded MLS file service 300 module. SLS computing device 400 includes a secure user processor 402 utilizing trusted processing hardware and single level (SL) trusted software (operating system and application software). A secure HMI 404 is also provided. The secure HMI 404 is comprised of trusted hardware. Secure HMI 404 interfaces with the secure user processor 402 by means of a trusted communication link. Any suitable physically-secure data communication path can be used for this purpose provided that it offers trusted communications between the secure user processor 402 and the secure HMI 404. This trusted communication link can be used for communicating user commands, data, and any information to be displayed on the secure HMI. It can also be used to facilitate user sign-on as hereinafter described. Trusted communication links as described herein are known in the art.
[0051] The secure user processor 402 also communicates with the MLS service module 300. In particular, the secure user processor 402 can communicate with the client SLS access interface 316 and the file system control interface 320. The client SLS access interface 316 provides services as described above. The file system control interface 320 can provide a path for trusted user sign-on and authentication for user access to the SLS file access provided by MLS file service module 300. Trusted paths for user sign-on and authentication as referenced herein are known in the art.
[0052] The architecture in FIG. 4 provides additional capabilities as compared to the prior art SLS computing device 100 shown in FIG. 1 , thereby overcoming several of its limitations. The single-level trusted software running on secure user processor 402 is much simpler and thus less expensive to design, develop, and test/certify as compared to the SL-trusted software required for the secure user processor 102 in computing device 100. The SL-trusted operating system utilized on secure user processor 402 does not need to implement a trusted file system which is normally a significant portion of the SL-trusted OS development effort. The SL-trusted software applications utilized on secure user processor 402 do not need to invoke decryption services upon file read from the file system and do not need to invoke encryption services upon file write to the file system. The absence of these requirements significantly reduces the design, development and testing/certification effort for those software applications.
[0053] In addition to the foregoing advantages, the secure user processor 402 can now be used to access files at multiple security classification levels. Such SLS access to the user MLS file system 301 is advantageously achieved by placing responsibility for MLS security with the MLS file service module, and more particularly, with the cryptographic processor 302. Cryptographic processor selectively controls the client zeroize/reset manager 316 to ensure that MLS file system data is zeroized in the client processor whenever the client processor transitions between accessing files at one security classification level versus files at another security classification level. This is a significant improvement over the capabilities and design efficiencies offered by existing architectures.
[0054] It is noted that although the software executing on secure user processor 402 is simpler and potentially less expensive than the software utilized by the secure user processor 102 in the prior art, the software executing on secure user processor 402 still needs to be designed, developed, and tested/certified to single-level secure standards. The software on secure user processor 402 still needs to be SL-trusted so that it can provide the trusted path to the file system control interface 320 to support trusted user sign-on services.
[0055] Referring now to FIG. 5 , there is shown a block diagram for another embodiment of a computer architecture for a multi-level secure computing device 500 with an embedded MLS file service module 300. MLS computing device 500 includes a secure user processor 502 utilizing trusted processing hardware. However, rather than using SL trusted software, non-trusted software (operating system and application software) is used instead. For example, COTS software can be used for this purpose.
[0056] A secure HMI 504 is also provided. The secure HMI 504 is comprised of trusted hardware. Secure HMI 504 interfaces with the secure user processor 502 by means of a physically-secure communication link. Any suitable physically-secure data communication path can be used for this purpose. This physically-secure data communication link can be used for communicating user commands, data, and any information to be displayed on the secure HMI. Notably, in the architecture shown in FIG. 5 , this physically-secure communication link is not used to facilitate user sign-on because the software utilized by secure user processor 502 is not trusted. Instead, a separate trusted communication link is provided directly between the secure HMI 504 and the file system control interface 320.
[0057] The secure user processor 502 also communicates with the MLS service module 300. In particular, the secure user processor 502 can communicate with the client SLS access interface 316 (but not the file system control interface 320). The client SLS access interface 316 provides services as described above.
[0058] The architecture in FIG. 5 provides the same capabilities as the SLS computing device 400 shown in FIG. 4 , while overcoming one of its major limitations. In contrast to the device 400, the software running on secure user processor 502 is COTS software that is highly familiar to the user and does not require expensive custom development. The tradeoff to this approach is that secure user processor 502 cannot provide the trusted path to the file system control interface 320 to support trusted user sign-on services. Referring to FIG. 5 , it is seen that trusted human/machine interface 504 must now support two separate interfaces, one trusted interface to the SLS file service module 300 to handle user authentication and a second physically-secure interface to secure user processor 502 for all normal user input/output such as running software applications. This can permit a user to use familiar COTS operating systems and applications installed on the secure user processor 502, while still having the benefit of access to the MLS file service module 300.
[0059] In FIGS. 4 and 5 a communication link is provided respectively between the secure user processor 402, 502 and an SLS access interface 316 associated with a MLS file service module 300. It should be understood that the foregoing communication link can be implemented by any suitable means and in different physical configurations, provided it is physically secure. For example, the data communication link can be through a direct connection (e.g. USB, PCMCIA) interface. Such a direct connection can create the appearance that the MLS file service module 300 is a local disk drive. However, in order to establish a trusted path for user sign-on/sign-off, suitable trusted path methods can be used to provide the communication link. Trusted path methods of this type are well known to those skilled in the art.
[0060] As an alternative to the direct connection approach described above, the MLS file service module 300 can be embedded in the computer on an I/O bus (e.g. PCI) to provide the appearance of a local disk drive, but within the same physically secure enclosure. In this way, a secure path can be provided between the secure user processor and the file service module. Yet another alternative can include embedding the MLS file service module 300 on a host computer motherboard. Consequently, the data communication can occur over a data communication link within the same physically secure enclosure to establish a secure path.
[0061] The invention described and claimed herein is not to be limited in scope by the preferred embodiments herein disclosed, since these embodiments are intended as illustrations of several aspects of the invention. Any equivalent embodiments are intended to be within the scope of this invention. Indeed, various modifications of the invention in addition to those shown and described herein will become apparent to those skilled in the art from the foregoing description. Such modifications are also intended to fall within the scope of the appended claims.
Claims
We claim:
1. A method for providing a secure file service, comprising:
receiving at a multi-level secure (MLS) file service module a request from a single level secure (SLS) user processor for a classified user data file of a first security classification level, said classified user data file exclusively comprising at least one of user data and a user software application;
responsive to said request, accessing with a cryptographic processor an MLS file system containing said classified user data file;
decrypting said classified user data file with said cryptographic processor;
communicating, from said cryptographic processor, said classified user data file to said SLS user processor in decrypted form;
transitioning said SLS user processor from accessing classified user data files of said first security classification level to accessing user data files of a second security classification level contained in said MLS file system; and
in response to said transitioning of said SLS user processor, automatically erasing said classified user data file from at least one memory device used by said SLS user processor to temporarily store at least one of said user data and said user software application served to said SLS user processor by said MLS file service module; and
wherein said first and second security classification levels specify which classes of persons have access rights to respective ones of said user data files.
2. The method according to claim 1, further comprising selecting said cryptographic processor to include one or more hardware based encryption services that facilitate the encryption and decryption of classified data files.
3. The method according to claim 2, further comprising selecting said hardware based encryption services from the group consisting of a hardware implemented cryptographic algorithm, a random number generator, and an exponentiator.
4. The method according to claim 1, further comprising exclusively limiting concurrent access of said SLS user processor to files defined within a single security classification level within said MLS file system.
5. The method according to claim 4, wherein said automatic erasure is controlled by said cryptographic processor.
6. The method according to claim 1, further comprising communicating said classified user data file from said MLS file service module to said SLS user processor over a secure path.
7. The method according to claim 1, further comprising generating said request for said classified user data file at a secure human/machine interface and communicating said request to said SLS user processor.
8. The method according to claim 1, further comprising, displaying information contained in said classified user data file to a user with said secure human/machine interface.
9. The method according to claim 1, further comprising:
communicating said classified user data file from said SLS user processor to said MLS file service module;
encrypting said classified user data file using said cryptographic processor; and
accessing said MLS file system using said cryptographic processor to store said classified user data file after encryption in said MLS file system.
10. The method according to claim 1, further comprising, authenticating a user to said cryptographic processor by communicating at least one user authentication information to said cryptographic processor.
11. The method according to claim 1, further comprising:
receiving at said MLS file service module a request from said SLS user processor for a non-encrypted unclassified data file;
responsive to said request, accessing with said MLS file system containing said unclassified data file; and
serving said unclassified data file to said SLS user processor in plain-text form.
12. The method according to claim 1, further comprising selecting said cryptographic processor to include a trusted microprocessor and a trusted operating system executing on said trusted cryptographic processor.
13. The method according to claim 1, further comprising selecting said SLS user processor to include a trusted microprocessor hardware.
14. The method according to claim 13, further comprising selecting said SLS user processor to include a single level trusted operating system.
15. The method according to claim 13, further comprising selecting said SLS user processor to include an untrusted operating system.
16. A system for providing a secure file service, comprising:
a multi-level secure (MLS) file service device comprising a cryptographic processor for
encrypting and decrypting a classified user data file;
an MLS file system hosted by said cryptographic processor containing classified user data files and accessible exclusively to said cryptographic processor; and
wherein said cryptographic processor comprises processing means responsive to a single level secure (SLS) user processor that is distinct from said cryptographic processor for accessing at least one classified user data file of a first security classification level from said secure file system, said classified user data file exclusively comprising at least one of user data and a user software application,
decrypting said classified user data file,
communicating, from said cryptographic processor, said classified user data file to said SLS user processor in decrypted form, and
automatically causing an erasure of said classified user data file from at least one data store used by said SLS user processor to temporarily store at least one of said user data and said user software application, in response to a transition of said SLS user processor from accessing said classified user data file of said first security classification level to accessing at least one user data file of a second security classification level;
and wherein said first and second security classification levels specify which classes of persons have access to rights to respective ones of said user data files.
17. The system according to claim 16, wherein said cryptographic processor further comprises one or more hardware based encryption services that facilitate the encryption and decryption of classified data files.
18. The system according to claim 17, wherein said hardware based encryption services are selected from the group consisting of a hardware implemented cryptographic algorithm, a random number generator, and an exponentiator.
19. The system according to claim 16, wherein said cryptographic processor exclusively limits said SLS user processor file access so that said SLS user processor can concurrently access only files defined within a single security classification level within said MLS file system.
20. The system according to claim 19, further comprising a client zeroizer responsive to said cryptographic processor, said client zeroizer configured for automatically zeroizing said data store used by said SLS user processor.
21. The system according to claim 16, further comprising a secure path defining a data communication link between said SLS user processor and said cryptographic processor.
22. The system according to claim 16, further comprising a secure human/machine interface operatively connected to said SLS user processor configured for communicating user commands to said SLS user processor and for displaying classified data files.
23. The system according to claim 16, wherein said SLS user processor further comprises processing means for communicating said classified user data file from said SLS user processor to said cryptographic processor.
24. The system according to claim 23, wherein said cryptographic processor further comprises processing means for encrypting said classified user data file, and for accessing said MLS file system with said cryptographic processor to store said classified user data file after encryption in said MLS file system.
25. The system according to claim 16, wherein at least one of said SLS user processor and said cryptographic processor further comprises processing means for authenticating a user responsive to at least one user authentication information.
26. The system according to claim 16, wherein said cryptographic processor further comprises means for accessing said MLS file system responsive to a request from said SLS user processor for an unclassified data file, and means for serving said unclassified data file to said SLS user processor.
27. The system according to claim 16, wherein said cryptographic processor is comprised of a trusted microprocessor and a trusted operating system executing on said trusted cryptographic processor.
28. The system according to claim 16, wherein said SLS user processor include a trusted microprocessor hardware.
29. The system according to claim 28, wherein said SLS user processor is comprised of a single level trusted operating system.
30. The system according to claim 28, wherein said SLS user processor comprises an untrusted operating system.
31. A multi-level secure (MLS) file services system, comprising:
an MLS file services device including
a cryptographic processor,
a MLS file system,
a client access interface configured to serve classified user data files stored in said MLS file system to a single level secure (SLS) client processor after decryption by said cryptographic processor, to receive said classified user data files from said SLS client processor, and to store said classified user data files in said MLS file system after encryption by said cryptographic processor,
a file system control interface, configured for authenticating a user prior to said client access interface serving classified user data files to said SLS client processor, and
a client zeroize/reset manager configured to automatically erase said classified user data files from a data store used by said SLS client processor for temporary storage of said classified user data files served by said client access interface when said SLS client processor transitions from accessing user files of a first security classification level to accessing user files of a second security classification level contained in said MLS file system, said user files exclusively comprising at least one of user data and a user software application;
wherein said first and second security classification levels specify which classes of persons have access rights to respective ones of said user data files.
32. The MLS file services system according to claim 31, further comprising a physically-secure data communication path for communicating said classified user data files between said client access interface and said SLS client processor.
33. The MLS file services module according to claim 32, wherein said physically secure data communication path is provided by co-locating said secure file services module in a physically secure enclosure that also contains said SLS client processor.
34. The MLS file services module according to claim 32, further comprising a trusted path between said file system control interface and a human/machine interface associated with said SLS client processor, said trusted path exclusive of said physically secure data communication path.
35. The MLS file services system according to claim 31, wherein said SLS client processor comprises untrusted software.
Patent Citations (69)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4227253(A) | 1980-10-01 | Ehrsam et al. | Applicant |
| US4493031(A) | 1985-01-01 | Silverio | Applicant |
| US4918728(A) | 1990-04-01 | Matyas et al. | Examiner |
| US5263168(A) | 1993-11-01 | Toms et al. | Applicant |
| US5283828(A) | 1994-02-01 | Saunders et al. | Examiner |
| US5369702(A) | 1994-11-01 | Shanton | Applicant |
| US5548646(A) | 1996-08-01 | Aziz et al. | Applicant |
| US5596718(A) | 1997-01-01 | Boebert et al. | Examiner |
| US5748744(A) | 1998-05-01 | Levy et al. | Applicant |
| US5802178(A) | 1998-09-01 | Holden et al. | Examiner |
| US5887064(A) | 1999-03-01 | Seysen | Applicant |
| US5956404(A) | 1999-09-01 | Schneier et al. | Applicant |
| US6081895(A) | 2000-06-01 | Harrison et al. | Examiner |
| US6092202(A) | 2000-07-01 | Veil et al. | Applicant |
| US6148401(A) | 2000-11-01 | Devanbu et al. | Applicant |
| US6282653(B1) | 2001-08-01 | Berstis et al. | Applicant |
| US6351817(B1) | 2002-02-01 | Flyntz | Applicant |
| US6378071(B1) | 2002-04-01 | Sasaki et al. | Examiner |
| US6378072(B1) | 2002-04-01 | Collins et al. | Examiner |
| US6671804(B1) | 2003-12-01 | Kent | Applicant |
| US6775778(B1) | 2004-08-01 | Laczko, Sr. et al. | Applicant |
| US7003674(B1) | 2006-02-01 | Hamlin | Applicant |
| US7028149(B2) | 2006-04-01 | Grawrock et al. | Applicant |
| US7069447(B1) | 2006-06-01 | Corder | Applicant |
| US7072937(B2) | 2006-07-01 | Neebe et al. | Applicant |
| US7302698(B1) | 2007-11-01 | Proudler et al. | Applicant |
| US7322042(B2) | 2008-01-01 | Srinivasan et al. | Applicant |
| US7380275(B2) | 2008-05-01 | Srinivasan et al. | Applicant |
| US7392398(B1) | 2008-06-01 | Shakkarwar | Examiner |
| US7543144(B2) | 2009-06-01 | Rensin et al. | Examiner |
| US7698552(B2) | 2010-04-01 | Wilson et al. | Applicant |
| US7765399(B2) | 2010-07-01 | O'Brien | Applicant |
| US7779252(B2) | 2010-08-01 | O'Brien et al. | Applicant |
| US7818574(B2) | 2010-10-01 | Fayad et al. | Applicant |
| US7979714(B2) | 2011-07-01 | Borsa et al. | Applicant |
| US2001/0044886(A1) | 2001-11-01 | Cassagnol et al. | Applicant |
| US2002/0059238(A1) | 2002-05-01 | Saito | Examiner |
| US2002/0099950(A1) | 2002-07-01 | Smith | Applicant |
| US2003/0046589(A1) | 2003-03-01 | Gregg | Examiner |
| US2003/0126434(A1) | 2003-07-01 | Lim et al. | Applicant |
| US2003/0163740(A1) | 2003-08-01 | Thjai et al. | Applicant |
| US2003/0204801(A1) | 2003-10-01 | Tkacik et al. | Applicant |
| US2004/0039924(A1) | 2004-02-01 | Baldwin et al. | Applicant |
| US2004/0044902(A1) | 2004-03-01 | Luthi | Applicant |
| US2004/0103288(A1) | 2004-05-01 | Ziv et al. | Applicant |
| US2005/0055524(A1) | 2005-03-01 | Gulick et al. | Applicant |
| US2005/0114687(A1) | 2005-05-01 | Zimmer et al. | Applicant |
| US2005/0132186(A1) | 2005-06-01 | Khan et al. | Applicant |
| US2006/0021007(A1) | 2006-01-01 | Rensin et al. | Examiner |
| US2006/0041755(A1) | 2006-02-01 | Pemmaraju | Applicant |
| US2006/0078109(A1) | 2006-04-01 | Akashika et al. | Applicant |
| US2006/0105740(A1) | 2006-05-01 | Puranik | Applicant |
| US2006/0195907(A1) | 2006-08-01 | Delfs et al. | Applicant |
| US2006/0248599(A1) | 2006-11-01 | Sack et al. | Applicant |
| US2006/0251258(A1) | 2006-11-01 | Lillie et al. | Applicant |
| US2006/0253711(A1) | 2006-11-01 | Kallmann | Applicant |
| US2007/0214364(A1) | 2007-09-01 | Roberts | Applicant |
| US2007/0226493(A1) | 2007-09-01 | O'Brien et al. | Applicant |
| US2007/0226517(A1) | 2007-09-01 | O'Brien et al. | Applicant |
| US2007/0250411(A1) | 2007-10-01 | Williams | Applicant |
| US2007/0283159(A1) | 2007-12-01 | Borsa et al. | Applicant |
| US2008/0022136(A1) | 2008-01-01 | Mattsson et al. | Examiner |
| US2009/0150899(A1) | 2009-06-01 | Tahan | Applicant |
| DE19633919(C1) | 1997-06-01 | Applicant | |
| EP471538 | 1992-02-01 | Applicant | |
| EP657820(A1) | 1995-06-01 | Applicant | |
| EP1085396 | 2001-03-01 | Applicant | |
| GB2336005(A) | 1999-10-01 | Applicant | |
| WO98/39876 | 1998-03-01 | Examiner |
Non-Patent Literature (13)
- Wiki: “Multilevel Security” Wikipedia, [online] Mar. 21, 2006, XP002446615 Internet. Retrieved from the Internet: URL:http://en.wikipedia.org/w/index.php?title=Multilevel—security&oldid=44733265> [retreived on Aug. 13, 2007].Applicant
- Wiki: “Multilevel Security” Wikipedia, [Online] Mar. 21, 2006, XP00246615 Internet Retrieved from the Internet: <URL:http://en.wikiedia.org/w/index.php?title=Multilevel—security&oldid=44733265>> [retrieved on Aug. 13, 2007].Applicant
- Schneier, Applied Cryptography Second Edition, 1996, John Wiley & Sons, Second Edition, pp. 513-514.Applicant
- U.S. Appl. No. 11/359,224, filed Feb. 22, 2006, Computer Architecture for a Handheld Electronic Device.Applicant
- U.S. Appl. No. 11/385,063, filed Mar. 21, 2006, Computer Architecture for a Handheld Electronic Device with a Shared Human-Machine Interface.Applicant
- U.S. Appl. No. 11/387,342, filed Mar. 23, 2006, Computer Architecture for an Electronic Device Providing a Secure File System.Applicant
- U.S. Appl. No. 11/387,991, filed Mar. 23, 2006, Computer Architecture for an Electronic Device Providing Single-Level Secure Access to Multi-Level Secure File System.Applicant
- U.S. Appl. No. 11/387,744, filed Mar. 23, 2006 Computer Architecture for an Electronic Device Providing SLS Access to MLS.Applicant
- U.S. Appl. No. 11/445,571, filed Jun. 2, 2006, Authentication and Access Control Device.Applicant
- Extended European Search Report mailed Jul. 13, 2011; Application Serial No. 11003076.4-2212 in the name of Harris Corporation.Applicant
- Meadows C Ed—Institute of Electrical and Electronics Engineers: “Extending the Brewer-Nash model to a multilevel context”, Proceedings of the Symposium on Research in Security and Privacy. Oakland, May 7-9, 1990; [Proceedings of the Symposium on Research in Security and Privacy],Los Alamitos, IEEE Comp. Soc. Press, US, vol. SYMP. 11, May 7, 1990, pp. 95-102, XP010020190, DOI: D0I:10.1109/RISP.1990.63842 ISBN: 978-0-8186-2060-7.Applicant
- Brewer D F C et al: “The Chinese Wall security policy”, Proceedings of the Symposium on Security and Privacy. Oakland, May 1-3, 1989; [Proceedings of the Symposium on Security and Privacy], Washington, IEEE Comp. Soc. Press, US, vol.-, May 1, 1989, pp. 206-214, XP010016022, DOI: D0I:10.1109/SECPRI.1989.36295 ISBN: 978-0-8186-1939-7.Applicant
- Fraser T: “LOMAC: Low Water-Mark integrity protection for COTS environments”, Security and Privacy, 2000. S&P 2000. Proceedings. 2000 IEEE Symposium on Berkeley, CA, USA May 14-17, 2000, Los Alamitos, CA, USA,IEEE Comput. Soc, US, May 14, 2000, pp. 230-245, XP010501138, DOI:DOI:10.1109/SECPRI.2000.848460 ISBN: 978-0-7695-0665-4.Applicant