Patent Application
20090157823
This invention relates generally to secure network communications. More particularly, this invention relates to a technique for supporting secure email services using multiple protocols, including proprietary and open protocols.
The configuration of
In view of this problem, it would be desirable to provide a technique that allows a secure email policy enforcement server to operate with an email server using an unsupported protocol. More particularly, it would be desirable to provide a technique to facilitate encryption and decryption operations in connection with an email server using an unsupported protocol.
The invention includes a computer readable storage medium with executable instructions to identify when a security policy cannot be applied by a supported secure email machine to a received email message and thus the email message is routed to an auxiliary secure email machine. Secure email policies are applied to the email message at the auxiliary secure email machine. The email message is then routed from the auxiliary secure email machine to the supported secure email machine.
The invention also includes a computer readable storage medium with executable instructions to determine that a security policy cannot be applied by a supported secure email machine to a generated email message and thus the email message is routed to an auxiliary secure email machine. Secure email policies are applied to the email message at the auxiliary secure email machine. The email message is directed from the auxiliary secure email machine to the supported secure email machine for routing to a recipient.
The invention is more fully appreciated in connection with the following detailed description taken in conjunction with the accompanying drawings, in which:
Like reference numerals refer to corresponding parts throughout the several views of the drawings.
The networked machines 204 may also be any type of client machine, including, for example, a personal computer, a personal digital assistant, and the like. The email server 202 and the networked machines 204 are linked by a transmission infrastructure 205, which may be any wired or wireless transmission medium.
Also connected to the transmission infrastructure 205 is a client machine 206, which is configured with software to implement operations of the invention. An auxiliary secure email machine 208, configured with software to implement operations of the invention, is also connected to the transmission infrastructure 205. The auxiliary secure email machine 208 facilitates the encryption and decryption of email messages. That is, the machine 208 participates in at least a portion of the process of encrypting or decrypting email messages associated with the client 206. Thus, the auxiliary secure email machine 208 operates as a secure email support facility for an unsupported protocol (i.e., a protocol that is not used between the email server 202 and a supported secure email machine 204). The auxiliary secure email machine 208 may also implement digital signature policies, as discussed below.
The email server 202 includes standard components, such as a network connection circuit 210, which is linked to a CPU 212 over a bus 214. A memory 216 is also connected to the bus 214. The memory 216 stores an email service module 218 to implement standard email operations.
The client machine 206 also includes standard components, such as a network connection circuit 220, a CPU 2 and a bus 224. A memory 226 is also connected to the bus 224. The memory 226 stores a set of executable instructions used to implement operations of the invention. The executable instructions include an unsupported email service module 228. The memory 230 also stores executable instructions in the form of a message communication module 230. This module, implemented in accordance with an embodiment of the invention, includes executable instructions to facilitate the routing of messages to the auxiliary secure email machine 208. In one embodiment, these communications are implemented using an open communication protocol, such as the Simple Object Access Protocol (SOAP). SOAP is a protocol specification for invoking methods. SOAP codifies the existing practice of using XML and HTTP as a method invocation mechanism. The SOAP specification also mandates an XML vocabulary that is used for representing method parameters, return values, and exceptions.
The auxiliary secure email machine 208 includes standard components, such as a network connection circuit 246, a CPU 248, and a bus 250. A memory 252 is also connected to the bus 250. The memory 252 stores executable instructions used to implement operations of the invention. In this embodiment, the memory stores a message communication module 254. The message communication module 254 includes executable instructions to communicate with the client machine 206. In one embodiment, these communications are implemented using an open communication protocol, such as the Simple Object Access Protocol (SOAP). The memory 252 also stores a policy application module 256. This module includes executable instructions to implement secure email policies (cryptographic policies), such as encryption, decryption, signatures, routing restrictions, and the like.
Various modules for implementing operations of the invention have now been introduced. It should be appreciated that these modules are exemplary. The operations of the invention may be implemented in any number of modules or configurations. Similarly, the network location at which these modules execute is insignificant. It is the operations of the invention, regardless of how they are implemented or where they are implement that are significant.
The first processing operation shown in
If the secure policy cannot be applied (302—NO), then the email is sent to the auxiliary secure email machine 208 using a second protocol (312). This operation may be implemented with the message communication module 230. In one embodiment, the message communication module 230 includes executable instructions to encapsulate the message in an open communication protocol, such as a SOAP communication. The message communication module 254 of the auxiliary secure email machine 208 receives the open protocol communication and passes it to the policy application module 256, which applies secure email policies (314) to the message. For example, if the client machine 206 does not have a private key, the policy application module 256 requests the private key from a network resource. The policy application module 256 then decrypts the message using the key. If the message is also signed, the policy application module 256 requests the sender's public key to verify the signature. Upon receipt of the public key, the policy application module 256 verifies the signature.
The decrypted message and the verified signature, if applicable, is then supplied to the message communication module 254, which routes the message to the supported secure email machine 204, which routes the email to the client 308. In one embodiment, the auxiliary secure email machine 208 routes the email directly to the client machine 206 using an open protocol (e.g., a second protocol) (316). The message communication module 230 of the client machine 206 receives the message. Executable instructions associated with the module strip the open protocol package to render the original message. The client machine can then open the original message (310).
The message communication module 230 may use any number of techniques to route the incoming messages to the auxiliary secure email machine 208. As previously indicated, an open protocol, such as the SOAP protocol may be advantageously used. However, other protocols, including proprietary protocols may be used for the communications between the client machine 206 and the auxiliary secure email machine 208, although such implementations are more cumbersome.
If the protocol is not supported (402—NO), then the message is routed to the auxiliary secure email machine 208 using a second protocol (410). An open protocol, such as the SOAP protocol, is preferably used to implement this operation. That is, the message communication module 230 utilizes executable instructions to encapsulate the email message as a SOAP message.
The message communication module 254 of the auxiliary secure email machine 208 receives the message and passes it to the policy application module 256. The policy application module 256 then applies secure email policies to the email (412). For example, the policy application module 256 includes executable instructions to request the public key for the message recipient. The policy application module 256 then encrypts the message to the recipient's public key. The policy application module 256 then sends the email using the second protocol (414). For example, the email is sent to the supported secure email machine, which then routes the email (416).
In an alternate embodiment of the invention, the determination of whether a protocol is supported is performed at the email server 202. Similarly, routing to the supported secure email machine 204 or the auxiliary secure email machine 28 is initiated from the email server 202.
An embodiment of the present invention relates to a computer storage product with a computer-readable medium having computer code thereon for performing various computer-implemented operations. The media and computer code may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well known and available to those having skill in the computer software arts. Examples of computer-readable media include, but are not limited to: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROMs and holographic devices; magneto-optical media such as floptical disks; and hardware devices that are specially configured to store and execute program code, such as application-specific integrated circuits (“ASICs”), programmable logic devices (“PLDs”) and ROM and RAM devices. Examples of computer code include machine code, such as produced by a compiler, and files containing higher-level code that are executed by a computer using an interpreter. For example, an embodiment of the invention may be implemented using Java, C++, or other object-oriented programming language and development tools. Another embodiment of the invention may be implemented in hardwired circuitry in place of, or in combination with, machine-executable software instructions.
The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the invention. However, it will be apparent to one skilled in the art that specific details are not required in order to practice the invention. Thus, the foregoing descriptions of specific embodiments of the invention are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed; obviously, many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, they thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the following claims and their equivalents define the scope of the invention.
