IP Library Granted Patent US 8,621,594
Granted Patent B2
US 8,621,594 · App. 13/100,788 · Granted Dec 31, 2013

Method and system for secure communication

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,621,594
App. No.
13/100,788
Granted
Dec 31, 2013
Kind
B2
Abstract

A method and system for secure communication is presented. A virtual private proxy is generated based on an agreement between a first entity and a second entity. A first virtual private proxy is associated with the first entity and a second virtual private proxy is associated with the second entity. Data associated with the first entity is monitored at the virtual private proxy. Whether the data violates the agreement is determined and communication of the data from the first virtual private proxy to the second virtual private proxy is disallowed when the data violates the agreement.

Claims (63)

1. A secure network communication method, the method comprising:

accessing, by a secure switch, a secure network communication agreement between a first entity and a second entity;

generating, by the secure switch, a first virtual private proxy and a second virtual private proxy;

establishing a first secure connection between the first virtual private proxy and the first entity;

prohibiting remote connections to the first entity other than the first secure connection;

establishing a second secure connection between the second virtual private proxy and the second entity;

establishing a logical connection between the first virtual private proxy and the second virtual private proxy; and

generating an alarm when transaction data transmitted over the logical connection is not in compliance with the agreement.

2. The method of claim 1 , wherein establishing the first secure connection occurs in response to receiving a connection request from a private session manager.

3. The method of claim 1 , wherein generating the alarm further comprises:

generating alarm data selected from a portion of the transaction data that is not in compliance with the agreement, a portion of the agreement associated with the alarm, data indicative of a source of the transaction data that is not in compliance with the agreement, and data indicative of a time associated with the alarm.

4. The method of claim 1 , further comprising:

evaluating whether the transaction data is explicitly allowed by the agreement; and

generating the alarm when the transaction data is not explicitly allowed by the agreement.

5. The method of claim 1 , further comprising:

evaluating whether the transaction data is explicitly forbidden by the agreement; and

generating the alarm when the transaction data is explicitly forbidden by the agreement.

6. The method of claim 5 , wherein transaction data that is explicitly forbidden by the agreement includes data selected from executable data, data indicative of a signature of a malicious program, and data indicative of an intrusion attempt.

7. The method of claim 1 , wherein the agreement specifies a parameter selected from a timeout value, a transport protocol, a transport security protocol, and a document exchange protocol.

8. The method of claim 1 , further comprising:

receiving first electronic commerce information for the first entity and second electronic commerce information for the second entity; and

modifying the agreement based on the first electronic commerce information and the second electronic commerce information.

9. A secure switch, comprising:

a processor configured to access storage media including program instructions, executable by the processor, the program instructions including instructions to:

access an agreement for secure network communication between a first entity and a second entity, the agreement based on a first profile for the first entity and a second profile for the second entity;

generate a first virtual private proxy and a second virtual private proxy;

establish a first secure connection between the first virtual private proxy and the first entity;

exclude all remote connections to the first entity other than the first secure connection;

establish a second secure connection between the second virtual private proxy and the second entity;

establish a logical connection between the first virtual private proxy and the second virtual private proxy; and

monitor, for compliance with the agreement, transaction data arriving at the first virtual private proxy and the second virtual private proxy for transmission over the logical connection between the first entity and the second entity.

10. The secure switch of claim 9 , wherein the program instructions include instructions to:

recognize a violation of the agreement when the transaction data is not in compliance with the agreement;

generate alarm data associated with the violation, wherein the alarm data is selected from a portion of the transaction data that is not in compliance with the agreement, a portion of the agreement associated with the violation, an indication of a source of the transaction data associated with the violation, and a time associated with the violation.

11. The secure switch of claim 9 , wherein the program instructions include instructions to:

when the transaction data violates the agreement, block transmission of the transaction data between the first entity and the second entity.

12. The secure switch of claim 9 , wherein the program instructions include instructions to:

when the transaction data complies with the agreement, allow transmission of the transaction data between the first entity and the second entity.

13. The secure switch of claim 9 , wherein the first profile includes electronic commerce information for the first entity and the second profile includes electronic commerce information for the second entity.

14. The secure switch of claim 13 , wherein the program instructions include instructions to:

receive the first profile for the first entity and the second profile for the second entity; and

modify the agreement based on the first profile and the second profile.

15. The secure switch of claim 14 , wherein the instructions to modify the agreement include instructions to generate the agreement.

16. Non-transitory storage media including program instructions for implementing secure network communications at a secure switch, the program instructions including instructions executable to:

access an agreement for secure network communication between a first entity and a second entity, the agreement based on a first profile for the first entity and a second profile for the second entity;

generate a first virtual private proxy and a second virtual private proxy;

establish a first secure connection between the first virtual private proxy and the first entity;

exclude all remote connections to the first entity other than the first secure connection;

establish a second secure connection between the second virtual private proxy and the second entity;

establish a logical connection between the first virtual private proxy and the second virtual private proxy;

monitor, for compliance with the agreement, transaction data arriving at the first virtual private proxy and the second virtual private proxy for transmission over the logical connection;

when the transaction data is not in compliance with the agreement, recognize a violation of the agreement and generate alarm data associated with the violation; and

when the transaction data complies with the agreement, allow transmission of the transaction data between the first entity and the second entity.

17. The storage media of claim 16 , wherein the program instructions include instructions executable to:

when the transaction data is not in compliance with the agreement, block transmission of the transaction data between the first entity and the second entity.

18. The storage media of claim 16 , wherein the alarm data include data selected from a portion of the transaction data that is not in compliance with the agreement, a portion of the agreement associated with the violation, an indication of a source of the transaction data that is not in compliance with the agreement, and a time of the violation.

19. The storage media of claim 16 , wherein the program instructions include instructions executable to:

receive the first profile for the first entity and the second profile for the second entity; and

modify the agreement based on the first profile and the second profile,

wherein the agreement specifies information selected from a timeout value, a transport protocol, a transport security protocol, and a document exchange protocol.

20. The storage media of claim 16 , wherein the program instructions include instructions executable to:

receive a connection request from a private session manager; and

disclose an identifier for the first virtual private proxy only to the private session manager.

Assignments (11)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 26, 2021
From: SOFTWARE LABS CAMPUS UNLIMITED COMPANY
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 056396/0942 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 11, 2020
From: IBM TECHNOLOGY CORPORATION
To: SOFTWARE LABS CAMPUS UNLIMITED COMPANY
Reel/Frame 053452/0537 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ERRONEOULY LISTED PATENT ON THE SCHEDULE A. PATENT NUMBER 7,792,767 WAS REMOVED FROM THE SCHEDULE A. PREVIOUSLY RECORDED AT REEL: 051170 FRAME: 0255. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Mar 19, 2020
From: IBM INTERNATIONAL GROUP B.V.
To: IBM INTERNATIONAL C.V.
Reel/Frame 052190/0394 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ERRONEOUSLY LISTEDPATENT ON THE SCHEDULE A. PATENT NUMBER 7,792,767WAS REMOVED FROM THE SCHEDULE A PREVIOUSLY RECORDED ON REEL 051170 FRAME 0722. ASSIGNOR(S) HEREBY CONFIRMS THE PATENTNUMBER 7,792,767 WAS ERRONEOUSLY LISTED ON THESCHEDULE A. Recorded Mar 19, 2020
From: IBM INTERNATIONAL L.P.
To: IBM TECHNOLOGY CORPORATION
Reel/Frame 052190/0464 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ERRONEOUS LISTED PATENT NUMBER 7,792,767 ON THE SCHEDULE A PREVIOUSLY RECORDED AT REEL: 051170 FRAME: 0745. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Mar 19, 2020
From: IBM INTERNATIONAL C.V.
To: IBM INTERNATIONAL L.P.
Reel/Frame 052190/0986 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 3, 2019
From: IBM INTERNATIONAL GROUP B.V.
To: IBM INTERNATIONAL C.V.
Reel/Frame 051170/0255 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 3, 2019
From: IBM INTERNATIONAL L.P.
To: IBM TECHNOLOGY CORPORATION
Reel/Frame 051170/0722 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 3, 2019
From: IBM INTERNATIONAL C.V.
To: IBM INTERNATIONAL L.P.
Reel/Frame 051170/0745 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 9, 2013
From: STERLING COMMERCE, INC.
To: IBM INTERNATIONAL GROUP, B.V.
Reel/Frame 030758/0376 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 20, 2013
From: STERLING COMMERCE, INC.
To: IBM INTERNATIONAL GROUP B.V.
Reel/Frame 030662/0729 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 2, 2013
From: FENTON, CHARLES S.; SHAFER, KEITH E.
To: STERLING COMMERCE, INC.
Reel/Frame 030336/0040 →