INTELLIGENT INTEGRATED NETWORK SECURITY DEVICE FOR HIGH-AVAILABILITY APPLICATIONS

• US 20130067268A1
• Filed: 09/14/2012
• Published: 03/14/2013
• Est. Priority Date: 02/08/2002
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: ZUK, Nir, Mao, Yu Ming, Guruswamy, Kowsik
• Granted Patent: US 8,631,113 B2
• Time in Patent Office: Days
• US Class Current: 714/4.11
• CPC Class Codes: G06F 11/2002 where interconnections or communication control functionality are redundant flexible arrangements for bus networks involving redundancy H04L12/40176
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/0236 Filtering by address, protocol, port number or service, e.g. IP-address or URL
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/1416 Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Methods and apparatuses for inspecting packets are provided. A primary security system may be configured for processing packets. The primary security system may be operable to maintain flow information for a group of devices to facilitate processing of the packets. A secondary security system may be designated for processing packets upon a failover event. Flow records may be shared from the primary security system with the secondary security system.

Claims

1-39. -39. (canceled)

40. A method comprising:

storing, by a first device and in a memory of the first device, first information relating to the first device operating as a primary security system;

storing, by the first device and in the memory of the first device, second information relating to the first device operating as a secondary security system,

the first device operating as the secondary security system when a failover event, associated with a second device, has occurred,

the second device being different than the first device;

determining, by the first device, whether the failover event has occurred;

processing, by the first device and using the first information, first packets when the failover event has not occurred; and

processing, by the first device and using the second information, second packets when the failover event has occurred,

the second packets being intended for the second device.

41. The method of claim 40, where determining whether the failover event has occurred includes:

receiving status information relating to the second device; and

determining whether the failover event has occurred based on receiving the status information.

42. The method of claim 40, where storing the second information includes:

receiving the second information from the second device; and

storing the second information after receiving the second information.

43. The method of claim 40, further comprising:

transmitting a portion of the first information to the second device at predetermined time intervals,

the second device providing failover support, for the first device, using the portion of the first information.

44. The method of claim 40, further comprising:

updating the first information to obtain updated first information; and

transmitting the updated first information to the second device,

the second device providing failover support, for the first device, based on the updated first information.

45. The method of claim 40, further comprising:

determining that the failover event has occurred,

where processing the second packets includes;

receiving, after determining that the failover event has occurred, the second packets,

the second packets being associated with a session processed by the second device prior to the failover event.

46. The method of claim 40, where determining whether the failover event has occurred includes determining whether the failover event has occurred after the second information has been received.

47. A device comprising:

a memory to store;

first information relating to the device processing packets in a first flow of packets, and

second information relating to the device processing packets in a second flow of packets,

the second flow of packets being different than the first flow of packets,

the packets, in the second flow of packets, being intended for processing by another device; and

one or more processors to;

determine whether a failover event, associated with the other device, has occurred,

process, using the first information, the packets in the first flow of packets when the failover event has not occurred, and

process, using the second information, the packets in the second flow of packets when the failover event has occurred.

48. The device of claim 47, where, when determining whether the failover event has occurred, the one or more processors are to:

determine that status information, relating to the other device, has not been received; and

determine that the failover event has occurred based on determining that the status information has not been received.

49. The device of claim 47, where the one or more processors are further to:

determine that the failover event has occurred based on one of;

a failure of the other device, or

a failure of a link to the other device.

50. The device of claim 47, where the one or more processors are further to:

receive the second information prior to the failover event occurring.

51. The device of claim 47, where the one or more processors are further to:

transmit, at particular time intervals, a portion of the first information to the other device,

the other device processing, using the portion of the first information, the packets in the first flow of packets when a failover event, associated with the device, occurs.

52. The device of claim 47, where, when transmitting the portion of the first information, the one or more processors are further to:

update the first information to obtain updated first information, and

transmit a portion of the updated first information to the other device.

53. The device of claim 47, where the one or more processors are further to:

determine that the failover event has occurred,

the packets in the second flow of packets being processed, using the second information, based on determining that the failover event has occurred, and

resume processing the packets in the first flow of packets when the failover event is corrected.

54. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions which, when executed by a first device, cause the first device to store first information relating to the first device processing packets in a first flow of packets;

one or more instructions which, when executed by the first device, cause the first device to store second information relating to the first device processing packets in a second flow of packets,

the second flow of packets being different than the first flow of packets,

the packets, in the second flow of packets, being intended for processing by a second device that is different than the first device;

one or more instructions which, when executed by the first device, cause the first device to determine whether a failover event, associated with the second device, has occurred;

one or more instructions which, when executed by the first device, cause the first device to process, using the first information, the packets in the first flow of packets when the failover event has not occurred; and

one or more instructions which, when executed by the first device, cause the first device to process, using the second information, the packets in the second flow of packets when the failover event has occurred.

55. The non-transitory computer-readable medium of claim 54, the instructions further comprising:

one or more instructions which, when executed by the first device, cause the first device to determine that the failover event has occurred;

one or more instructions which, when executed by the first device, cause the first device to determine that the failover event is corrected; and

one or more instructions which, when executed by the first device, cause the first device to resume processing the packets in the first flow of packets based on determining that the failover event is corrected.

56. The non-transitory computer-readable medium of claim 54, the instructions further comprising:

one or more instructions which, when executed by the first device, cause the first device to receive the second information, from the second device, prior to the failover event occurring.

57. The non-transitory computer-readable medium of claim 54, where the one or more instructions to determine whether the failover event has occurred include:

one or more instructions which, when executed by the first device, cause the first device to transmit information to the second device to determine whether the second device is operational; and

one or more instructions which, when executed by the first device, cause the first device to determine whether the failover event has occurred based on transmitting the information to the second device.

58. The non-transitory computer-readable medium of claim 54, the instructions further comprising:

one or more instructions which, when executed by the first device, cause the first device to receive information relating to a failure of the second device from a third device that monitors the second device,

the third device being different than the first device and the second device; and

one or more instructions which, when executed by the first device, cause the first device to determine that the failover event has occurred based on receiving the information relating to the failure of the second device.

59. The non-transitory computer-readable medium of claim 54, the instructions further comprising:

one or more instructions which, when executed by the first device, cause the first device to determine that the failover event has occurred,

where the one or more instructions to process, using the second information, the packets in the second flow of packets when the failover event has occurred include;

one or more instructions which, when executed by the first device, cause the first device to receive, after determining that the failover event has occurred, the packets in the second flow of packets,

where the packets, in the second flow of packets, are associated with a session processed by the second device prior to the failover event.