IP Library Patent Application 11541424
Patent Application
App. No. 11/541,424

Protocol/API between a key server (KAP) and an enforcement point (PEP)

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 None
App. No.
11/541,424
Abstract

An Application Programming Interface (API) for communicating security policy information between a Key Authority Point (KAP) and a Policy Enforcement Point (PEP), thereby eliminating the need to manually install security policies on each network device.

Claims (31)

1 . A method for communicating policy information between at least one key authority point and at least one policy enforcement point, the method comprising:

generating detailed policy information from high level policy definitions at the at least one key authority point;

communicating the detailed policy information from the at least one key authority point to the at least one policy enforcement point over a network, wherein the detailed policy information conforms to an application programming interface; and

receiving and storing of the detailed policy information at the at least one policy enforcement point.

2 . The method of claim 1 , wherein communicating policy information includes communicating a policy name, server information, transaction information, and transaction details.

3 . The method of claim 2 , wherein communicating server information includes indicating one of the at least one key authority points.

4 . The method of claim 2 , wherein communicating transaction information includes specifying a deferred reload time.

5 . The method of claim 2 , wherein communicating transaction information includes specifying a transaction type.

6 . The method of claim 5 , wherein specifying the transaction type includes specifying a transaction type that corresponds with the transaction details.

7 . The method of claim 5 , wherein specifying the transaction type includes specifying a replace transaction.

8 . The method of claim 2 , wherein communicating transaction details includes communicating details for a replace transaction.

9 . The method of claim 8 , wherein communicating transaction details includes specifying a set of policy rules.

10 . The method of claim 9 , wherein specifying the set of policy rules includes specifying at least one policy rule.

11 . The method of claim 10 , wherein specifying the at least one policy rule includes specifying a policy action.

12 . The method of claim 1 , wherein communicating the detailed policy information includes communicating at least one key.

13 . The method of claim 1 , wherein communicating the detailed policy information includes communicating using transport layer security.

14 . The method of claim 1 , wherein communicating the detailed policy information includes communicating using remote procedure calls encoded with an extensible markup language.

15 . A system for communicating security policy information between a key authority point and a policy enforcement point, the system comprising:

at least one key authority point residing on a network;

at least one policy enforcement point residing on the network; and

an application programming interface between the at least one key authority point and the at least one policy enforcement point for invoking remote procedure calls over the network.

16 . The system of claim 15 , wherein the application programming interface comprises: a policy name component; a server information component; a transaction information component; and a transaction details component.

17 . The system of claim 16 , wherein the server information component indicates one of the at least one key authority points.

18 . The system of claim 16 , wherein the transaction information component includes a deferred reload time.

19 . The system of claim 16 , wherein the transaction information component includes a transaction type.

20 . The system of claim 19 , wherein the transaction type indicates a type of content stored in the transaction details component.

21 . The system of claim 19 , wherein the transaction type indicates a replace transaction.

22 . The system of claim 16 , wherein the transaction details component includes details for a replace transaction.

23 . The system of claim 22 , wherein the transaction details component includes a set of policy rules.

24 . The system of claim 23 , wherein the set of policy rules includes at least one policy rule.

25 . The system of claim 24 , wherein the at least one policy rule includes a action component.

Assignments (9)
RELEASE OF SECURITY INTEREST Recorded Feb 9, 2011
From: ADAMS CAPITAL MANAGEMENT III, L.P.
To: CIPHEROPTICS INC.
Reel/Frame 025775/0040 →
RELEASE OF SECURITY INTEREST Recorded Jan 12, 2011
From: VENTURE LENDING & LEASING IV, INC.
To: CIPHEROPTICS, INC.
Reel/Frame 025625/0961 →
RELEASE OF SECURITY INTEREST Recorded May 13, 2010
From: ADAMS CAPITAL MANAGEMENT III, LP
To: CIPHEROPTICS, INC.
Reel/Frame 024379/0889 →
RELEASE OF SECURITY INTEREST Recorded Feb 3, 2010
From: ADAMS CAPITAL MANAGEMENT III, L.P.
To: CIPHEROPTICS INC.
Reel/Frame 023890/0220 →
SECURITY AGREEMENT Recorded Dec 29, 2009
From: CIPHEROPTICS INC.
To: ADAMS CAPITAL MANAGEMENT III, L.P.
Reel/Frame 023713/0623 →
SECURITY AGREEMENT Recorded Apr 7, 2009
From: CIPHEROPTICS INC.
To: RENEWABLE ENERGY FINANCING, LLC
Reel/Frame 022516/0338 →
SECURITY AGREEMENT Recorded Apr 24, 2007
From: CIPHEROPTICS, INC.
To: ADAMS CAPITAL MANAGEMENT III, L.P.
Reel/Frame 019198/0810 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 29, 2007
From: MCALISTER, DONALD; ORANGE, JOHN CARY
To: CIPHEROPTICS, INC.
Reel/Frame 019083/0643 →
SECURITY AGREEMENT Recorded Dec 21, 2006
From: CIPHEROPTICS INC.
To: VENTURE LENDING & LEASING IV, INC.
Reel/Frame 018728/0421 →