Maintaining dependencies in a set of rules for security scanning in could-based web applications and API protection
Systems and methods include receiving a copy of a template file of security rules where the template file includes a plurality of rule tags and one or more dependency tags that define relationships and dependencies between any rules associated with the plurality of rule tags; scanning the template file including, for each respective rule tag of the plurality of rule tags checking if an enabled flag is set for the respective rule tag, when the enable flag is set, looking up a respective rule in a rule database and replacing the respective rule tag with the respective rule, and when the enable flag is not set, removing the respective rule tag from the template file; and providing an output file including a plurality of rules having the relationships and dependencies, where the output file is used for security scanning.
1. A non-transitory computer-readable medium comprising instructions that, when executed, cause one or more processors to perform steps of:
receiving a copy of a template file where the template file includes a plurality of rule tags and one or more dependency tags that define relationships and dependencies between any rules associated with the plurality of rule tags;
scanning the template file including, for each respective rule tag of the plurality of rule tags
checking if an enabled flag is set for the respective rule tag,
when the enable flag is set, looking up a respective rule in a rule database configured to enable an administrator to enable/disable rules based on the respective rule tag and replacing the respective rule tag with the respective rule text from the rule database, and
when the enable flag is not set, removing the respective rule tag from the template file;
providing an output file including a plurality of rules having the relationships and dependencies; and
utilizing the output file to provide a set of rules for performing security scanning via a cloud-based system.
2. The non-transitory computer-readable medium of claim 1 , wherein the steps further include
updating any of the rules in the rule database independently from updating the one or more dependency tags in the template file.
3. The non-transitory computer-readable medium of claim 2 , wherein the steps further include
repeating the scanning of the template file and providing an output file subsequent to the updating, wherein the output file provided subsequent to the updating includes a plurality of rules having the relationships and dependencies based on the updating.
4. The non-transitory computer-readable medium of claim 1 , wherein rules are stored in the rule database as strings.
5. The non-transitory computer-readable medium of claim 1 , wherein the rule database utilizes one of Postgres or MySQL to enable the storing and distribution of security rules.
6. The non-transitory computer-readable medium of claim 1 , wherein the output file defines functionality for any of cloud-based Web Application Firewalls (WAF), Deep Packet Inspection (DPI), Intrusion Prevention Systems (IPS), Cloud-based web application and API protection (WAAP), and Data Loss Prevention.
7. The non-transitory computer-readable medium of claim 1 , wherein the plurality of rules include detection of any of top ten OWASP web application security risks.
8. The non-transitory computer-readable medium 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.
9. The non-transitory computer-readable medium of claim 1 , wherein the steps further include
updating the plurality of rules based on monitoring of other users in a cloud-based system.
10. The non-transitory computer-readable medium of claim 1 , wherein the plurality of rules include a combination of user-defined rules and pre-defined rules.
11. A method comprising steps of:
receiving a copy of a template file where the template file includes a plurality of rule tags and one or more dependency tags that define relationships and dependencies between any rules associated with the plurality of rule tags;
scanning the template file including, for each respective rule tag of the plurality of rule tags
checking if an enabled flag is set for the respective rule tag,
when the enable flag is set, looking up a respective rule in a rule database configured to enable an administrator to enable/disable rules based on the respective rule tag and replacing the respective rule tag with the respective rule text from the rule database, and
when the enable flag is not set, removing the respective rule tag from the template file;
providing an output file including a plurality of rules having the relationships and dependencies; and
utilizing the output file to provide a set of rules for performing security scanning via a cloud-based system.
12. The method of claim 11 , wherein the steps further include
updating any of the rules in the rule database independently from updating the one or more dependency tags in the template file.
13. The method of claim 12 , wherein the steps further include
repeating the scanning of the template file and providing an output file subsequent to the updating, wherein the output file provided subsequent to the updating includes a plurality of rules based on the updating.
14. The method of claim 11 , wherein rules are stored in the rule database as strings.
15. The method of claim 11 , wherein the rule database utilizes one of Postgres or MySQL.
16. The method of claim 11 , wherein the output file defines functionality for any of cloud-based Web Application Firewalls (WAF), Deep Packet Inspection (DPI), Intrusion Prevention Systems (IPS), Cloud-based web application and API protection (WAAP), and Data Loss Prevention.
17. The method of claim 11 , wherein the plurality of rules include detection of any of top ten OWASP web application security risks.
18. The method of claim 11 , 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.
19. The method of claim 11 , wherein the steps further include
updating the plurality of rules based on monitoring of other users in a cloud-based system.
20. The method of claim 11 , wherein the plurality of rules include a combination of user-defined rules and pre-defined rules.