Common serverless security API
System and method for executing a security operation for microservices/serverless function of a microservices-based/serverless application running on a physical infrastructure use a central security controller to execute the security operation for different microservices/serverless functions of the microservices-based/serverless application. Requests for the security operation are transmitted to the central security controller when communications are received at the different microservices/serverless functions of the microservices-based/serverless application. Results of the security operation are then received from the central security controller at the different microservices/serverless functions of the microservices-based/serverless application. Based on the results of the security operation, a task associated with the communications is executed at the different microservices/serverless functions.
1. A computer-implemented method for executing a security operation for microservices/serverless functions of a microservices-based/serverless application running on a physical infrastructure, the method comprising:
receiving communications at different microservices/serverless functions of the microservices-based/serverless application;
at each of the different microservices/serverless functions, determining whether a received communication requires a security operation to be performed, wherein the security operation is one of an authorization operation, a data validation operation and a data sanitization operation;
for the received communications at the different microservices/serverless functions that require the security operation to be performed, transmitting requests for the security operation from the different microservices/serverless functions of the microservices-based/serverless application to a central security controller for the received communications so that the security operation is executed at the central security controller for the different microservices/serverless functions;
receiving results of the security operation from the central security controller at the different microservices/serverless functions of the microservices-based/serverless application; and
executing a task associated with the communications at the different microservices/serverless functions of the microservices-based/serverless application based on the results of the security operation from the central security controller.
2. The method of claim 1 , wherein the different microservices/serverless functions are coded using different computer programming languages.
3. The method of claim 1 , wherein each of the different microservices/serverless functions is not programmed to execute the security operation.
4. The method of claim 1 , wherein the requests for the security operation are application programming interface (API) calls for the security operation.
5. The method of claim 1 , further comprising, for the received communications at particular microservices/serverless functions that do not require the security operation to be performed, executing a task associated with the communications at the particular microservices/serverless functions of the microservices-based/serverless application without transmitting any requests for the security operation from the particular microservices/serverless functions of the microservices-based/serverless application to the central security controller.
6. The method of claim 1 , further comprising executing the security operation at the central security controller in response to each of the requests to produce the results of the security operation.
7. The method of claim 1 , further comprising monitoring data in the central security controller to collect data traffic information regarding the different microservices/serverless functions of the microservices-based/serverless application.
8. A non-transitory computer-readable storage medium containing program instructions for a method for executing a security operation for microservices/serverless functions of a microservices-based/serverless application running on a physical infrastructure, wherein execution of the program instructions by one or more processors of a computer system causes the one or more processors to perform steps comprising:
receiving communications at different microservices/serverless functions of the microservices-based/serverless application;
at each of the different microservices/serverless functions, determining whether a received communication requires a security operation to be performed, wherein the security operation is one of an authorization operation, a data validation operation and a data sanitization operation;
for the received communications at the different microservices/serverless functions that require the security operation to be performed, transmitting requests for the security operation from the different microservices/serverless functions of the microservices-based/serverless application to a central security controller for the received communications so that the security operation is executed at the central security controller for the different microservices/serverless functions;
receiving results of the security operation from the central security controller at the different microservices of the microservices-based/serverless application; and
executing a task associated with the communications at the different microservices/serverless functions of the microservices-based/serverless application based on the results of the security operation from the central security controller.
9. The computer-readable storage medium of claim 8 , wherein the different microservices/serverless functions are coded using different computer programming languages.
10. The computer-readable storage medium of claim 8 , wherein each of the different microservices/serverless functions is not programmed to execute the security operation.
11. The computer-readable storage medium of claim 8 , wherein the requests for the security operation are application programming interface (API) calls for the security operation.
12. The computer-readable storage medium of claim 8 , wherein the steps further comprise, for the received communications at particular microservices/serverless functions that do not require the security operation to be performed, executing a task associated with the communications at the particular microservices/serverless functions of the microservices-based/serverless application without transmitting any requests for the security operation from the particular microservices/serverless functions of the microservices-based/serverless application to the central security controller.
13. The computer-readable storage medium of claim 8 , wherein the steps further comprise executing the security operation at the central security controller in response to each of the requests to produce the results of the security operation.
14. The computer-readable storage medium of claim 8 , wherein the steps further comprise monitoring data in the central security controller to collect data traffic information regarding the different microservices/serverless functions of the microservices-based/serverless application.
15. A system comprising:
memory; and
at least one processor configured to:
receive communications at different microservices/serverless functions of a microservices-based/serverless application;
at each of the different microservices/serverless functions, determine whether a received communication requires a security operation to be performed, wherein the security operation is one of an authorization operation, a data validation operation and a data sanitization operation;
for the received communications at the different microservices/serverless functions that require the security operation to be performed, transmit requests for a security operation from the different microservices/serverless functions of the microservices-based/serverless application to a central security controller for the received communications so that the security operation is executed at the central security controller for the different microservices/serverless functions;
receive results of the security operation from the central security controller at the different microservices/serverless functions of the microservices-based/serverless application; and
execute a task associated with the communications at the different microservices/serverless functions of the microservices-based/serverless application based on the results of the security operation from the central security controller.
16. The system of claim 15 , wherein the different microservices/serverless functions are coded using different computer programming languages.
17. The system of claim 15 , wherein each of the different microservices/serverless functions is not programmed to execute the security operation.
18. The system of claim 15 , wherein the requests for the security operation are application programming interface (API) calls for the security operation.
19. The system of claim 15 , wherein the at least one processor is configured to, for the received communications at particular microservices/serverless functions that do not require the security operation to be performed, execute a task associated with the communications at the particular microservices/serverless functions of the microservices-based/serverless application without transmitting any requests for the security operation from the particular microservices/serverless functions of the microservices-based/serverless application to the central security controller.
20. The system of claim 15 , wherein the at least one processor is configured to execute the security operation at the central security controller in response to each of the requests to produce the results of the security operation.