DYNAMIC FILTERING FOR SDN API CALLS ACROSS A SECURITY BOUNDARY

• US 20150200955A1
• Filed: 01/13/2014
• Published: 07/16/2015
• Est. Priority Date: 01/13/2014
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Martin, Antonio
• Granted Patent: US 9,258,315 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/562 Static detection
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/0245 Filtering by information in the payload
• CPC Class Codes: H04L 63/0263 Rule management
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/14 for detecting or protecting against malicious traffic
• CPC Class Codes: H04L 63/1408 by monitoring network traffic monitoring network traffic per se H04L43/00
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002
• CPC Class Codes: H04L 63/168 above the transport layer

Abstract

Presented herein are techniques to reduce the vulnerabilities of network elements to malicious API calls. One or more filters that validate data across an API boundary at a network element are dynamically loaded into the network element such that a reboot of the network element is not required to use the one or more filters. An API call is received for an API function, wherein the API call contains one or more parameter values associated with the API function. The parameters may be validated using the one or more filters. If it is determined that the one or more filters validate the parameters for the API function, the API function may be executed using the parameter values. If it is determined that the one or more filters do not validate the parameters for the API function, the execution of the API function may be aborted.

Claims

1. A method comprising:

dynamically loading one or more filters that validate data across an application programming interface (API) boundary in a network element such that a reboot of the network element is not required to use the one or more filters;

receiving an API call for an API function, wherein the API call contains one or more parameter values associated with the API function;

validating the parameters using the one or more filters;

if it is determined that the one or more filters validate the parameters for the API function, executing the API function using the parameter values; and

if it is determined that the one or more filters do not validate the parameters for the API function, aborting execution of the API function.

2. The method of claim 1, further comprising presenting to a user performance cost data associated with loading the one or more filters;

receiving confirmation from the user as to whether to load the one or more filters; and

loading the one or more filters only depending on whether confirmation from the user is received.

3. The method of claim 1, further comprising:

in response to receiving the API call, applying one or more filters to identify malformed data in the API call; and

in response to determining that there is no malformed data in the API call, parsing the API call to determine the parameter values.

4. The method of claim 3, further comprising:

parsing the API call to determine authorization values; and

applying one or more filters to identify malicious authorization values.

5. The method of claim 1, wherein the loading of the one or more filters is initiated by a software defined networking controller to download the one or more filters to the network element.

6. The method of claim 1, wherein the one or more filters comprise at least one of:

a regular expression black list filter and regular expression white list filter.

7. The method of claim 1, further comprising:

monitoring a plurality of API calls; and

in response to identifying a sequence in the plurality of API calls defined in the one or more filters that poses a security risk, dropping one or more API calls from the plurality of API calls.

8. The method of claim 1, wherein validating the API call further comprises:

if it is determined that there are one or more filters associated with the API function, determining whether there are one or more filters associated with the one or more parameters; and

if it is determined that there are one or more filters associated with the one or more parameters, validating the API parameters using the associated one or more filters.

9. The method of claim 1, further comprising:

receiving a firmware update for the network element to fix a security vulnerability associated with one or more filters that have already been loaded into the network element; and

in response to receiving the firmware update, removing the filters associated with the security vulnerability.

10. An apparatus comprising:

a plurality of network ports;

a network processor unit coupled to the plurality of network ports;

a processor coupled to the network processor unit, and configured to;

dynamically load one or more filters that validate data across an application programming interface (API) boundary such that a reboot of a network element is not required to use the one or more filters;

receive an API call for an API function, wherein the API call contains one or more parameter values associated with the API function;

validate the parameters using one or more filters that validate data traversing an API boundary of a network element;

if it is determined that the one or more filters validate the parameters for the API function or there are no associated filters, execute the API function using the parameter values; and

if it is determined that the one or more filters do not validate the parameters for the API function, abort execution of the API function.

11. The apparatus of claim 10, wherein the processor is further configured to:

present to a user performance cost data associated with loading the one or more filters;

receive confirmation from the user as to whether to load the one or more filters; and

load the one or more filters only depending on whether confirmation from the user is received.

12. The apparatus of claim 10, wherein the processor is further configured to:

in response to receiving the API call, apply one or more filters to identify malformed data in the API call; and

in response to determining that there is no malformed data in the API call, parse the API call to determine the parameter values.

13. The apparatus of claim 10, wherein the processor is further configured to:

monitor a plurality of API calls; and

in response to identifying a sequence in the plurality of API calls defined in the one or more filters that poses a security risk, drop one or more API calls from the plurality of API calls.

14. The apparatus of claim 10, wherein the processor is further configured to:

if it is determined that there are one or more filters associated with the API function, determine whether there are one or more filters associated with the one or more parameters; and

if it is determined that there are one or more filters associated with the one or more parameters, validate the parameters using the one or more associated filters.

15. The apparatus of claim 10, wherein the processor is configured to:

receive a firmware update for the network element to fix a security vulnerability associated with a filter that has already been loaded into the network element; and

in response to receiving the firmware update, remove the filters associated with the fixed security vulnerabilities.

16. A computer-readable storage media encoded with software comprising computer executable instructions and when the software is executed operable to:

dynamically load one or more filters that validate data across an application programming interface (API) boundary such that a reboot of a network element is not required to use the one or more filters;

receive an API call for an API function, wherein the API call contains one or more parameter values associated with the API function;

validate the parameters using one or more filters that validate data traversing an API boundary of a network element;

if it is determined that the one or more filters validate the parameters for the API function or there are no associated filters, execute the API function using the parameter values; and

if it is determined that the one or more filters do not validate the parameters for the API function, abort execution of the API function.

17. The computer-readable storage media of claim 16, further comprising instructions operable to:

present to a user performance cost data associated with loading the one or more filters;

receive confirmation from the user as to whether to load the one or more filters; and

load the one or more filters only depending on whether confirmation from the user is received.

18. The computer-readable storage media of claim 16, further comprising instructions operable to:

in response to receiving the API call, apply one or more filters to identify malformed data in the API call; and

in response to determining that there is no malformed data in the API call, parse the API call to determine the parameter values.

19. The computer-readable storage media of claim 16, further comprising instructions operable to:

if it is determined that there are one or more filters associated with the API function, determine whether there are one or more filters associated with the one or more parameters; and

if it is determined that there are one or more filters associated with the one or more parameters, validate the API call parameters using the one or more filters.

20. The computer-readable storage media of claim 16, further comprising instructions operable to:

monitor a plurality of API calls; and

in response to identifying a sequence in the plurality of API calls defined in the one or more filters that poses a security risk, drop one or more API calls from the plurality of API calls.