Operational methods for a secure node in a computer network

• US 5,530,758 A
• Filed: 06/03/1994
• Issued: 06/25/1996
• Est. Priority Date: 06/03/1994
• Status: Expired due to Fees

• Current Assignee: General Dynamics C4 Systems Incorporated (General Dynamics Corporation)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Marino, Joseph T. Jr., Borgoyne, Ernest W. Jr.
• Primary Examiner(s): Gregory, Bernarr E.
• Application Number:
  US08/253,993
• Time in Patent Office: 753 Days
• Field of Search: 380/4, 380/9, 380/21, 380/23, 380/24, 380/25, 380/30, 380/49, 380/50, 380/20
• US Class Current: 713/150
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2211/009 Trust
• CPC Class Codes: G06F 2221/2101 Auditing as a secondary aspect
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices

Abstract

A computer network (20) including secure nodes (26) and unsecured nodes (28). The secure nodes (26) may communicate private data without compromising security provisions. The secure nodes (26) include a security kernel (36) that implements communication security provisions and a trusted operating system (40) that imposes computer data security provisions. A trusted interface (44) is used to transfer data between the trusted operating system (40) and the security kernel (36). In addition, this interface (44) insures that computer security attributes are compatible with communication security attributes. If incompatibilities are discovered, requested communications are thwarted and audit records for the security linkage violations are recorded.

Claims

1. A method of operating a secure node in a computer network, said method comprising steps of:

(a) performing a trusted process on said secure node, said trusted process associating security attributes with data provided thereby;

(b) establishing a security kernel for managing communications with other nodes on said network, said security kernel associating communication security attributes with network communication channels; and

(c) determining whether said trusted process data security attributes are compatible with said communication security attributes.

2. A method as claimed in claim 1 wherein said step (c) is performed in a trusted interface between said trusted process and said security kernel.

3. A method as claimed in claim 1 wherein said trusted process is a trusted operating system that manages the operations of a plurality of applications.

4. A method as claimed in claim 3 wherein:

at least one of said applications imports data;

said trusted process additionally associates data security attributes with said at least one application; and

said step (c) additionally comprises a step of resolving whether data requested to be imported into said at least one application are associated with communication security attributes that are compatible with said data security attributes for said at least one application.

5. A method as claimed in claim 1 wherein said step (c) comprises substeps of:

(c1) evaluating a request to transmit said data from said node to a destination entity; and

(c2) resolving whether said destination entity is authorized to receive said data.

6. A method as claimed in claim 5 wherein said step (c) additionally comprises substeps of:

(c3) generating an audit record when said destination entity is not authorized to receive said data; and

(c4) providing said audit record to said trusted process.

7. A method as claimed in claim 5 wherein said step (c) additionally comprises a step (d) of resolving whether a secure channel is available for transmitting said data to said destination entity.

8. A method as claimed in claim 5 wherein said step (b) comprises substeps of:

(b1) initializing a communication channel between said process and said destination entity; and

(b2) associating a security attribute with said communication channel.

9. A method as claimed in claim 8 additionally comprising steps of:

(d) transmitting said data through said channel; and

(e) continuously verifying, as said data are being transmitted, that said channel security attribute is compatible with said data security attribute.

10. A method as claimed in claim 9 additionally comprising a step (f) of packaging said data in accordance with a predetermined security protocol.

11. A method as claimed in claim 5 wherein said step (c) additionally comprises a substep (c3) of identifying a mail server to use for storing said data.

12. A method as claimed in claim 11 wherein said step (c) additionally comprises a substep (c4) of verifying that a security certificate for said node has been posted with said mail server.

13. A method as claimed in claim 1 additionally comprising a step (d) of posting a security certificate at a mail server node of said network, said security certificate being used for encrypting mail data.

14. A method of operating a computer network having unsecured communication links to remotely store secure mail data, said method comprising steps of:

(a) posting a security certificate from a destination node at a common node;

(b) requesting to transmit mail data from a source node to said destination node via remote storage in a mail server node;

(c) obtaining, at said source node in response to said requesting step, said security certificate from said common node;

(d) encrypting said mail data in response to said security certificate to provide encrypted mail data; and

(e) sending, after said step (d), said encrypted mail data to said mail server node for storage therein.

15. A method as claimed in claim 14 additionally comprising steps of:

(f) identifying processes which operate at said source node and which are authorized to send mail;

(g) verifying that said source node is authorized to post a source security certificate; and

(h) posting said source security certificate from said source node at said common node.

16. A method as claimed in claim 14 additionally comprising steps of:

(f) sending a message from said destination node to said mail server, said message requesting said mail server to send said encrypted mail data to said destination node;

(g) transmitting said encrypted mail data from said mail server to said destination node in response to said sending step; and

(h) decrypting said encrypted mail data in response to said security certificate.

17. A method as claimed in claim 16 wherein said source node and said destination node are the same node.

18. A method as claimed in claim 16 wherein said source node and said destination node are different nodes.

19. A method as claimed in claim 14 wherein said step (b) additionally comprises, prior to said step (c), substeps of:

(b1) verifying, at said source node, that said destination node is authorized to receive said encrypted mail data; and

(b2) identifying, in response to an identification of said destination node, an address for said mail server.

20. A method as claimed in claim 19 wherein said substep (b2) additionally comprises a substep (b3) of verifying that said security certificate for said source node has been posted at said common node.

21. A method as claimed in claim 14 wherein:

said step (c) comprises a substep (c1) of establishing a communication channel between said mail server node and said source node, said communication channel having a communication security attribute associated therewith;

data security attributes are associated with said mail data at said source node; and

said step (e) comprises a substep (e1) of determining whether said data security attributes are compatible with said communication security attribute.

22. A method of operating a secure node in a computer network, said method comprising steps of:

(a) running a trusted operating system which manages an application that transmits data away from said secure node, said trusted operating system associating data security attributes with said data;

(b) establishing a security kernel for managing communication channels with other nodes on said network, said security kernel associating communication security attributes with said communication channels;

(c) evaluating, in an interface between said trusted operating system and said security kernel, a request from said application to transmit said data to a destination entity; and

(d) determining, in said interface, whether said data security attributes are compatible with said communication security attributes.

23. A method as claimed in claim 22 wherein said step (d) comprises a substep (d1) of resolving whether said destination entity is authorized to receive said data.

24. A method as claimed in claim 22 wherein said step (c) comprises a substep (c1) of resolving whether a secure channel is available for transmitting said data to said destination entity.

25. A method as claimed in claim 22 wherein said step (b) comprises substeps of:

(b1) initializing a communication channel between said process and said destination entity; and

(b2) associating a communication security attribute with said channel.

26. A method as claimed in claim 25 additionally comprising steps of:

(e) transmitting said data through said channel; and

(f) continuously verifying, as said data are being transmitted, that said communication security attribute is compatible with said data security attributes.

27. A method as claimed in claim 22 wherein said step (c) additionally comprises a substep (c1) of identifying a mail server to use for temporarily storing said data.