IP Library Granted Patent US 11,641,379
Granted Patent B1
US 11,641,379 · App. 17/397,778 · Granted May 2, 2023

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 11,641,379
App. No.
17/397,778
Granted
May 2, 2023
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 (59)

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, a second group of application activities, and a third group of application activities, wherein a first portion of the security-related application activities is classified into the first group of application activities, wherein being classified into the first group indicates that the first group of application activities are each to be mapped to one of a plurality of activity categories, wherein a second portion of the security-related application activities are classified into the second group of application activities, wherein being classified into the second group indicates that second group of application activities are each to be ignored, 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 indicates that the third group of application activities cannot be mapped to any of the plurality of activity categories, and wherein each of the first portion of the security-related application activities, the second portion of security-related application activities, and the third portion of the security-related application activities is different;

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 and that the plurality of activity categories may need to be updated to include the application activity; and

for each application activity of the first 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.

2. The method of claim 1 , further comprising for each application activity of the first portion of the security-related application activities:

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 1 , wherein the at least one hardware processor implements a network proxy server to monitor network traffic to and from the enterprise.

4. 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.

5. The method of claim 4 , 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.

6. The method of claim 1 , wherein the corresponding set of one or more security enforcement policies of at least one application activity of the first 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.

7. The method of claim 1 , wherein a first application activity of the first 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.

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, a second group of application activities, and a third group of application activities, wherein a first portion of the security-related application activities is classified into the first group of application activities, wherein being classified into the first group indicates that the first group of application activities are each to be mapped to one of a plurality of activity categories, wherein a second portion of the security-related application activities are classified into the second group of application activities, wherein being classified into the second group indicates that second group of application activities are each to be ignored, 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 indicates that the third group of application activities cannot be mapped to any of the plurality of activity categories, and wherein each of the first portion of the security-related application activities, the second portion of security-related application activities, and the third portion of the security-related application activities is different;

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 and that the plurality of activity categories may need to be updated to include the application activity; and

for each application activity of the first 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; and

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.

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, for each application activity of the first portion of the security-related application activities:

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 8 , wherein the at least one hardware processor implements a network proxy server to monitor network traffic to and from the enterprise.

11. 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.

12. The system recited in claim 11 , 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.

13. The system recited in claim 8 , wherein the corresponding set of one or more security enforcement policies of at least one application activity of the first 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.

14. The system recited in claim 8 , wherein a first application activity of the first 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.

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, a second group of application activities, and a third group of application activities, wherein a first portion of the security-related application activities is classified into the first group of application activities, wherein being classified into the first group indicates that the first group of application activities are each to be mapped to one of a plurality of activity categories, wherein a second portion of the security-related application activities are classified into the second group of application activities, wherein being classified into the second group indicates that second group of application activities are each to be ignored, 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 indicates that the third group of application activities cannot be mapped to any of the plurality of activity categories, and wherein each of the first portion of the security-related application activities, the second portion of security-related application activities, and the third portion of the security-related application activities is different;

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 and that the plurality of activity categories may need to be updated to include the application activity; and

for each application activity of the first 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.

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

for each application activity of the first portion of the security-related application activities:

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 15 , wherein the at least one processor implements a network proxy server to monitor network traffic to and from the enterprise.

18. 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.

19. The non-transitory computer-readable medium of claim 18 , 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.

20. The non-transitory computer-readable medium of claim 15 , wherein the corresponding set of one or more security enforcement policies of at least one application activity of the first 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.

21. The non-transitory computer-readable medium of claim 15 , wherein a first application activity of the first 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.

Assignments (8)
ASSIGNMENT OF INTERCOMPANY FIRST LIEN PATENT SECURITY AGREEMENT Recorded Apr 14, 2025
From: UBS AG, STAMFORD BRANCH
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 070840/0598 →
INTERCOMPANY FIRST LIEN PATENT SECURITY AGREEMENT Recorded Jan 24, 2025
From: SKYHIGH SECURITY LLC
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 070618/0001 →
RELEASE OF SECURITY INTEREST Recorded Aug 16, 2024
From: STG PARTNERS, LLC
To: MUSARUBRA US LLC; SKYHIGH SECURITY LLC
Reel/Frame 068671/0435 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Aug 15, 2024
From: MAGENTA SECURITY HOLDINGS LLC; SKYHIGH SECURITY LLC
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 068657/0666 →
SECURITY INTEREST Recorded Aug 1, 2024
From: MUSARUBRA US LLC; SKYHIGH SECURITY LLC
To: STG PARTNERS, LLC
Reel/Frame 068324/0731 →
CHANGE OF NAME Recorded Jun 1, 2022
From: SKYHIGH NETWORKS, LLC
To: SKYHIGH SECURITY LLC
Reel/Frame 060247/0079 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 27, 2022
From: SARUKKAI, SEKHAR; SOMASAMUDRAM, PRASAD RAGHAVENDRA; TARANIGANTY, RAMA; JAISWAL, VIKRAM; SETO, CHAPMAN; HINGARAJIYA, RAVI; VISWANATHAN, SURENDRAKUMAR; NARAYAN, KAUSHIK; MANGALAPURI, PRADEEP KUMAR REDDY; SHENOY, GURUPRASAD
To: SKYHIGH NETWORKS, INC.
Reel/Frame 060043/0046 →
CHANGE OF NAME Recorded May 27, 2022
From: SKYHIGH NETWORKS, INC.
To: SKYHIGH NETWORKS, LLC
Reel/Frame 060217/0662 →
Continuity (2)
Continuation 15341463 · Nov 2, 2016
Provisional Application 62393466 · Sep 12, 2016
Cited By (1)
US 12,271,385