IP Library Granted Patent US 12,261,921
Granted Patent B2
US 12,261,921 · App. 18/656,718 · Granted Mar 25, 2025

Cloud system providing data protection of data in a SaaS or cloud provider

Inventors: Abhishek Bathla (Panipat, IN); Kumar Gaurav (Cupertino, CA); Raman Madaan (Bengaluru, IN); Chakkaravarthy Periyasamy Balaiah (Sunnyvale, CA); Shweta Gupta (Chandigarh, IN)
Assignee: Zscaler, Inc.
H04L67/562G06F21/552G06F21/568H04L63/145H04L67/1095H04L67/563
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,261,921
App. No.
18/656,718
Granted
Mar 25, 2025
Kind
B2
Abstract

A method performed by a cloud system includes, subsequent to the cloud system connecting to one of a cloud provider and a Software-as-a-Service (SaaS) application, scanning data stored therein for one or more users associated with a tenant of a plurality of tenants of the cloud system; detecting an incident in the data during the scanning; maintaining details of the incident in an in-memory data store; and providing a notification to the tenant of the incident.

Claims (34)

1. A method performed by a cloud system, the method comprising steps of:

subsequent to the cloud system connecting to one of a cloud provider and a Software-as-a-Service (SaaS) application, scanning data stored therein for one or more users associated with a tenant of a plurality of tenants of the cloud system;

detecting an incident in the data during the scanning;

maintaining details of the incident in an in-memory data store; and

providing a notification to the tenant of the incident.

2. The method of claim 1 , wherein the steps further include:

subsequent to the incident and while the data is being modified, updating the details of the incident in the in-memory data store.

3. The method of claim 1 , wherein the tenant of the cloud-based system is also a tenant of the one of the cloud provider and the SaaS application.

4. The method of claim 1 , wherein the cloud-based system is separate from the one of the cloud provider and the SaaS application.

5. The method of claim 4 , wherein the cloud-based system connects to the one of the cloud provider and the SaaS application via an Application Programming Interface (API).

6. The method of claim 1 , wherein the incident relates to data loss for the tenant based on one or more of a standard dictionary for all of the plurality of tenants and a custom dictionary for the tenant.

7. The method of claim 1 , wherein the incident relates to the threat which is one of a plurality of threats which are maintained and updated in real-time in the cloud-based system.

8. The method of claim 7 , wherein the plurality of threats include any of malware, spyware, viruses, command-and-control, phishing, cross-site scripting, and bots.

9. The method of claim 1 , wherein the steps further include:

receiving updates for the scanning associated with the tenant in the cloud system.

10. The method of claim 1 , wherein the steps further include:

providing both real-time notifications and aggregated reports to the tenant of any detected incidents.

11. A cloud system comprising one or more processors configured to implement steps of:

subsequent to the cloud system connecting to one of a cloud provider and a Software-as-a-Service (SaaS) application, scanning data stored therein for one or more users associated with a tenant of a plurality of tenants of the cloud system;

detecting an incident in the data during the scanning;

maintaining details of the incident in an in-memory data store; and

providing a notification to the tenant of the incident.

12. The cloud system of claim 11 , wherein the steps further include:

subsequent to the incident and while the data is being modified, updating the details of the incident in the in-memory data store.

13. The cloud system of claim 11 , wherein the tenant of the cloud-based system is also a tenant of the one of the cloud provider and the SaaS application.

14. The cloud system of claim 11 , wherein the cloud-based system is separate from the one of the cloud provider and the SaaS application.

15. The cloud system of claim 14 , wherein the cloud-based system connects to the one of the cloud provider and the SaaS application via an Application Programming Interface (API).

16. The cloud system of claim 11 , wherein the incident relates to data loss for the tenant based on one or more of a standard dictionary for all of the plurality of tenants and a custom dictionary for the tenant.

17. The cloud system of claim 11 , wherein the incident relates to the threat which is one of a plurality of threats which are maintained and updated in real-time in the cloud-based system.

18. The cloud system of claim 17 , wherein the plurality of threats include any of malware, spyware, viruses, command-and-control, phishing, cross-site scripting, and bots.

19. The cloud system of claim 11 , wherein the steps further include:

receiving updates for the scanning associated with the tenant in the cloud system.

20. The cloud system of claim 11 , wherein the steps further include:

providing both real-time notifications and aggregated reports to the tenant of any detected incidents.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 7, 2024
From: BATHLA, ABHISHEK; GAURAV, KUMAR; MADAAN, RAMAN; BALAIAH, CHAKKARAVARTHY PERIYASAMY; GUPTA, SHWETA
To: ZSCALER, INC.
Reel/Frame 067331/0220 →
Priority Claims (1)
IN 202011035829 · Aug 20, 2020 · national
Continuity (3)
Continuation 18122354 · Mar 16, 2023
Continuation 17061704 · Oct 2, 2020
Related Publication 20240291904A1 · Aug 29, 2024
References Cited (36)
US 8185510B2 · Chaudhry et al. · 2012 [cited by applicant]
US 8429111B1 · Kailash et al. · 2013 [cited by applicant]
US 8869259B1 · Udupa et al. · 2014 [cited by applicant]
US 8887249B1 · Schekochikhin et al. · 2014 [cited by applicant]
US 9152789B2 · Natarajan et al. · 2015 [cited by applicant]
US 9154475B1 · Kailash et al. · 2015 [cited by applicant]
US 9473537B2 · Sinha et al. · 2016 [cited by applicant]
US 9609015B2 · Natarajan et al. · 2017 [cited by applicant]
US 10523710B2 · Sinha et al. · 2019 [cited by applicant]
US 10621346B1 · Singh et al. · 2020 [cited by applicant]
US 10706167B1 · Sokolov · 2020 [cited by examiner]
US 10812531B2 · Narayanaswamy et al. · 2020 [cited by applicant]
US 10873644B1 · Rappaport et al. · 2020 [cited by applicant]
US 10979452B2 · Kundu et al. · 2021 [cited by applicant]
US 20140282545A1 · Richards · 2014 [cited by examiner]
US 20170295197A1 · Parimi et al. · 2017 [cited by applicant]
US 20180011983A1 · Zuhars · 2018 [cited by examiner]
US 20180027006A1 · Zimmermann et al. · 2018 [cited by applicant]
US 20180097832A1 · Viktorov · 2018 [cited by applicant]
US 20180375886A1 · Kirti et al. · 2018 [cited by applicant]
US 20190007394A1 · Patel et al. · 2019 [cited by applicant]
US 20190007438A1 · Viktorov · 2019 [cited by applicant]
US 20190020667A1 · Parker et al. · 2019 [cited by applicant]
US 20190068627A1 · Thampy · 2019 [cited by applicant]
US 20190095320A1 · Biswas et al. · 2019 [cited by applicant]
US 20190098037A1 · Shenoy, Jr. et al. · 2019 [cited by applicant]
US 20190297161A1 · Ayyadevara et al. · 2019 [cited by applicant]
US 20190318100A1 · Bhatia et al. · 2019 [cited by applicant]
US 20200128047A1 · Biswas et al. · 2020 [cited by applicant]
US 20200336484A1 · Mahajan et al. · 2020 [cited by applicant]
US 20200336503A1 · Xu et al. · 2020 [cited by applicant]
US 20210044603A1 · Annen et al. · 2021 [cited by applicant]
US 20210044604A1 · Annen et al. · 2021 [cited by applicant]
US 20210083967A1 · Joshi · 2021 [cited by examiner]
US 20210150056A1 · Vax et al. · 2021 [cited by applicant]
US 20210250333A1 · Negrea et al. · 2021 [cited by applicant]