Dynamic group creation and traffic flow registration under a group in a group key infrastructure

• US 9,009,302 B2
• Filed: 02/21/2012
• Issued: 04/14/2015
• Est. Priority Date: 02/21/2012
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Detienne, Frederic R. P., Sethi, Pratima, Wijnands, Ijsbrand
• Primary Examiner(s): KIM, EDWARD J
• Application Number:
  US13/400,841
• Publication Number:
  US 20130219035A1
• Time in Patent Office: 1,148 Days
• Field of Search: 709/223, 709/224, 709/225, 709/230, 709/232, 709/237, 709/231
• US Class Current: 709/224
• CPC Class Codes: H04L 63/065 for group communications cryptographic mechanisms or cryptographic arrangements for key management involving conference or group key H04L9/0833
• CPC Class Codes: H04L 9/0833 involving conference or group key network architectures or network communication protocols for key management in group communication in a packet data network H04L63/065
• CPC Class Codes: H04L 9/3268 using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]

Abstract

Upon detection of a new traffic flow, a registration node can dynamically register the new traffic flow with a key server policy manager by sending a registration request on behalf of the new traffic flow. A registration request indicates the new traffic flow should be protected by a security group. A registration request may also include a request to dynamically generate a new security group to protect the traffic flow. The registration request is received by a key server policy manager, which performs authentication and authorization checks of the requesting registration node, and determines whether to accept or reject the registration request. If accepted, the key server policy manager registers the new traffic flow by including a description of the traffic flow in a group policy of an existing security group or a newly created security group, depending on the registration request.

Claims

1. A method, comprising:

receiving a registration request to dynamically register a traffic flow, wherein

the registration request is sent from a registration node,

the registration request is received at a key server policy manager,

the key server policy manager and the registration node are communicatively coupled via a network, and

the registration request comprises a group identifier (ID);

determining whether to accept the registration request; and

performing the registration request, in response to a determination to accept the registration request, wherein the performing the registration request comprises

determining whether the group ID identifies a new security group that does not presently exist in the network, and

in response to determining that the group ID identifies the new security group that does not presently exist in the network, creating the new security group identified by the group ID.

2. The method of claim 1, wherein

the registration request comprises a traffic flow identifier,

the traffic flow identifier identifies the traffic flow, and

the registration request indicates that the new security group should protect the traffic flow.

3. The method of claim 1, wherein the determining whether to accept the registration request is based on administrative decisions implemented in an encryption scheme that is implemented in the network.

4. The method of claim 1, wherein the performing the registration request further comprises:

generating a new group policy for the new security group, wherein

the new group policy protects the traffic flow, and

the creating the new security group comprises

storing the new group policy in a new entry in a group policy data store.

5. The method of claim 4, further comprising:

registering the registration node as a default group member of the new security group, subsequent to the performing the registration request; and

publishing the new group policy to one or more group members of the new security group, subsequent to the performing the registration request.

6. The method of claim 1, further comprising:

authenticating the registration node using a registration node identifier; and

verifying authorization of the registration node to make the registration request.

7. A method, comprising:

detecting a new traffic flow at a registration node, wherein

the new traffic flow is identified by a new traffic flow identifier (ID), and

the new traffic flow ID does not match any traffic flow IDs present in existing group policies configured at the registration node; and

sending a registration request to a key server policy manager, wherein

the registration request comprises

a request to dynamically register the new traffic flow,

the new traffic flow identifier, and

a group ID that identifies a security group that should protect the new traffic flow.

8. The method of claim 7, further comprising:

receiving an acknowledgement from the key server policy manger, wherein

the acknowledgement indicates acceptance or rejection of the registration request.

9. The method of claim 7, further comprising:

receiving publication of a group policy, wherein the group policy comprises the new traffic flow identifier; and

refreshing the group policy, wherein the refreshing renews an expiration period associated with the group policy.

21. The method of claim 7, wherein

the registration node and the key server policy manager are communicatively coupled via a network, and

the group ID identifies one of

a new security group that does not presently exist in the network, and

an existing security group.

10. A system comprising:

one or more processors; and

one or more memories coupled to the one or more processors and configured to

store instructions executable by the one or more processors, the instructions configured to implement

a policy manager configured to

receive a registration request to dynamically register a traffic flow, wherein

the registration request is sent from a registration node,

the policy manager and the registration node are communicatively coupled via a network, and

the registration request comprises a group identifier (ID),

determine whether to accept the registration request, and

perform the registration request, in response to a determination to accept the registration request, wherein the policy manager is further configured to

determine whether the group ID identifies a new security group that does not presently exist in the network, and

in response to a determination that the group ID identifies the new security group that does not presently exist in the network, create the new security group identified by the group ID.

11. The system of claim 10, wherein

the registration request comprises a traffic flow identifier,

the traffic flow identifier identifies the traffic flow, and

the registration request indicates that the new security group should protect the traffic flow.

12. The system of claim 10, wherein

the policy manager is further configured to accept the registration request based on administrative decisions implemented in an encryption scheme that is implemented in the network.

13. The system of claim 10, wherein

the policy manager is further configured to

generate a new group policy for the new security group, wherein

the new group policy protects the traffic flow, and

store the new group policy in a new entry in a group policy data store.

14. The system of claim 13, wherein the instructions are further configured to implement

a key server configured to

register the registration node as a default group member of the new security group, subsequent to performance of the registration request, and

publish the new group policy to one or more group members of the new security group, subsequent to performance of the registration request.

15. The system of claim 10, wherein

the policy manager is further configured to

authenticate the registration node using a registration node identifier, and

verify authorization of the registration node to make the registration request.

16. The system of claim 10, wherein the instructions are further configured to implement

a registration node module configured to

detect a new traffic flow, wherein

the new traffic flow is identified by a new traffic flow identifier (ID), and

the new traffic flow ID does not match any traffic flow IDs present in existing group policies configured at the registration node;

and

send the registration request to the policy manager, wherein

the registration request comprises

the traffic flow identifier, and

the group ID.

17. The system of claim 16, wherein

the registration node module is further configured to

receive an acknowledgement from the policy manger, wherein

the acknowledgement indicates acceptance or rejection of the registration request.

18. The system of claim 16, wherein

the registration node module is further configured to

receive publication of a group policy, wherein the group policy comprises the new traffic flow identifier;

and

refresh the group policy, wherein the refreshing renews an expiration period associated with the group policy.

19. An apparatus comprising:

a line card configured to receive a registration request to dynamically register a traffic flow, wherein

the registration request is sent from a registration node,

the registration node and the line card are communicatively coupled via a network, and

the registration request comprises a group identifier (ID); and

a control module coupled to the line card, the control module configured to

determine whether to accept the registration request, and

perform the registration request, in response to a determination to accept the registration request, wherein the control module is further configured to

determine whether the group ID identifies a new security group that does not presently exist in the network, and

in response to a determination that the group ID identifies the new security group that does not presently exist in the network, create the new security group identified by the group ID.

20. An apparatus comprising:

a line card configured to receive packets; and

a control module coupled to the line card, the control module configured to

detect packets of a new traffic flow, wherein

the new traffic flow is identified by a new traffic flow identifier (ID), and

the new traffic flow ID does not match any traffic flow IDs present in existing group policies configured at a registration node, and

send a registration request to a key server policy manager, wherein

the registration request comprises

a request to dynamically register the new traffic flow,

the new traffic flow identifier, and

a group identifier (ID) that identifies a security group that should protect the new traffic flow.