IP Library › Granted Patent US 12,483,601
Granted Patent B2
US 12,483,601 · App. 17/248,529 · Granted Nov 25, 2025

Automation of cloud network security policy analysis and deployment

Inventors: Toan Van Nguyen (Singapore, SG); Qiyuan Zheng (Sammamish, WA); Santhosh Ram Vetrinadar Manohar (San Jose, CA); Varun Kulkarni Somashekhar (Fremont, CA); Prabhat Singh (Sunnyvale, CA)
Assignee: Salesforce, Inc.
H04L63/205
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,483,601
App. No.
17/248,529
Granted
Nov 25, 2025
Kind
B2
Abstract

Disclosed are examples of systems, apparatus, methods and computer program products for automation of network security policy analysis and deployment. A server system can obtain a system input comprising two versions of a policy output. The system can generate a severity characteristic that indicates a severity of deploying the second version of the policy output. The system can then determine whether to deploy the second version of the policy output based on the severity characteristic. The system can then, in response to determining that the second version of the policy output is to be deployed, deploy the second version of the policy output to one of a plurality of clouds.

Claims (71)

1 . A system comprising:

one or more memory devices; and

a server system comprising one or more processors in communication with the one or more memory devices, the server system configurable to cause:

obtaining a system input comprising:

a first version of a policy output, and

a second version of the policy output,

each version of the policy output comprising a version of a cloud-specific policy set specific to one of a plurality of clouds of different cloud providers;

generating a severity characteristic associated with deployment of the second version of the policy output to one of the plurality of clouds based on one or more differences between the first version of the policy output and the second version of the policy output, wherein the severity characteristic indicates an impact of at least one type of change associated with the one or more differences between the first version of the policy output and the second version of the policy output;

determining that the second version of the policy output is to be deployed without manual review of the second version of the policy output based on a determination that the severity characteristic indicative of the impact of the at least one type of change associated with the one or more differences between the first version and the second version is below a predetermined threshold; and

in response to determining that the second version of the policy output is to be deployed, deploying the second version of the policy output to the one of the plurality of clouds.

2 . The system of claim 1 , the server system further configurable to cause:

generating a report that includes the severity characteristic, wherein the report is generated based on the one or more differences between the first version of the policy output and the second version of the policy output; and

causing the report to be transmitted to a user device.

3 . The system of claim 2 , wherein causing the report to be transmitted to the user device comprises causing the report to be presented in a website that presents a dashboard related to a set of security policies.

4 . The system of claim 1 , the server system further configurable to cause:

designating each of the one or more differences between the first version of the policy output and the second version of the policy output as one of a plurality of types of changes; and

determining, for each of the one or more differences, the severity characteristic based on the type of change associated with the difference.

5 . The system of claim 4 , wherein the severity characteristic is retrieved from a table that associates a severity characteristic with each of the plurality of types of changes.

6 . The system of claim 1 , wherein the server system is further configurable to cause:

obtaining additional system input comprising a third version of the policy output;

generating a second severity characteristic that indicates a severity of deploying the third version of the policy output to the one of the plurality of clouds based on one or more differences between the second version of the policy output and the third version of the policy output;

determining whether to deploy the third version of the policy output based on the second severity characteristic; and

in response to determining that the third version of the policy output is not to be deployed, causing a report that indicates the one or more differences to be transmitted to a user device.

7 . The system of claim 6 , wherein the server system is further configurable to cause:

receiving, from the user device, an instruction to deploy the third version of the policy output; and

deploying the third version of the policy output to the one of the plurality of clouds in response to receiving the instruction from the user device.

8 . A non-transitory computer-readable medium comprising instructions, which, when executed by one or more processors cause performance of:

obtaining a system input comprising:

a first version of a policy output, and

a second version of the policy output,

each version of the policy output comprising a version of a cloud-specific policy set specific to one of a plurality of clouds of different cloud providers;

generating a severity characteristic associated with deployment of the second version of the policy output to one of the plurality of clouds based on one or more differences between the first version of the policy output and the second version of the policy output, wherein the severity characteristic indicates an impact of at least one type of change associated with the one or more differences between the first version of the policy output and the second version of the policy output;

determining that the second version of the policy output is to be deployed without manual review of the second version of the policy output based on a determination that the severity characteristic indicative of the impact of the at least one type of change associated with the one or more differences between the first version and the second version is below a predetermined threshold, wherein the at least one type of change comprises at least one of: an addition of a service, a removal of a service, allowing new traffic to access a provider, blocking one or more ports of traffic, blocking one or more particular communication protocols, or any combination thereof; and

in response to determining that the second version of the policy output is to be deployed, deploying the second version of the policy output to the one of the plurality of clouds.

9 . The non-transitory computer-readable medium of claim 8 , the instructions further configurable to cause:

generating a report that includes the severity characteristic, wherein the report is generated based on the one or more differences between the first version of the policy output and the second version of the policy output; and

causing the report to be transmitted to a user device.

10 . The non-transitory computer-readable medium of claim 9 , wherein causing the report to be transmitted to the user device comprises causing the report to be presented in a website that presents a dashboard related to a set of security policies.

11 . The non-transitory computer-readable medium of claim 8 , the instructions further configurable to cause:

designating each of the one or more differences between the first version of the policy output and the second version of the policy output as one of a plurality of types of changes; and

determining, for each of the one or more differences, the severity characteristic based on the type of change associated with the difference.

12 . The non-transitory computer-readable medium of claim 11 , wherein the severity characteristic is retrieved from a table that associates a severity characteristic with each of the plurality of types of changes.

13 . The non-transitory computer-readable medium of claim 8 , the instructions further configurable to cause:

obtaining additional system input comprising a third version of the policy output;

generating a second severity characteristic that indicates a severity of deploying the third version of the policy output to the one of the plurality of clouds based on one or more differences between the second version of the policy output and the third version of the policy output;

determining whether to deploy the third version of the policy output based on the second severity characteristic; and

in response to determining that the third version of the policy output is not to be deployed, causing a report that indicates the one or more differences to be transmitted to a user device.

14 . The non-transitory computer-readable medium of claim 13 , the instructions further configurable to cause:

receiving, from the user device, an instruction to deploy the third version of the policy output; and

deploying the third version of the policy output to the one of the plurality of clouds in response to receiving the instruction from the user device.

15 . A method comprising:

obtaining a system input comprising:

a first version of a policy output, and

a second version of the policy output,

each version of the policy output comprising a version of a cloud-specific policy set specific to one of a plurality of clouds of different cloud providers;

generating a severity characteristic associated with deployment of the second version of the policy output to one of the plurality of clouds based on one or more differences between the first version of the policy output and the second version of the policy output, wherein the severity characteristic indicates an impact of at least one type of change associated with the one or more differences between the first version of the policy output and the second version of the policy output;

determining that the second version of the policy output is to be deployed without manual review of the second version of the policy output based on a determination that the severity characteristic indicative of the impact of the at least one type of change associated with the one or more differences between the first version and the second version is below a predetermined threshold; and

in response to determining that the second version of the policy output is to be deployed, deploying the second version of the policy output to the one of the plurality of clouds.

16 . The method of claim 15 , further comprising:

generating a report that includes the severity characteristic, wherein the report is generated based on the one or more differences between the first version of the policy output and the second version of the policy output; and

causing the report to be transmitted to a user device.

17 . The method of claim 16 , wherein causing the report to be transmitted to the user device comprises causing the report to be presented in a website that presents a dashboard related to a set of security policies.

18 . The method of claim 15 , further comprising:

designating each of the one or more differences between the first version of the policy output and the second version of the policy output as one of a plurality of types of changes; and

determining, for each of the one or more differences, the severity characteristic based on the type of change associated with the difference.

19 . The method of claim 18 , wherein the severity characteristic is retrieved from a table that associates a severity characteristic with each of the plurality of types of changes.

20 . The method of claim 15 , further comprising:

obtaining additional system input comprising a third version of the policy output;

generating a second severity characteristic that indicates a severity of deploying the third version of the policy output to the one of the plurality of clouds based on one or more differences between the second version of the policy output and the third version of the policy output;

determining whether to deploy the third version of the policy output based on the second severity characteristic; and

in response to determining that the third version of the policy output is not to be deployed, causing a report that indicates the one or more differences to be transmitted to a user device.

Assignments (2)
CHANGE OF NAME Recorded Aug 4, 2026
From: SALESFORCE.COM, INC.
To: SALESFORCE, INC.
Reel/Frame 076118/0548 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 17, 2021
From: NGUYEN, TOAN VAN; ZHENG, QIYUAN; SOMASHEKHAR, VARUN KULKARNI; MANOHAR, SANTHOSH RAM VETRINADAR; SINGH, PRABHAT
To: SALESFORCE.COM, INC
Reel/Frame 055298/0512 →
Continuity (2)
Continuation In Part 16948399 · Sep 16, 2020
Related Publication 20220086193A1 · Mar 17, 2022
References Cited (241)
US 5577188A · Zhu · 1996 [cited by applicant]
US 5608872A · Schwartz et al. · 1997 [cited by applicant]
US 5649104A · Carleton et al. · 1997 [cited by applicant]
US 5715450A · Ambrose et al. · 1998 [cited by applicant]
US 5761419A · Schwartz et al. · 1998 [cited by applicant]
US 5819038A · Carleton et al. · 1998 [cited by applicant]
US 5821937A · Tonelli et al. · 1998 [cited by applicant]
US 5831610A · Tonelli et al. · 1998 [cited by applicant]
US 5873096A · Lim et al. · 1999 [cited by applicant]
US 5918159A · Fomukong et al. · 1999 [cited by applicant]
US 5963953A · Cram et al. · 1999 [cited by applicant]
US 5983227A · Nazem et al. · 1999 [cited by applicant]
US 6092083A · Brodersen et al. · 2000 [cited by applicant]
US 6161149A · Achacoso et al. · 2000 [cited by applicant]
US 6169534B1 · Raffel et al. · 2001 [cited by applicant]
US 6178425B1 · Brodersen et al. · 2001 [cited by applicant]
US 6189011B1 · Lim et al. · 2001 [cited by applicant]
US 6216133B1 · Masthoff · 2001 [cited by applicant]
US 6216135B1 · Brodersen et al. · 2001 [cited by applicant]
US 6233617B1 · Rothwein et al. · 2001 [cited by applicant]
US 6236978B1 · Tuzhilin · 2001 [cited by applicant]
US 6266669B1 · Brodersen et al. · 2001 [cited by applicant]
US 6288717B1 · Dunkle · 2001 [cited by applicant]
US 6295530B1 · Ritchie et al. · 2001 [cited by applicant]
US 6324568B1 · Diec et al. · 2001 [cited by applicant]
US 6324693B1 · Brodersen et al. · 2001 [cited by applicant]
US 6336137B1 · Lee et al. · 2002 [cited by applicant]
US D454139S · Feldcamp et al. · 2002 [cited by applicant]
US 6367077B1 · Brodersen et al. · 2002 [cited by applicant]
US 6393605B1 · Loomans · 2002 [cited by applicant]
US 6405220B1 · Brodersen et al. · 2002 [cited by applicant]
US 6411949B1 · Schaffer · 2002 [cited by applicant]
US 6434550B1 · Warner et al. · 2002 [cited by applicant]
US 6446089B1 · Brodersen et al. · 2002 [cited by applicant]
US 6535909B1 · Rust · 2003 [cited by applicant]
US 6549908B1 · Loomans · 2003 [cited by applicant]
US 6553563B2 · Ambrose et al. · 2003 [cited by applicant]
US 6560461B1 · Fomukong et al. · 2003 [cited by applicant]
US 6574635B2 · Stauber et al. · 2003 [cited by applicant]
US 6577726B1 · Huang et al. · 2003 [cited by applicant]
US 6601087B1 · Zhu et al. · 2003 [cited by applicant]
US 6604117B2 · Lim et al. · 2003 [cited by applicant]
US 6604128B2 · Diec et al. · 2003 [cited by applicant]
US 6609150B2 · Lee et al. · 2003 [cited by applicant]
US 6621834B1 · Scherpbier et al. · 2003 [cited by applicant]
US 6654032B1 · Zhu et al. · 2003 [cited by applicant]
US 6665648B2 · Brodersen et al. · 2003 [cited by applicant]
US 6665655B1 · Warner et al. · 2003 [cited by applicant]
US 6684438B2 · Brodersen et al. · 2004 [cited by applicant]
US 6711565B1 · Subramaniam et al. · 2004 [cited by applicant]
US 6724399B1 · Katchour et al. · 2004 [cited by applicant]
US 6728702B1 · Subramaniam et al. · 2004 [cited by applicant]
US 6728960B1 · Loomans et al. · 2004 [cited by applicant]
US 6732095B1 · Warshavsky et al. · 2004 [cited by applicant]
US 6732100B1 · Brodersen et al. · 2004 [cited by applicant]
US 6732111B2 · Brodersen et al. · 2004 [cited by applicant]
US 6754681B2 · Brodersen et al. · 2004 [cited by applicant]
US 6763351B1 · Subramaniam et al. · 2004 [cited by applicant]
US 6763501B1 · Zhu et al. · 2004 [cited by applicant]
US 6768904B2 · Kim · 2004 [cited by applicant]
US 6772229B1 · Achacoso et al. · 2004 [cited by applicant]
US 6782383B2 · Subramaniam et al. · 2004 [cited by applicant]
US 6804330B1 · Jones et al. · 2004 [cited by applicant]
US 6826565B2 · Ritchie et al. · 2004 [cited by applicant]
US 6826582B1 · Chatterjee et al. · 2004 [cited by applicant]
US 6826745B2 · Coker · 2004 [cited by applicant]
US 6829655B1 · Huang et al. · 2004 [cited by applicant]
US 6842748B1 · Warner et al. · 2005 [cited by applicant]
US 6850895B2 · Brodersen et al. · 2005 [cited by applicant]
US 6850949B2 · Warner et al. · 2005 [cited by applicant]
US 6907566B1 · McElfresh et al. · 2005 [cited by applicant]
US 7062502B1 · Kesler · 2006 [cited by applicant]
US 7069231B1 · Cinarkaya et al. · 2006 [cited by applicant]
US 7069497B1 · Desai · 2006 [cited by applicant]
US 7082102B1 · Wright · 2006 [cited by applicant]
US 7100111B2 · McElfresh et al. · 2006 [cited by applicant]
US 7181758B1 · Chan · 2007 [cited by applicant]
US 7269590B2 · Hull et al. · 2007 [cited by applicant]
US 7289976B2 · Kihneman et al. · 2007 [cited by applicant]
US 7340411B2 · Cook · 2008 [cited by applicant]
US 7356482B2 · Frankland et al. · 2008 [cited by applicant]
US 7373599B2 · McElfresh et al. · 2008 [cited by applicant]
US 7401094B1 · Kesler · 2008 [cited by applicant]
US 7406501B2 · Szeto et al. · 2008 [cited by applicant]
US 7412455B2 · Dillon · 2008 [cited by applicant]
US 7454509B2 · Boulter et al. · 2008 [cited by applicant]
US 7484237B2 · Joly et al. · 2009 [cited by applicant]
US 7508789B2 · Chan · 2009 [cited by applicant]
US 7599935B2 · La Rotonda et al. · 2009 [cited by applicant]
US 7603331B2 · Tuzhilin et al. · 2009 [cited by applicant]
US 7603483B2 · Psounis et al. · 2009 [cited by applicant]
US 7620655B2 · Larsson et al. · 2009 [cited by applicant]
US 7644122B2 · Weyer et al. · 2010 [cited by applicant]
US 7668861B2 · Steven · 2010 [cited by applicant]
US 7698160B2 · Beaven et al. · 2010 [cited by applicant]
US 7730478B2 · Weissman · 2010 [cited by applicant]
US 7747648B1 · Kraft et al. · 2010 [cited by applicant]
US 7779039B2 · Weissman et al. · 2010 [cited by applicant]
US 7779475B2 · Jakobson et al. · 2010 [cited by applicant]
US 7827208B2 · Bosworth et al. · 2010 [cited by applicant]
US 7853881B1 · Aly Assal et al. · 2010 [cited by applicant]
US 7945653B2 · Zukerberg et al. · 2011 [cited by applicant]
US 8005896B2 · Cheah · 2011 [cited by applicant]
US 8014943B2 · Jakobson · 2011 [cited by applicant]
US 8015495B2 · Achacoso et al. · 2011 [cited by applicant]
US 8032297B2 · Jakobson · 2011 [cited by applicant]
US 8073850B1 · Hubbard et al. · 2011 [cited by applicant]
US 8082301B2 · Ahlgren et al. · 2011 [cited by applicant]
US 8095413B1 · Beaven · 2012 [cited by applicant]
US 8095531B2 · Weissman et al. · 2012 [cited by applicant]
US 8095594B2 · Beaven et al. · 2012 [cited by applicant]
US 8103611B2 · Tuzhilin et al. · 2012 [cited by applicant]
US 8150913B2 · Cheah · 2012 [cited by applicant]
US 8209308B2 · Rueben et al. · 2012 [cited by applicant]
US 8209333B2 · Hubbard et al. · 2012 [cited by applicant]
US 8275836B2 · Beaven et al. · 2012 [cited by applicant]
US 8307404B2 · Vinberg et al. · 2012 [cited by applicant]
US 8457545B2 · Chan · 2013 [cited by applicant]
US 8484111B2 · Frankland et al. · 2013 [cited by applicant]
US 8490025B2 · Jakobson et al. · 2013 [cited by applicant]
US 8504945B2 · Jakobson et al. · 2013 [cited by applicant]
US 8510045B2 · Rueben et al. · 2013 [cited by applicant]
US 8510664B2 · Rueben et al. · 2013 [cited by applicant]
US 8566301B2 · Rueben et al. · 2013 [cited by applicant]
US 8646103B2 · Jakobson et al. · 2014 [cited by applicant]
US 10404757B1 · Horton · 2019 [cited by applicant]
US 12170692B2 · Nguyen et al. · 2024 [cited by applicant]
US 12170693B2 · Nguyen · 2024 [cited by applicant]
US 20010044791A1 · Richter et al. · 2001 [cited by applicant]
US 20020072951A1 · Lee et al. · 2002 [cited by applicant]
US 20020082892A1 · Raffel et al. · 2002 [cited by applicant]
US 20020129352A1 · Brodersen et al. · 2002 [cited by applicant]
US 20020140731A1 · Subramaniam et al. · 2002 [cited by applicant]
US 20020143997A1 · Huang et al. · 2002 [cited by applicant]
US 20020162090A1 · Parnell et al. · 2002 [cited by applicant]
US 20020165742A1 · Robbins · 2002 [cited by applicant]
US 20030004971A1 · Gong · 2003 [cited by applicant]
US 20030018705A1 · Chen et al. · 2003 [cited by applicant]
US 20030018830A1 · Chen et al. · 2003 [cited by applicant]
US 20030066031A1 · Laane et al. · 2003 [cited by applicant]
US 20030066032A1 · Ramachandran et al. · 2003 [cited by applicant]
US 20030069936A1 · Warner et al. · 2003 [cited by applicant]
US 20030070000A1 · Coker et al. · 2003 [cited by applicant]
US 20030070004A1 · Mukundan et al. · 2003 [cited by applicant]
US 20030070005A1 · Mukundan et al. · 2003 [cited by applicant]
US 20030074418A1 · Coker et al. · 2003 [cited by applicant]
US 20030120675A1 · Stauber et al. · 2003 [cited by applicant]
US 20030151633A1 · George et al. · 2003 [cited by applicant]
US 20030159136A1 · Huang et al. · 2003 [cited by applicant]
US 20030187921A1 · Diec et al. · 2003 [cited by applicant]
US 20030189600A1 · Gune et al. · 2003 [cited by applicant]
US 20030204427A1 · Gune et al. · 2003 [cited by applicant]
US 20030206192A1 · Chen et al. · 2003 [cited by applicant]
US 20030225730A1 · Warner et al. · 2003 [cited by applicant]
US 20040001092A1 · Rothwein et al. · 2004 [cited by applicant]
US 20040010489A1 · Rio et al. · 2004 [cited by applicant]
US 20040015981A1 · Coker et al. · 2004 [cited by applicant]
US 20040027388A1 · Berg et al. · 2004 [cited by applicant]
US 20040128001A1 · Levin et al. · 2004 [cited by applicant]
US 20040186860A1 · Lee et al. · 2004 [cited by applicant]
US 20040193510A1 · Catahan et al. · 2004 [cited by applicant]
US 20040199489A1 · Barnes-Leon et al. · 2004 [cited by applicant]
US 20040199536A1 · Barnes-Leon et al. · 2004 [cited by applicant]
US 20040199543A1 · Braud et al. · 2004 [cited by applicant]
US 20040249854A1 · Barnes-Leon et al. · 2004 [cited by applicant]
US 20040260534A1 · Pak et al. · 2004 [cited by applicant]
US 20040260659A1 · Chan et al. · 2004 [cited by applicant]
US 20040268299A1 · Lei et al. · 2004 [cited by applicant]
US 20050050555A1 · Exley et al. · 2005 [cited by applicant]
US 20050091098A1 · Brodersen et al. · 2005 [cited by applicant]
US 20050188072A1 · Lee et al. · 2005 [cited by applicant]
US 20050198098A1 · Levin et al. · 2005 [cited by applicant]
US 20050257244A1 · Joly et al. · 2005 [cited by applicant]
US 20070156919A1 · Potti et al. · 2007 [cited by applicant]
US 20070282951A1 · Selimis et al. · 2007 [cited by applicant]
US 20080060051A1 · Lim · 2008 [cited by examiner]
US 20080249972A1 · Dillon · 2008 [cited by applicant]
US 20080256593A1 · Vinberg et al. · 2008 [cited by applicant]
US 20090063415A1 · Chatfield et al. · 2009 [cited by applicant]
US 20090100342A1 · Jakobson · 2009 [cited by applicant]
US 20090177744A1 · Marlow et al. · 2009 [cited by applicant]
US 20110218958A1 · Warshavsky et al. · 2011 [cited by applicant]
US 20110247051A1 · Bulumulla et al. · 2011 [cited by applicant]
US 20120042218A1 · Cinarkaya et al. · 2012 [cited by applicant]
US 20120079266A1 · Ogata et al. · 2012 [cited by applicant]
US 20120233137A1 · Jakobson et al. · 2012 [cited by applicant]
US 20120290407A1 · Hubbard et al. · 2012 [cited by applicant]
US 20130212497A1 · Zelenko et al. · 2013 [cited by applicant]
US 20130218948A1 · Jakobson · 2013 [cited by applicant]
US 20130218949A1 · Jakobson · 2013 [cited by applicant]
US 20130218966A1 · Jakobson · 2013 [cited by applicant]
US 20130247216A1 · Cinarkaya et al. · 2013 [cited by applicant]
US 20140019617A1 · Hadar · 2014 [cited by examiner]
US 20140359537A1 · Jakobson et al. · 2014 [cited by applicant]
US 20150006289A1 · Jakobson et al. · 2015 [cited by applicant]
US 20150007050A1 · Jakobson et al. · 2015 [cited by applicant]
US 20150095162A1 · Jakobson et al. · 2015 [cited by applicant]
US 20150142596A1 · Jakobson et al. · 2015 [cited by applicant]
US 20150169879A1 · Hagiuda et al. · 2015 [cited by applicant]
US 20150172563A1 · Jakobson et al. · 2015 [cited by applicant]
US 20170251013A1 · Kirti et al. · 2017 [cited by applicant]
US 20170339003A1 · Åström et al. · 2017 [cited by applicant]
US 20170339023A1 · Aström et al. · 2017 [cited by applicant]
US 20190007443A1 · Cook et al. · 2019 [cited by applicant]
US 20190068598A1 · Kang et al. · 2019 [cited by applicant]
US 20190098037A1 · Shenoy, Jr. et al. · 2019 [cited by applicant]
US 20190158617A1 · Åström et al. · 2019 [cited by applicant]
US 20190289058A1 · Bhoj · 2019 [cited by examiner]
US 20190306194A1 · Benson et al. · 2019 [cited by applicant]
US 20190312909A1 · Kulkarni et al. · 2019 [cited by applicant]
US 20200004742A1 · Nagarajan · 2020 [cited by examiner]
US 20200059420A1 · Abraham · 2020 [cited by applicant]
US 20200128047A1 · Biswas et al. · 2020 [cited by applicant]
US 20200278813A1 · Nilsson · 2020 [cited by applicant]
US 20200382560A1 · Woolward et al. · 2020 [cited by applicant]
US 20210144550A1 · Ito et al. · 2021 [cited by applicant]
US 20210314363A1 · Hensley et al. · 2021 [cited by applicant]
US 20210336929A1 · Moore et al. · 2021 [cited by applicant]
US 20220006842A1 · Wadhwa et al. · 2022 [cited by applicant]
US 20220383154A1 · Eberlein · 2022 [cited by examiner]
US 20250047719A1 · Nguyen et al. · 2025 [cited by applicant]
CN 104506487B · 2017 [cited by applicant]
EP 3611619A1 · 2020 [cited by applicant]
JP 5346010B2 · 2013 [cited by applicant]
WO WO2017138944A1 · 2017 [cited by applicant]
“Rightscale 2019 State of the Cloud Report” Flexera, 2019. [cited by applicant]
“All Data Breaches in 2019 & 2020—An Alarming Timeline” [cited by applicant]
Shahin, Mojtaba, Muhammad Ali Babar, and Liming Zhu. “ [cited by applicant]
Spinnaker: Cloud Native Continuous Delivery: Fast, safe, repeatable deployments for every Enterprise, Webpage, Accessed: Jan. 20, 2021. [cited by applicant]
“Google Plus Users”, Google+Ripples, Oct. 31, 2011 [retrieved on Feb. 21, 2012 from Internet at http://www.googleplusers.com/google-ripples.html], 3 pages. [cited by applicant]
U.S. Appl. No. 16/948,399, filed Sep. 16, 2020, Toan Van Nguyen, et al. [cited by applicant]
U.S. Appl. No. 17/248,347, filed Jan. 21, 2021, Toan Van Nguyen. [cited by applicant]
International Preliminary Report on Patentability dated Mar. 30, 2023, in PCT Application No. PCT/US2021/049484. [cited by applicant]
International Search Report and Written Opinion dated Dec. 3, 2021, in Application No. PCT/US2021/049484, 13 pages. [cited by applicant]
U.S. Final office Action dated Jul. 6, 2023 in U.S. Appl. No. 16/948,399. [cited by applicant]
U.S. Non-Final office Action dated Jan. 23, 2023 in U.S. Appl. No. 16/948,399. [cited by applicant]
U.S. Non-Final Office Action dated Mar. 12, 2024 in U.S. Appl. No. 17/248,347. [cited by applicant]
U.S. Non-Final Office Action dated Nov. 28, 2023 in U.S. Appl. No. 16/948,399. [cited by applicant]
U.S. Notice of Allowance dated Aug. 1, 2024 in U.S. Appl. No. 16/948,399. [cited by applicant]
U.S. Notice of Allowance dated Aug. 21, 2024 in U.S. Appl. No. 17/248,347. [cited by applicant]
U.S. Corrected Notice of Allowance dated Nov. 20, 2024 in U.S. Appl. No. 16/948,399. [cited by applicant]