Cloud-based web application and API protection from untrusted users and devices
Systems and methods include, responsive to determining a user can access an application via a cloud-based system, wherein the application is in one of a public cloud, a private cloud, and an enterprise network, and wherein the user is remote over the Internet, obtaining a predetermined inspection profile for the user with the inspection profile including a plurality of rules evaluated in an order; performing inspection of the access using the plurality of rules in the order; and responsive to results of any of the plurality of rules, one or more of monitoring, allowing, blocking, and redirecting the access, via the cloud-based system.
1. A method comprising:
responsive to determining a user can access an application via a cloud-based system, wherein the application is in one of a public cloud, a private cloud, and an enterprise network, and wherein the user is remote over the Internet, obtaining a predetermined inspection profile for the user with the inspection profile including a plurality of rules evaluated in an order, wherein obtaining the predetermined inspection profile is based on the application and the user;
storing the plurality of rules in rows of database as strings;
responsive to the obtaining, obtaining a copy of a template file and filtering the template file based on a mapping table, wherein the template file comprises dependency information for the plurality of rules and a set of tags for each rule, and wherein the mapping table comprises rule definitions and rule inclusions and exclusions;
replacing the tags with rule data from the database;
performing inspection of transactions between a user device associated with the user and the application during the access, the inspection being performed based on the plurality of rules, each rule having dependencies maintained with other rules, in the predetermined inspection profile, wherein the rules are investigated in an order based on the dependencies; and
responsive to results of any of the plurality of rules, one or more of monitoring, allowing, blocking, and redirecting the access, via the cloud-based system.
2. The method of claim 1 , wherein performing the inspection comprises performing OWASP rule coverage and custom and standard Hypertext Transfer Protocol (HTTP) header inspection based on a plurality of operating modes.
3. The method of claim 1 , wherein the plurality of rules include anomaly detection, bot detection, Application Programming Interface (API) inspection rules, Denial of Service (DoS) detection rules, and customizable rules.
4. The method of claim 1 , further comprising
updating the plurality of rules based on monitoring of other users in the cloud-based system.
5. The method of claim 1 , further comprising
responsive to determining the user cannot access the application via the cloud-based system, notifying the user the application does not exist.
6. The method of claim 1 , further comprising
after the determining, stitching connections together between 1) a connector application executing on a user device associated with the user and the cloud-based system and 2) the cloud-based system and a lightweight connector associated with the application.
7. The method of claim 1 , further comprising
logging results of the rules and the access in the cloud-based system.
8. A system comprising:
a connector connected to the Internet and configured to only support outbound connections with a cloud-based system to provide a user access to an application;
a Web application and API protection (WAAP) module between the connector and the application, wherein the application is in one of a public cloud, a private cloud, and an enterprise network, and wherein the user is remote over the Internet; and
memory storing instructions, the instructions causing one or more processors to:
responsive to determination a user can access the application, obtain a predetermined inspection profile for the user with the inspection profile including a plurality of rules evaluated in an order, wherein the predetermined inspection profile is obtained based on the application and the user,
store the plurality of rules in rows of a database as strings,
responsive to the predetermined inspection profile being obtained, obtain a copy of a template file and filtering the template file based on a mapping table, wherein the template file comprises dependency information for the plurality of rules and a set of tags for each rule, and wherein the mapping table comprises rule definitions and rule inclusions and exclusions,
replace the tags with rule data from the database,
perform inspection of transactions between a user device associated with the user and the application during the access, the inspection being performed based on the plurality of rules, each rule having dependencies maintained with other rules, in the predetermined inspection profile, wherein the rules are investigated in an order based on the dependencies, and
responsive to results of any of the plurality of rules, one or more of monitor, allow, block, and redirect the access, via the cloud-based system.
9. The system of claim 8 , wherein performing the inspection comprises performing OWASP rule coverage and custom and standard Hypertext Transfer Protocol (HTTP) header inspection based on a plurality of operating modes.
10. The system of claim 8 , wherein the plurality of rules include anomaly detection, bot detection, Application Programming Interface (API) inspection rules, Denial of Service (DOS) detection rules, and customizable rules.
11. The system of claim 8 , wherein the instructions further cause the one or more processors to
update the plurality of rules based on monitoring of other users in the cloud-based system.
12. The system of claim 8 , wherein the connector is configured to
responsive to determining the user cannot access the application via the cloud-based system, notify the user the application does not exist.
13. The system of claim 8 , wherein the cloud-based system is configured to
after the determination, stitch connections together between 1) a connector application executing on a user device associated with the user and the cloud-based system and 2) the cloud-based system and a lightweight connector associated with the application.
14. The system of claim 8 , wherein the instructions further cause the one or more processors to
log results of the rules and the access in the cloud-based system.
15. A non-transitory computer-readable medium comprising instructions that, when executed, cause a node in a cloud-based system to perform the steps of:
responsive to determining a user can access an application via a cloud-based system, wherein the application is in one of a public cloud, a private cloud, and an enterprise network, and wherein the user is remote over the Internet, obtaining a predetermined inspection profile for the user with the inspection profile including a plurality of rules evaluated in an order, wherein obtaining the predetermined inspection profile is based on the application and the user;
storing the plurality of rules in rows of a database as strings;
responsive to the obtaining, obtaining a copy of a template file and filtering the template file based on a mapping table, wherein the template file comprises dependency information for the plurality of rules and a set of tags for each rule, and wherein the mapping table comprises rule definitions and rule inclusions and exclusions;
replacing the tags with rule data from the database,
performing inspection of transactions between a user device associated with the user and the application during the access, the inspection being performed based on the plurality of rules, each rule having dependencies maintained with other, rules, in the predetermined inspection profile, wherein the rules are investigated in an order based on the dependencies; and
responsive to results of any of the plurality of rules, one or more of monitoring, allowing, blocking, and redirecting the access, via the cloud-based system.
16. The non-transitory computer-readable medium of claim 15 , wherein performing the inspection comprises performing OWASP rule coverage and custom and standard Hypertext Transfer Protocol (HTTP) header inspection based on a plurality of operating modes.
17. The non-transitory computer-readable medium of claim 15 , wherein the plurality of rules include anomaly detection, bot detection, Application Programming Interface (API) inspection rules, Denial of Service (DOS) detection rules, and customizable rules.