IP Library Granted Patent US 12,568,123
Granted Patent B1
US 12,568,123 · App. 18/130,082 · Granted Mar 3, 2026

Cloud security policy enforcement for custom web applications

Inventors: Sekhar Sarukkai (Cupertino, CA); Prasad Raghavendra Somasamudram (Bangalore, IN); Rama Taraniganty (Cupertino, CA); Vikram Jaiswal (Fremont, CA); Chapman Seto (San Jose, CA); Ravi Hingarajiya (Sunnyvale, CA); Surendrakumar Viswanathan (Santa Clara, CA); Kaushik Narayan (San Jose, CA); Pradeep Kumar Reddy Mangalapuri (Bangalore, IN); Guruprasad Shenoy (Bangalore, IN)
Assignee: Skyhigh Security LLC
H04L63/205H04L43/0876H04L63/0281H04L63/1408
View Patent ↗
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 12,568,123
App. No.
18/130,082
Granted
Mar 3, 2026
Kind
B1
Abstract

A cloud security method implement web security at the application level by monitoring network traffic and detecting cloud activities related to web applications, and then classifying the detected cloud activities to map certain security-related cloud activities into activity categories to enable security policy to be applied. The application-level cloud security method enables policy enforcement rules to be established for cloud activity categories. The security policies are then applied based on activity categories.

Claims (67)

1 . A method of implementing cloud security policy enforcement for web applications being used by an enterprise, the method comprising:

classifying, using at least one hardware processor, security-related application activities relating to a web application into at least a first group of application activities, wherein a first portion of the security-related application activities are classified into the first group of application activities, wherein the first portion of the security-related application activities being classified into the first group of application activities indicates that the corresponding first portion of the security-related application activities cannot be mapped to any of a plurality of activity categories and that the corresponding first portion of the security-related application activities does not involve only viewing static resources of the web application; and

generating an alert in response to an application activity being classified into the first group, wherein the alert indicates that the application activity should be reviewed by a human and that the plurality of activity categories may need to be updated to include the application activity,

wherein the plurality of activity categories include at least two of administration, data access, data download, data updates, external data sharing, login success, report execution, service usage, user account creation, and user account deletion.

2 . The method of claim 1 , further comprising:

classifying, using at least one hardware processor, the security-related application activities relating to the web application into at least a second group of application activities, wherein a second portion of the security-related application activities is classified into the second group of application activities, wherein being classified into the second group of application activities indicates that corresponding application activities are each to be mapped to one of the plurality of activity categories; and

for each application activity of the second portion of the security-related application activities relating to the web application:

mapping the application activity to one of the plurality of activity categories based on a signature of the application activity;

associating a corresponding set of one or more security enforcement policies of the mapped activity category to the application activity; and

applying the corresponding set of one or more security enforcement policies to network traffic corresponding to the application activity based on the application activity being mapped to the mapped activity category;

generating metadata containing information indicative of the application activity, the web application, and the mapped activity category for the application activity; and

generating the corresponding set one or more of security enforcement policies for the application activity using the metadata.

3 . The method of claim 2 , wherein the corresponding set of one or more security enforcement policies of at least one application activity of the second portion of the security-related application activities relating to the web application includes security policies for threat detection, data encryption, data loss prevention, and access control.

4 . The method of claim 2 , wherein a first application activity of the second portion of the security-related application activities is mapped to a first activity category, the method further comprising:

tagging at least one data field in the first application activity; and

associating a first security enforcement policy of the first activity category to the first application activity, the first security enforcement policy comprising encrypting data in the tagged data fields associated with the first application activity.

5 . The method of claim 1 , further comprising:

classifying, using at least one hardware processor, the security-related application activities relating to the web application into at least a third group of application activities, wherein a third portion of the security-related application activities are classified into the third group of application activities, wherein being classified into the third group of application activities indicates that corresponding application activities are each to be ignored.

6 . The method of claim 1 , wherein the at least one hardware processor implements a containerized cloud security reverse proxy embedded in a containerized web application to monitor network traffic to and from the enterprise, the containerized web application being configured in an application container.

7 . The method of claim 6 , further comprising:

embedding the containerized cloud security reverse proxy into the application container containing the containerized web application by accessing an application programming interface (API) of the application container to generate a reverse proxy configuration.

8 . A system for implementing cloud security policy enforcement for web applications being used by an enterprise, the system comprising:

at least one hardware processor; and

a memory coupled with the at least one hardware processor, wherein the memory is configured to provide the at least one hardware processor with instructions which when executed cause the at least one hardware processor to:

classify security-related application activities relating to a web application into at least a first group of application activities, wherein a first portion of the security-related application activities are classified into the first group of application activities, wherein the first portion of the security-related application activities being classified into the first group of application activities indicates that the corresponding first portion of the security-related application activities cannot be mapped to any of a plurality of activity categories and that the corresponding first portion of the security-related application activities does not involve only viewing static resources of the web application; and

generate an alert in response to an application activity being classified into the third group, wherein the alert indicates that the application activity should be reviewed by a human and that the plurality of activity categories may need to be updated to include the application activity,

wherein the plurality of activity categories include at least two of administration, data access, data download, data updates, external data sharing, login success, report execution, service usage, user account creation, and user account deletion.

9 . The system recited in claim 8 , wherein the memory is further configured to provide the at least one hardware processor with instructions which when executed cause the at least one hardware processor to:

classify the security-related application activities relating to the web application into at least a second group of application activities, wherein a second portion of the security-related application activities is classified into the second group of application activities, wherein being classified into the second group of application activities indicates that corresponding application activities are each to be mapped to one of the plurality of activity categories; and

for each application activity of the second portion of the security-related application activities relating to the web application:

map the application activity to one of the plurality of activity categories based on a signature of the application activity;

associate a corresponding set of one or more security enforcement policies of the mapped activity category to the application activity;

apply the corresponding set of one or more security enforcement policies to network traffic corresponding to the application activity based on the application activity being mapped to the mapped activity category;

generate metadata containing information indicative of the application activity, the web application, and the mapped activity category for the application activity; and

generate the corresponding set of one or more security enforcement policies for the application activity using the metadata.

10 . The system recited in claim 9 , wherein the corresponding set of one or more security enforcement policies of at least one application activity of the second portion of the security-related application activities relating to the web application includes security policies for threat detection, data encryption, data loss prevention, and access control.

11 . The system recited in claim 9 , wherein a first application activity of the second portion of the security-related application activities is mapped to a first activity category, and wherein the memory is further configured to provide the at least one hardware processor with instructions which when executed cause the at least one hardware processor to:

tag at least one data field in the first application activity; and

associate a first security enforcement policy of the first activity category to the first application activity, the first security enforcement policy comprising encrypting data in the tagged data fields associated with the first application activity.

12 . The system recited in claim 8 , wherein the memory is further configured to provide the at least one hardware processor with instructions which when executed cause the at least one hardware processor to:

classify the security-related application activities relating to the web application into at least a third group of application activities, wherein a third portion of the security-related application activities are classified into the third group of application activities, wherein being classified into the third group of application activities indicates that corresponding application activities are each to be ignored.

13 . The system recited in claim 8 , wherein the memory is further configured to provide the at least one hardware processor with instructions which when executed cause the at least one hardware processor to:

provide a containerized cloud security reverse proxy embedded in a containerized web application to monitor network traffic to and from the enterprise, the containerized web application being configured in an application container.

14 . The system recited in claim 13 , wherein the memory is further configured to provide the at least one hardware processor with instructions which when executed cause the at least one hardware processor to:

embed the containerized cloud security reverse proxy into the application container containing the containerized web application by accessing an application programming interface (API) of the application container to generate a reverse proxy configuration.

15 . A non-transitory computer-readable medium containing computer executable instructions that, when executed by at least one processor, cause the at least one processor to perform a method for implementing cloud security policy enforcement for web applications being used by an enterprise, the method comprising:

classifying security-related application activities relating to a web application into at least a first group of application activities, wherein a first portion of the security-related application activities are classified into the first group of application activities, wherein the first portion of the security-related application activities being classified into the first group of application activities indicates that the corresponding first portion of the security-related application activities cannot be mapped to any of a plurality of activity categories and that the corresponding first portion of the security-related application activities does not involve only viewing static resources of the web application; and

generating an alert in response to an application activity being classified into the third group, wherein the alert indicates that the application activity should be reviewed by a human and that the plurality of activity categories may need to be updated to include the application activity,

wherein the plurality of activity categories include at least two of administration, data access, data download, data updates, external data sharing, login success, report execution, service usage, user account creation, and user account deletion.

16 . The non-transitory computer-readable medium of claim 15 , wherein the method further comprises:

classifying the security-related application activities relating to the web application into at least a second group of application activities, wherein a second portion of the security-related application activities is classified into the second group of application activities, wherein being classified into the second group of application activities indicates that corresponding application activities are each to be mapped to one of the plurality of activity categories; and

for each application activity of the second portion of the security-related application activities relating to the web application:

mapping the application activity to one of the plurality of activity categories based on a signature of the application activity;

associating a corresponding set of one or more security enforcement policies of the mapped activity category to the application activity; and

applying the corresponding set of one or more security enforcement policies to network traffic corresponding to the application activity based on the application activity being mapped to the mapped activity category;

generating metadata containing information indicative of the application activity, the web application, and the mapped activity category for the application activity; and

generating the corresponding set of one or more security enforcement policies for the application activity using the metadata.

17 . The non-transitory computer-readable medium of claim 16 , wherein the corresponding set of one or more security enforcement policies of at least one application activity of the second portion of the security-related application activities relating to the web application includes security policies for threat detection, data encryption, data loss prevention, and access control.

18 . The non-transitory computer-readable medium of claim 16 , wherein a first application activity of the second portion of the security-related application activities is mapped to a first activity category, and wherein the method further comprises:

tagging at least one data field in the first application activity; and

associating a first security enforcement policy of the first activity category to the first application activity, the first security enforcement policy comprising encrypting data in the tagged data fields associated with the first application activity.

19 . The non-transitory computer-readable medium of claim 15 , wherein the method further comprises:

classifying the security-related application activities relating to the web application into at least a third group of application activities, wherein a third portion of the security-related application activities are classified into the third group of application activities, wherein being classified into the third group of application activities indicates that corresponding application activities are each to be ignored.

20 . The non-transitory computer-readable medium of claim 15 , wherein the method further comprises:

providing a containerized cloud security reverse proxy embedded in a containerized web application to monitor network traffic to and from the enterprise, the containerized web application being configured in an application container.

21 . The non-transitory computer-readable medium of claim 20 , wherein the method further comprises:

embedding the containerized cloud security reverse proxy into the application container containing the containerized web application by accessing an application programming interface (API) of the application container to generate a reverse proxy configuration.

Continuity (3)
Continuation 17397778 · Aug 9, 2021
Continuation 15341463 · Nov 2, 2016
Provisional Application 62393466 · Sep 12, 2016
References Cited (88)
US 7610375B2 · Portolani et al. · 2009 [cited by applicant]
US 7810151B1 · Guruswamy · 2010 [cited by examiner]
US 7937761B1 · Bennett · 2011 [cited by examiner]
US 8060577B1 · Conrad · 2011 [cited by examiner]
US 8195793B2 · Prescott · 2012 [cited by applicant]
US 8320381B2 · Lange · 2012 [cited by applicant]
US 8392963B2 · Shulman · 2013 [cited by examiner]
US 9369433B1 · Paul et al. · 2016 [cited by applicant]
US 9407664B1 · Banerjee · 2016 [cited by applicant]
US 9483742B1 · Ahmed · 2016 [cited by examiner]
US 9832209B1 · Cooley et al. · 2017 [cited by applicant]
US 9917852B1 · Xu et al. · 2018 [cited by applicant]
US 9977921B2 · Sprague et al. · 2018 [cited by applicant]
US 10237149B1 · Guo et al. · 2019 [cited by applicant]
US 10445514B1 · Brandwine · 2019 [cited by examiner]
US 10699276B1 · Smith · 2020 [cited by examiner]
US 20030149888A1 · Yadav · 2003 [cited by applicant]
US 20050097150A1 · McKeon · 2005 [cited by examiner]
US 20060191008A1 · Fernando · 2006 [cited by examiner]
US 20070261112A1 · Todd · 2007 [cited by examiner]
US 20080034424A1 · Overcash et al. · 2008 [cited by applicant]
US 20080104699A1 · Gounares et al. · 2008 [cited by applicant]
US 20090158430A1 · Borders · 2009 [cited by examiner]
US 20100058366A1 · Swildens · 2010 [cited by applicant]
US 20100095348A1 · Foster et al. · 2010 [cited by applicant]
US 20100281539A1 · Burns · 2010 [cited by examiner]
US 20100299292A1 · Collazo · 2010 [cited by examiner]
US 20100299302A1 · Gopshtein et al. · 2010 [cited by applicant]
US 20100299437A1 · Moore · 2010 [cited by applicant]
US 20110022642A1 · deMilo et al. · 2011 [cited by applicant]
US 20110219035A1 · Korsunsky · 2011 [cited by examiner]
US 20110219426A1 · Riley et al. · 2011 [cited by applicant]
US 20110277034A1 · Hanson · 2011 [cited by applicant]
US 20110289308A1 · Sobko · 2011 [cited by examiner]
US 20120167162A1 · Raleigh et al. · 2012 [cited by applicant]
US 20120210427A1 · Bronner et al. · 2012 [cited by applicant]
US 20120240183A1 · Sinha · 2012 [cited by applicant]
US 20130311475A1 · Emanuel · 2013 [cited by examiner]
US 20140150100A1 · Gupta · 2014 [cited by examiner]
US 20140317734A1 · Valencia · 2014 [cited by examiner]
US 20140342691A1 · Kalavade · 2014 [cited by applicant]
US 20150150123A1 · Be'ery · 2015 [cited by examiner]
US 20150161386A1 · Gupta · 2015 [cited by examiner]
US 20150172321A1 · Kirti et al. · 2015 [cited by applicant]
US 20150195166A1 · Kalavade · 2015 [cited by applicant]
US 20150213376A1 · Ideses · 2015 [cited by examiner]
US 20150264063A1 · Jenson · 2015 [cited by examiner]
US 20150319185A1 · Kirti · 2015 [cited by examiner]
US 20160078362A1 · Christodorescu · 2016 [cited by examiner]
US 20160099852A1 · Cook · 2016 [cited by examiner]
US 20160127407A1 · Mankovskii et al. · 2016 [cited by applicant]
US 20160149936A1 · Pegna · 2016 [cited by examiner]
US 20160173529A1 · Baig et al. · 2016 [cited by applicant]
US 20160275303A1 · Narayanaswamy et al. · 2016 [cited by applicant]
US 20160330246A1 · Narayanaswamy et al. · 2016 [cited by applicant]
US 20160337390A1 · Sridhara · 2016 [cited by examiner]
US 20170104851A1 · Arangasamy et al. · 2017 [cited by applicant]
US 20170149807A1 · Schilling · 2017 [cited by examiner]
US 20170163670A1 · Manadhata · 2017 [cited by examiner]
US 20170195291A1 · Yadav et al. · 2017 [cited by applicant]
US 20170251013A1 · Kirti et al. · 2017 [cited by applicant]
US 20170318035A1 · Baughman · 2017 [cited by examiner]
US 20170364814A1 · Rinehart · 2017 [cited by examiner]
US 20170374083A1 · Cohen · 2017 [cited by examiner]
US 20180020024A1 · Chao · 2018 [cited by examiner]
US 20180025011A1 · Aksionkin · 2018 [cited by examiner]
US 20180027006A1 · Zimmermann et al. · 2018 [cited by applicant]
US 20180041376A1 · Li et al. · 2018 [cited by applicant]
US 20180152534A1 · Kristiansson et al. · 2018 [cited by applicant]
US 20180173555A1 · Lutas · 2018 [cited by applicant]
US 20190261222A1 · Raleigh · 2019 [cited by examiner]
W. Li and A. W. Moore, “A Machine Learning Approach for Efficient Traffic Classification,” 2007 15th International Symposium on Modeling, Analysis, and Simulation of Computer and Telecommunication Systems, Istanbul, Tur… [cited by examiner]
T. Verhanneman, F. Piessens, B. De Win and W. Joosen, “Uniform application-level access control enforcement of organizationwide policies,” 21st Annual Computer Security Applications Conference (ACSAC'05), Tucson, AZ, US… [cited by examiner]
Bossi, Lorenzo, Elisa Bertino, and Syed Rafiul Hussain. “A system for profiling and monitoring database access patterns by application programs for anomaly detection.” IEEE Transactions on software engineering 43.5 (201… [cited by examiner]
Viswanathan, Ram Prasad, Youssif Al-Nashif, and Salim Hariri. “Application attack detection system (AADS): An anomaly based behavior analysis approach.” 2011 9th IEEE/ACS International Conference on Computer Systems and… [cited by examiner]
Razzaq, Abdul, et al. “Semantic security against web application attacks.” Information Sciences 254 (2014): 19-38. (Year: 2014). [cited by examiner]
Srivatsa, Mudhakar, et al. “Mitigating application-level denial of service attacks on Web servers: A client-transparent approach.” ACM Transactions on the Web (TWEB) 2.3 (2008): 1-49. (Year: 2008). [cited by examiner]
Aljurayban, N.S. et al., “Framework for Cloud Intrusion Detection System Service”, In 2nd World Symposium on Web Applications and Networking (WSWAN), Sousse, Aug. 2015, pp. 1-5. [cited by applicant]
Docker, “Modern Application Architecture for the Enterprise: Delivering agility, portability and control with Docker Containers as a Service (CaaS)”, in Docker , Jan. 21, 2016, pp. 1-6, available at www.docker.com. [cited by applicant]
Notice of Allowance dated Apr. 21, 2021 in U.S. Appl. No. 15/341,463, pp. 1-23. [cited by applicant]
Notice of Allowance dated Dec. 29, 2022 in U.S. Appl. No. 17/397,778, pp. 1-72. [cited by applicant]
Office Action dated Feb. 1, 2021 in U.S. Appl. No. 15/341,463, pp. 1-24. [cited by applicant]
Office Action dated Feb. 28, 2019 in U.S. Appl. No. 15/341,463, pp. 1-31. [cited by applicant]
Office Action dated Mar. 10, 2020 in U.S. Appl. No. 15/341,463, pp. 1-17. [cited by applicant]
Office Action dated Jul. 25, 2018 in U.S. Appl. No. 15/341,463, pp. 1-46. [cited by applicant]
Office Action dated Sep. 13, 2019 in U.S. Appl. No. 15/341,463, pp. 1-14. [cited by applicant]
Office Action dated Sep. 30, 2020 in U.S. Appl. No. 15/341,463, pp. 1-30. [cited by applicant]
Paquette, S., et al., “Identifying the Security Risks Associated wiht Governmental use of Cloud Computing”, In Government Information Quarterly, v. 27.3, Apr. 13, 2010, pp. 245-253. [cited by applicant]