IP Library Granted Patent US 8,353,023
Granted Patent B2
US 8,353,023 · App. 13/250,950 · Granted Jan 8, 2013

Identity-based-encryption message management system

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,353,023
App. No.
13/250,950
Granted
Jan 8, 2013
Kind
B2
Abstract

Systems and methods for managing email are provided. Some of the email may be encrypted using identity-based-encryption (IBE) techniques. When an incoming IBE-encrypted message for a recipient in an organization is received by a gateway at the organization, the gateway may request an IBE private key from an IBE private key generator. The IBE private key generator may generate the requested IBE private key for the gateway. The gateway may use an IBE decryption engine to decrypt the incoming message. The decrypted message can be scanned for viruses and spam and delivered to the recipient. Outgoing email messages can also be processed. If indicated by message attributes or information provided by a message sender, an outgoing message can be encrypted using an IBE encryption engine and the IBE public key of a desired recipient.

Claims (40)

1. A method of processing incoming email messages to an organization, wherein the organization has a network, a gateway, a private key generator, and a plurality of recipients and wherein the gateway, private key generator, and recipients are connected by the network, the method comprising:

receiving an encrypted email message for a recipient in the organization with the gateway;

with the gateway, using recipient credential information to request a private key of the recipient from the private key generator;

using the recipient credential information at the private key generator to determine whether the gateway is authorized to obtain the requested private key, and, if the gateway is authorized, generating the requested private key in real time;

providing the private key that has been generated by the private key generator to the gateway; and

at the gateway, using the private key to decrypt the email message.

2. The method defined in claim 1 wherein the gateway has an identity-based-encryption (IBE) decryption engine and wherein using the private key to decrypt the email message comprises using the IBE decryption engine to decrypt the email message at the gateway.

3. The method defined in claim 1 wherein the gateway is connected to the Internet by a firewall, the method further comprising receiving the encrypted email message with the gateway through the firewall.

4. A method of processing email messages in an organization, wherein the organization has a network, a gateway, a private key generator, and a plurality of recipients and wherein the gateway, private key generator, and recipients are connected by the network, the method comprising:

receiving an encrypted email message for a recipient in the organization with the gateway;

with the gateway, using recipient credential information to request a private key of the recipient from the private key generator;

at the gateway, receiving the private key from the private key generator; and

at the gateway, using the private key to decrypt the email message.

5. The method defined in claim 4 wherein the gateway has an identity-based-encryption (IBE) decryption engine and wherein using the private key to decrypt the email message comprises using the IBE decryption engine to decrypt the email message at the gateway.

6. The method defined in claim 4 wherein the gateway is connected to the Internet by a firewall, the method further comprising receiving the encrypted email message with the gateway through the firewall.

7. The method defined in claim 4 further comprising:

at the gateway, scanning the decrypted email message for viruses to produce a scanned version of the email message; and

providing the scanned email message from the gateway to the recipient.

8. The method defined in claim 7 further comprising:

processing the decrypted email message at the gateway to determine whether to edit the email message; and

if it is determined that the email message is to be edited, using a message editor at the gateway to edit the email message.

9. The method defined in claim 8 wherein processing the decrypted email message at the gateway to determine whether to edit the email message comprises determining that the email message includes an attachment that contains a virus and wherein using the message editor at the gateway to edit the email message comprises removing the attachment.

10. The method defined in claim 7 further comprising:

processing the decrypted email message at the gateway to determine whether to generate a notification; and

if it is determined that a notification is to be generated, using the gateway to generate the notification.

11. The method defined in claim 10 wherein processing the decrypted email message at the gateway to determine whether to generate a notification comprises determining that the email message includes an attachment that contains a virus and wherein using the gateway to generate the notification comprises generating an alarm.

12. The method defined in claim 4 further comprising:

processing the decrypted email message at the gateway to determine whether to generate a notification; and

if it is determined that a notification is to be generated, using the gateway to generate the notification.

13. The method defined in claim 12 wherein processing the decrypted email message at the gateway to determine whether to generate a notification comprises processing the decrypted email message at the gateway to determine whether the email message violates an organizational policy and wherein using the gateway to generate the notification comprises sending a notification message to an appropriate party that identifies the organizational policy violation.

14. The method defined in claim 12 wherein processing the decrypted email message at the gateway to determine whether to generate a notification comprises processing the decrypted email message at the gateway to determine whether the email message contains a sensitive document as an attachment.

15. The method defined in claim 4 further comprising:

processing the decrypted email message at the gateway to determine whether to edit the email message; and

if it is determined that the email message is to be edited, using a message editor at the gateway to edit the email message.

16. The method defined in claim 15 wherein processing the decrypted email message at the gateway to determine whether to edit the email message comprises determining that the email message includes sensitive information and wherein using the message editor at the gateway to edit the email message comprises removing the sensitive information.

17. The method defined in claim 4 further comprising:

processing the decrypted email message at the gateway to determine whether to archive the email message; and

if it is determined that the email message is to be archived, using a database controller to save a copy of the email message in a database of the organization.

18. The method defined in claim 17 wherein processing the decrypted email message at the gateway to determine whether to archive the email message comprises determining that the email message includes a virus and wherein using the database controller to save the copy of the email message in the database of the organization comprises saving a copy of the email message that includes the virus.

19. The method defined in claim 17 wherein processing the decrypted email message at the gateway to determine whether to archive the email message comprises determining that at least one condition is satisfied, wherein the at least one condition is selected from the group consisting of: the email message contains a particular type of data, the email message contains patient data, the email contains medical data, the email message originated from a particular sender, the email message originated from a physician, the recipient that the email message is destined to is a particular recipient, and the recipient that the email message is destined to is a patient, and wherein using the database controller to save the copy of the email message in the database of the organization comprises saving of copy of the email message.

Assignments (8)
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0577 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC)
Reel/Frame 063560/0001 →
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC); BORLAND SOFTWARE CORPORATION; MICRO FOCUS (US), INC.; SERENA SOFTWARE, INC; ATTACHMATE CORPORATION; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062746/0399 →
CHANGE OF NAME Recorded Dec 17, 2018
From: VOLTAGE SECURITY, INC.
To: VOLTAGE SECURITY, LLC
Reel/Frame 051198/0611 →
MERGER AND CHANGE OF NAME Recorded Dec 17, 2018
From: VOLTAGE SECURITY, LLC; ENTIT SOFTWARE LLC
To: ENTIT SOFTWARE LLC
Reel/Frame 051199/0074 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ENTIT SOFTWARE LLC; ARCSIGHT, LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0577 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ATTACHMATE CORPORATION; BORLAND SOFTWARE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE, INC.; ENTIT SOFTWARE LLC; ARCSIGHT, LLC; SERENA SOFTWARE, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0718 →
RELEASE OF SECURITY INTEREST Recorded Feb 27, 2015
From: VENTURE LENDING & LEASING VI, INC.; VENTURE LENDING & LEASING VII, INC.
To: VOLTAGE SECURITY, INC.
Reel/Frame 035110/0726 →
SECURITY AGREEMENT Recorded Feb 7, 2014
From: VOLTAGE SECURITY, INC.
To: VENTURE LENDING & LEASING VI, INC.; VENTURE LENDING & LEASING VII, INC.
Reel/Frame 032170/0273 →