IP Library › Granted Patent US 12,309,182
Granted Patent B1
US 12,309,182 · App. 17/939,415 · Granted May 20, 2025

Customer onboarding and integration with anomaly detection systems

Inventors: David McAleer (Belfast, GB); David M. Hazekamp (Tinley Park, IL); Declan Wilson (Craigavon, GB); Ellie Goggin (Belfast, GB); Yijou Chen (Cupertino, CA)
Assignee: Fortinet, Inc.
H04L63/1425G06F9/455G06F9/545G06F16/9024G06F16/9038G06F16/9535G06F16/9537G06F21/57H04L41/06H04L63/10H04L67/306H04L67/535G06F16/2456
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,309,182
App. No.
17/939,415
Granted
May 20, 2025
Kind
B1
Abstract

Systems and methods for customer environment integration with anomaly detection systems are disclosed. The methods include receiving cloud computing environment data for the cloud computing environment; generating, based on the received cloud computing environment data, a set of commands for generating cloud computing infrastructure for anomaly detection, the set of commands including one or more commands for generating a first set of anomaly detection infrastructure elements within the cloud computing environment and for generating a second set of anomaly detection infrastructure elements at the anomaly detection system; and initiating an execution of the set of commands.

Claims (135)

1. A computer program product disposed upon a non-transitory computer readable medium, the computer program product comprising computer program instructions that, when executed, cause a computer to carry out the steps of:

receiving cloud computing environment data for the cloud computing environment;

generating, based on the received cloud computing environment data, a set of commands for generating cloud computing infrastructure for anomaly detection, the set of commands including:

one or more commands for generating a first set of anomaly detection infrastructure elements within the cloud computing environment; and

one or more commands for generating a second set of anomaly detection infrastructure elements at an anomaly detection system;

initiating an execution of the set of commands; and

wherein generating the set of commands further comprises:

detecting, from a log file of a cloud services provider of the cloud computing environment, creation of a new user account within the cloud computing environment;

presenting a notification that includes details of the new user account and a first request to apply anomaly detection functions for the new user account; and

based on a response to the first request, generating a customer account profile at the anomaly detection system corresponding to the new user account.

2. The computer program product of claim 1 , wherein generating the set of commands further comprises:

generating one or more native command line interface (CLI) commands of a native CLI of the anomaly detection system.

3. The computer program product of claim 1 , wherein generating the set of commands further comprises:

generating shell interface commands of a cloud services provider shell interface, wherein the cloud services provider shell interface is associated with a cloud services provider of the cloud computing environment of a customer.

4. A method of automated integration of a cloud computing environment of a customer with an anomaly detection system, the method comprising:

executing a set of commands for generating cloud computing infrastructure for anomaly detection, wherein executing the set of commands comprises:

generating a first set of anomaly detection infrastructure elements within the cloud computing environment;

generating a second set of anomaly detection infrastructure elements at the anomaly detection system;

detecting, from a log file of a cloud services provider of the cloud computing environment, creation of a new user account within the cloud computing environment;

presenting a notification that includes details of the new user account and a first request to apply anomaly detection functions for the new user account; and

based on a response to the first request, generating a customer account profile at the anomaly detection system corresponding to the new user account.

5. The method of claim 4 , wherein execution of the set of commands further comprises automatically installing one or more agents on customer resources at the cloud computing environment.

6. The method of claim 4 , wherein execution of the set of commands further comprises creating user profiles and application profiles within the anomaly detection system.

7. The method of claim 4 , wherein execution of the set of commands further comprises automatically enabling a set of anomaly detection features for the customer in the anomaly detection system, wherein the set of anomaly detection features is a default set of features.

8. The method of claim 4 , wherein execution of the set of commands further comprises causing existing anomaly detection modules of the anomaly detection system to execute anomaly detection for computing resources of the cloud computing environment of the customer.

9. The method of claim 4 , further comprising:

based on received cloud computing environment data, detecting that the cloud computing environment is serviced by a first cloud services provider and a second cloud services provider;

determining that a new user account was created within a first user directory of the first cloud services provider;

based on the determination, presenting a second request to create a second instance of the new user account within a second user directory of the second cloud services provider at the cloud computing environment; and

based on a response to the second request, creating the second instance of the new user account and updating a customer account profile to include information for the second instance of the new user account.

10. The method of claim 4 , wherein execution of the set of commands further comprises:

generating a state file, wherein the state file indicates a current state of the cloud computing environment; and

storing the state file at the anomaly detection system.

11. The method of claim 10 , wherein execution of the set of commands further comprises:

detecting that an additional anomaly detection feature is available for installation at the cloud computing environment; and

based on the detection, analyzing the state file to determine whether the additional anomaly detection feature is installed for the cloud computing environment.

12. The method of claim 4 , wherein execution of the set of commands further comprises:

receiving first cloud computing environment data from a first source and second cloud computing environment data from a second source within the cloud computing environment;

determining that the first cloud computing environment data alone or the second cloud computing environment data alone do not indicate an anomaly within the anomaly detection system;

based on the determination, analyzing the first cloud computing environment data and the second cloud computing environment data together to detect anomalies; and

based on the analyzing, determining that the first cloud computing environment data and the second cloud computing environment data taken together indicate an anomaly within the cloud computing environment.

13. A method of automated integration of a cloud computing environment of a customer with an anomaly detection system, the method comprising:

executing a set of commands for generating cloud computing infrastructure for anomaly detection, wherein executing the set of commands comprises:

generating a first set of anomaly detection infrastructure elements within the cloud computing environment; and

generating a second set of anomaly detection infrastructure elements at the anomaly detection system;

based on received cloud computing environment data, detecting that the cloud computing environment is serviced by a first cloud services provider and a second cloud services provider;

determining that a new user account was created within a first user directory of the first cloud services provider;

based on the determination, presenting a second request to create a second instance of the new user account within a second user directory of the second cloud services provider at the cloud computing environment; and

based on a response to the second request, creating the second instance of the new user account and updating a customer account profile to include information for the second instance of the new user account.

14. The method of claim 13 , wherein execution of the set of commands further comprises automatically installing one or more agents on customer resources at the cloud computing environment.

15. The method of claim 13 , wherein execution of the set of commands further comprises creating user profiles and application profiles within the anomaly detection system.

16. The method of claim 13 , wherein execution of the set of commands further comprises automatically enabling a set of anomaly detection features for the customer in the anomaly detection system, wherein the set of anomaly detection features is a default set of features.

17. The method of claim 13 , wherein execution of the set of commands further comprises causing existing anomaly detection modules of the anomaly detection system to execute anomaly detection for computing resources of the cloud computing environment of the customer.

18. The method of claim 13 , wherein execution of the set of commands further comprises:

generating a state file, wherein the state file indicates a current state of the cloud computing environment; and

storing the state file at the anomaly detection system.

19. The method of claim 18 , wherein execution of the set of commands further comprises:

detecting that an additional anomaly detection feature is available for installation at the cloud computing environment; and

based on the detection, analyzing the state file to determine whether the additional anomaly detection feature is installed for the cloud computing environment.

20. The method of claim 13 , wherein execution of the set of commands further comprises:

receiving first cloud computing environment data from a first source and second cloud computing environment data from a second source within the cloud computing environment;

determining that the first cloud computing environment data alone or the second cloud computing environment data alone do not indicate an anomaly within the anomaly detection system;

based on the determination, analyzing the first cloud computing environment data and the second cloud computing environment data together to detect anomalies; and

based on the analyzing, determining that the first cloud computing environment data and the second cloud computing environment data taken together indicate an anomaly within the cloud computing environment.

21. A method of automated integration of a cloud computing environment of a customer with an anomaly detection system, the method comprising:

executing a set of commands for generating cloud computing infrastructure for anomaly detection, wherein executing the set of commands comprises:

generating a first set of anomaly detection infrastructure elements within the cloud computing environment;

generating a second set of anomaly detection infrastructure elements at the anomaly detection system;

generating a state file, wherein the state file indicates a current state of the cloud computing environment;

storing the state file at the anomaly detection system;

detecting that an additional anomaly detection feature is available for installation at the cloud computing environment; and

based on the detection, analyzing the state file to determine whether the additional anomaly detection feature is installed for the cloud computing environment.

22. The method of claim 21 , wherein execution of the set of commands further comprises automatically installing one or more agents on customer resources at the cloud computing environment.

23. The method of claim 21 , wherein execution of the set of commands further comprises creating user profiles and application profiles within the anomaly detection system.

24. The method of claim 21 , wherein execution of the set of commands further comprises automatically enabling a set of anomaly detection features for the customer in the anomaly detection system, wherein the set of anomaly detection features is a default set of features.

25. The method of claim 21 , wherein execution of the set of commands further comprises causing existing anomaly detection modules of the anomaly detection system to execute anomaly detection for computing resources of the cloud computing environment of the customer.

26. The method of claim 21 , wherein execution of the set of commands further comprises:

receiving first cloud computing environment data from a first source and second cloud computing environment data from a second source within the cloud computing environment;

determining that the first cloud computing environment data alone or the second cloud computing environment data alone do not indicate an anomaly within the anomaly detection system;

based on the determination, analyzing the first cloud computing environment data and the second cloud computing environment data together to detect anomalies; and

based on the analyzing, determining that the first cloud computing environment data and the second cloud computing environment data taken together indicate an anomaly within the cloud computing environment.

27. A method of automated integration of a cloud computing environment of a customer with an anomaly detection system, the method comprising:

executing a set of commands for generating cloud computing infrastructure for anomaly detection, wherein executing the set of commands comprises:

generating a first set of anomaly detection infrastructure elements within the cloud computing environment;

generating a second set of anomaly detection infrastructure elements at the anomaly detection system;

receiving first cloud computing environment data from a first source and second cloud computing environment data from a second source within the cloud computing environment;

determining that the first cloud computing environment data alone or the second cloud computing environment data alone do not indicate an anomaly within the anomaly detection system;

based on the determination, analyzing the first cloud computing environment data and the second cloud computing environment data together to detect anomalies; and

based on the analyzing, determining that the first cloud computing environment data and the second cloud computing environment data taken together indicate an anomaly within the cloud computing environment.

28. The method of claim 27 , wherein execution of the set of commands further comprises automatically installing one or more agents on customer resources at the cloud computing environment.

29. The method of claim 27 , wherein execution of the set of commands further comprises creating user profiles and application profiles within the anomaly detection system.

30. The method of claim 27 , wherein execution of the set of commands further comprises automatically enabling a set of anomaly detection features for the customer in the anomaly detection system, wherein the set of anomaly detection features is a default set of features.

31. The method of claim 27 , wherein execution of the set of commands further comprises causing existing anomaly detection modules of the anomaly detection system to execute anomaly detection for computing resources of the cloud computing environment of the customer.

32. A computer program product disposed upon a non-transitory computer readable medium, the computer program product comprising computer program instructions that, when executed, cause a computer to carry out the steps of:

receiving cloud computing environment data for the cloud computing environment;

generating, based on the received cloud computing environment data, a set of commands for generating cloud computing infrastructure for anomaly detection, the set of commands including:

one or more commands for generating a first set of anomaly detection infrastructure elements within the cloud computing environment; and

one or more commands for generating a second set of anomaly detection infrastructure elements at an anomaly detection system;

initiating an execution of the set of commands;

based on received cloud computing environment data, detecting that the cloud computing environment is serviced by a first cloud services provider and a second cloud services provider;

determining that a new user account was created within a first user directory of the first cloud services provider;

based on the determination, presenting a second request to create a second instance of the new user account within a second user directory of the second cloud services provider at the cloud computing environment; and

based on a response to the second request, creating the second instance of the new user account and updating a customer account profile to include information for the second instance of the new user account.

33. The computer program product of claim 32 , wherein generating the set of commands further comprises:

generating one or more native command line interface (CLI) commands of a native CLI of the anomaly detection system.

34. The computer program product of claim 32 , wherein generating the set of commands further comprises:

generating shell interface commands of a cloud services provider shell interface, wherein the cloud services provider shell interface is associated with a cloud services provider of the cloud computing environment of a customer.

35. A computer program product disposed upon a non-transitory computer readable medium, the computer program product comprising computer program instructions that, when executed, cause a computer to carry out the steps of:

receiving cloud computing environment data for the cloud computing environment;

generating, based on the received cloud computing environment data, a set of commands for generating cloud computing infrastructure for anomaly detection, the set of commands including:

one or more commands for generating a first set of anomaly detection infrastructure elements within the cloud computing environment; and

one or more commands for generating a second set of anomaly detection infrastructure elements at an anomaly detection system;

initiating an execution of the set of commands;

generating a state file, wherein the state file indicates a current state of the cloud computing environment;

storing the state file at the anomaly detection system;

detecting that an additional anomaly detection feature is available for installation at the cloud computing environment; and

based on the detection, analyzing the state file to determine whether the additional anomaly detection feature is installed for the cloud computing environment.

36. The computer program product of claim 35 , wherein generating the set of commands further comprises:

generating one or more native command line interface (CLI) commands of a native CLI of the anomaly detection system.

37. The computer program product of claim 35 , wherein generating the set of commands further comprises:

generating shell interface commands of a cloud services provider shell interface, wherein the cloud services provider shell interface is associated with a cloud services provider of the cloud computing environment of a customer.

38. A computer program product disposed upon a non-transitory computer readable medium, the computer program product comprising computer program instructions that, when executed, cause a computer to carry out the steps of:

receiving cloud computing environment data for the cloud computing environment;

generating, based on the received cloud computing environment data, a set of commands for generating cloud computing infrastructure for anomaly detection, the set of commands including:

one or more commands for generating a first set of anomaly detection infrastructure elements within the cloud computing environment; and

one or more commands for generating a second set of anomaly detection infrastructure elements at an anomaly detection system;

initiating an execution of the set of commands;

receiving first cloud computing environment data from a first source and second cloud computing environment data from a second source within the cloud computing environment;

determining that the first cloud computing environment data alone or the second cloud computing environment data alone do not indicate an anomaly within the anomaly detection system;

based on the determination, analyzing the first cloud computing environment data and the second cloud computing environment data together to detect anomalies; and

based on the analyzing, determining that the first cloud computing environment data and the second cloud computing environment data taken together indicate an anomaly within the cloud computing environment.

39. The computer program product of claim 38 , wherein generating the set of commands further comprises:

generating one or more native command line interface (CLI) commands of a native CLI of the anomaly detection system.

40. The computer program product of claim 38 , wherein generating the set of commands further comprises:

generating shell interface commands of a cloud services provider shell interface, wherein the cloud services provider shell interface is associated with a cloud services provider of the cloud computing environment of a customer.

Assignments (2)
MERGER Recorded Oct 7, 2024
From: LACEWORK, INC.
To: FORTINET, INC.
Reel/Frame 069269/0377 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 7, 2022
From: MCALEER, DAVID; HAZEKAMP, DAVID M.; WILSON, DECLAN; GOGGIN, ELLIE; CHEN, YIJOU
To: LACEWORK, INC.
Reel/Frame 061015/0111 →
Continuity (9)
Continuation In Part 17504311 · Oct 18, 2021
Continuation 16665961 · Oct 28, 2019
Continuation 16134794 · Sep 18, 2018
Provisional Application 63366363 · Jun 14, 2022
Provisional Application 63244336 · Sep 15, 2021
Provisional Application 63244367 · Sep 15, 2021
Provisional Application 63241965 · Sep 8, 2021
Provisional Application 62650971 · Mar 30, 2018
Provisional Application 62590986 · Nov 27, 2017
References Cited (400)
US 5584024A · Shwartz · 1996 [cited by applicant]
US 5806062A · Chen et al. · 1998 [cited by applicant]
US 6363411B1 · Dugan et al. · 2002 [cited by applicant]
US 7054873B2 · Nordström et al. · 2006 [cited by applicant]
US 7233333B2 · Lomask · 2007 [cited by applicant]
US 7478246B2 · Arndt et al. · 2009 [cited by applicant]
US 7484091B2 · Bade et al. · 2009 [cited by applicant]
US 7526501B2 · Albahari et al. · 2009 [cited by applicant]
US 7707411B2 · Bade et al. · 2010 [cited by applicant]
US 7739211B2 · Coffman et al. · 2010 [cited by applicant]
US 7747559B2 · Leitner et al. · 2010 [cited by applicant]
US 7765431B2 · Agha et al. · 2010 [cited by applicant]
US 8050907B2 · Baisley et al. · 2011 [cited by applicant]
US 8086852B2 · Bade et al. · 2011 [cited by applicant]
US 8103906B1 · Alibakhsh et al. · 2012 [cited by applicant]
US 8122122B1 · Clingenpeel et al. · 2012 [cited by applicant]
US 8140977B2 · Kriss et al. · 2012 [cited by applicant]
US 8160999B2 · Jin et al. · 2012 [cited by applicant]
US 8209204B2 · Adler et al. · 2012 [cited by applicant]
US 8301660B2 · Yalamanchi · 2012 [cited by applicant]
US 8352589B2 · Ridel et al. · 2013 [cited by applicant]
US 8443442B2 · Wang et al. · 2013 [cited by applicant]
US 8490055B2 · Basak · 2013 [cited by applicant]
US 8671453B2 · Underwood et al. · 2014 [cited by applicant]
US 8862524B2 · Zheng et al. · 2014 [cited by applicant]
US 9021583B2 · Wittenstein et al. · 2015 [cited by applicant]
US 9037273B2 · Mikkelsen · 2015 [cited by applicant]
US 9043764B2 · Ranganathan et al. · 2015 [cited by applicant]
US 9053437B2 · Adler et al. · 2015 [cited by applicant]
US 9064210B1 · Hart · 2015 [cited by applicant]
US 9075618B2 · Winternitz et al. · 2015 [cited by applicant]
US 9110873B2 · Woodall et al. · 2015 [cited by applicant]
US 9159024B2 · Bhanot et al. · 2015 [cited by applicant]
US 9189623B1 · Lin et al. · 2015 [cited by applicant]
US 9225730B1 · Brezinski · 2015 [cited by applicant]
US 9332020B2 · Thomas et al. · 2016 [cited by applicant]
US 9497224B2 · Sweet et al. · 2016 [cited by applicant]
US 9515999B2 · Ylonen · 2016 [cited by applicant]
US 9516053B1 · Muddu et al. · 2016 [cited by applicant]
US 9558265B1 · Tacchi et al. · 2017 [cited by applicant]
US 9589069B2 · Yang et al. · 2017 [cited by applicant]
US 9591010B1 · Muddu et al. · 2017 [cited by applicant]
US 9596253B2 · Chauhan et al. · 2017 [cited by applicant]
US 9596254B1 · Muddu et al. · 2017 [cited by applicant]
US 9600915B2 · Winternitz et al. · 2017 [cited by applicant]
US 9654503B1 · Kowalyshyn · 2017 [cited by applicant]
US 9667641B2 · Muddu et al. · 2017 [cited by applicant]
US 9679243B2 · Zou et al. · 2017 [cited by applicant]
US 9699205B2 · Muddu et al. · 2017 [cited by applicant]
US 9710332B1 · Fan et al. · 2017 [cited by applicant]
US 9720703B2 · Reick et al. · 2017 [cited by applicant]
US 9720704B2 · Reick et al. · 2017 [cited by applicant]
US 9727441B2 · Agarwal et al. · 2017 [cited by applicant]
US 9727604B2 · Jin et al. · 2017 [cited by applicant]
US 9729416B1 · Khanal et al. · 2017 [cited by applicant]
US 9734040B2 · Gounares · 2017 [cited by applicant]
US 9749339B2 · Kadambe et al. · 2017 [cited by applicant]
US 9811790B2 · Ahern et al. · 2017 [cited by applicant]
US 9813435B2 · Muddu et al. · 2017 [cited by applicant]
US 9824473B2 · Winternitz et al. · 2017 [cited by applicant]
US 9838410B2 · Muddu et al. · 2017 [cited by applicant]
US 9843837B2 · Gopalan · 2017 [cited by applicant]
US 9853968B2 · Shen et al. · 2017 [cited by applicant]
US 9864672B2 · Seto et al. · 2018 [cited by applicant]
US 9866433B1 · Fakhouri · 2018 [cited by examiner]
US 9923911B2 · Vasseur et al. · 2018 [cited by applicant]
US 9953014B1 · Reshadi et al. · 2018 [cited by applicant]
US 9985827B2 · Li et al. · 2018 [cited by applicant]
US 10003605B2 · Muddu et al. · 2018 [cited by applicant]
US 10033611B1 · Linkous et al. · 2018 [cited by applicant]
US 10115111B2 · Miltonberger · 2018 [cited by applicant]
US 10116670B2 · Muddu et al. · 2018 [cited by applicant]
US 10122740B1 · Finkelshtein et al. · 2018 [cited by applicant]
US 10127273B2 · Dickey · 2018 [cited by applicant]
US 10142357B1 · Tamersoy et al. · 2018 [cited by applicant]
US 10148677B2 · Muddu et al. · 2018 [cited by applicant]
US 10158652B2 · Muddu et al. · 2018 [cited by applicant]
US 10205735B2 · Apostolopoulos · 2019 [cited by applicant]
US 10205736B2 · Rieke et al. · 2019 [cited by applicant]
US 10237294B1 · Zadeh et al. · 2019 [cited by applicant]
US 10243970B2 · Muddu et al. · 2019 [cited by applicant]
US 10254848B2 · Winternitz et al. · 2019 [cited by applicant]
US 10338895B2 · Zhang et al. · 2019 [cited by applicant]
US 10339309B1 · Kling et al. · 2019 [cited by applicant]
US 10367704B2 · Giura et al. · 2019 [cited by applicant]
US 10382303B2 · Khanal et al. · 2019 [cited by applicant]
US 10389738B2 · Muddu et al. · 2019 [cited by applicant]
US 10389742B2 · Reddy et al. · 2019 [cited by applicant]
US 10419463B2 · Muddu et al. · 2019 [cited by applicant]
US 10419465B2 · Muddu et al. · 2019 [cited by applicant]
US 10419468B2 · Glatfelter et al. · 2019 [cited by applicant]
US 10432639B1 · Bebee et al. · 2019 [cited by applicant]
US 10447526B2 · Tucker et al. · 2019 [cited by applicant]
US 10454889B2 · Huang · 2019 [cited by applicant]
US 10459979B2 · Piechowicz et al. · 2019 [cited by applicant]
US 10462169B2 · Durairaj et al. · 2019 [cited by applicant]
US 10491705B2 · Oetting et al. · 2019 [cited by applicant]
US 10496468B2 · Gefen et al. · 2019 [cited by applicant]
US 10505818B1 · Yona et al. · 2019 [cited by applicant]
US 10521584B1 · Mehr · 2019 [cited by applicant]
US 10534633B2 · Hilemon et al. · 2020 [cited by applicant]
US 10565373B1 · Rao et al. · 2020 [cited by applicant]
US 10594718B1 · Deaguero et al. · 2020 [cited by applicant]
US 10666668B2 · Muddu et al. · 2020 [cited by applicant]
US 10673880B1 · Pratt et al. · 2020 [cited by applicant]
US 10693900B2 · Zadeh et al. · 2020 [cited by applicant]
US 10698954B2 · Piechowicz et al. · 2020 [cited by applicant]
US 10708082B1 · Bakiaraj et al. · 2020 [cited by applicant]
US 10735329B2 · Wang et al. · 2020 [cited by applicant]
US 10756982B2 · Bai et al. · 2020 [cited by applicant]
US 10771488B2 · Verma et al. · 2020 [cited by applicant]
US 10776191B2 · Zheng et al. · 2020 [cited by applicant]
US 10788570B2 · Wilson · 2020 [cited by applicant]
US 10791131B2 · Nor et al. · 2020 [cited by applicant]
US 10797974B2 · Giura et al. · 2020 [cited by applicant]
US 10812497B2 · Venkatramani et al. · 2020 [cited by applicant]
US 10904270B2 · Muddu et al. · 2021 [cited by applicant]
US 10911470B2 · Muddu et al. · 2021 [cited by applicant]
US 11036716B2 · Griffith et al. · 2021 [cited by applicant]
US 11044264B2 · Durairaj et al. · 2021 [cited by applicant]
US 11082289B2 · Dang et al. · 2021 [cited by applicant]
US 11120343B2 · Das et al. · 2021 [cited by applicant]
US 11126533B2 · Knowles et al. · 2021 [cited by applicant]
US 11194791B1 · Baine · 2021 [cited by examiner]
US 11194849B2 · Lassoued et al. · 2021 [cited by applicant]
US 11212299B2 · Gamble et al. · 2021 [cited by applicant]
US 11233821B2 · Yadav et al. · 2022 [cited by applicant]
US 11258807B2 · Muddu et al. · 2022 [cited by applicant]
US 11281519B2 · Krishnaswamy et al. · 2022 [cited by applicant]
US 11314789B2 · Goldfarb · 2022 [cited by applicant]
US 11334661B1 · Brandwine · 2022 [cited by examiner]
US 11411966B2 · Muddu et al. · 2022 [cited by applicant]
US 11431735B2 · Shua · 2022 [cited by applicant]
US 11463464B2 · Zadeh et al. · 2022 [cited by applicant]
US 11489863B1 · Shua et al. · 2022 [cited by applicant]
US 11494787B2 · Erickson et al. · 2022 [cited by applicant]
US 11544138B2 · Kapish et al. · 2023 [cited by applicant]
US 11546217B1 · Vishwakarma · 2023 [cited by examiner]
US 11575693B1 · Muddu et al. · 2023 [cited by applicant]
US 11606272B1 · Popelka et al. · 2023 [cited by applicant]
US 11636090B2 · Li et al. · 2023 [cited by applicant]
US 11640388B2 · Yang et al. · 2023 [cited by applicant]
US 11647034B2 · Levin et al. · 2023 [cited by applicant]
US 11658990B2 · Shapoury · 2023 [cited by applicant]
US 11669571B2 · Binkley et al. · 2023 [cited by applicant]
US 11693958B1 · Steiman · 2023 [cited by applicant]
US 11722554B2 · Keren et al. · 2023 [cited by applicant]
US 11734351B2 · Binkley et al. · 2023 [cited by applicant]
US 11734419B1 · Mackle · 2023 [cited by applicant]
US 11748473B2 · Araujo et al. · 2023 [cited by applicant]
US 11755576B1 · Jiang et al. · 2023 [cited by applicant]
US 11755602B2 · Smith et al. · 2023 [cited by applicant]
US 11769098B2 · Adinarayan et al. · 2023 [cited by applicant]
US 11770387B1 · Shivamoggi et al. · 2023 [cited by applicant]
US 20020184225A1 · Ghukasyan · 2002 [cited by applicant]
US 20030037136A1 · Labovitz et al. · 2003 [cited by applicant]
US 20030179227A1 · Ahmad et al. · 2003 [cited by applicant]
US 20040015470A1 · Smith et al. · 2004 [cited by applicant]
US 20040225929A1 · Agha et al. · 2004 [cited by applicant]
US 20050102284A1 · Srinivasan et al. · 2005 [cited by applicant]
US 20050188222A1 · Motsinger et al. · 2005 [cited by applicant]
US 20050246521A1 · Bade et al. · 2005 [cited by applicant]
US 20060025987A1 · Baisley et al. · 2006 [cited by applicant]
US 20060026419A1 · Arndt et al. · 2006 [cited by applicant]
US 20060085437A1 · Brodhun et al. · 2006 [cited by applicant]
US 20060109271A1 · Lomask · 2006 [cited by applicant]
US 20060259470A1 · Chandrasekharan et al. · 2006 [cited by applicant]
US 20060288415A1 · Wong · 2006 [cited by applicant]
US 20070050497A1 · Haley et al. · 2007 [cited by applicant]
US 20070118909A1 · Hertzog et al. · 2007 [cited by applicant]
US 20070130330A1 · Ridel et al. · 2007 [cited by applicant]
US 20070168696A1 · Ridel et al. · 2007 [cited by applicant]
US 20070214111A1 · Jin et al. · 2007 [cited by applicant]
US 20070282916A1 · Albahari et al. · 2007 [cited by applicant]
US 20080109730A1 · Coffman et al. · 2008 [cited by applicant]
US 20080147707A1 · Jin et al. · 2008 [cited by applicant]
US 20080148180A1 · Liu et al. · 2008 [cited by applicant]
US 20080151893A1 · Nordmark et al. · 2008 [cited by applicant]
US 20080270451A1 · Thomsen et al. · 2008 [cited by applicant]
US 20090006843A1 · Bade et al. · 2009 [cited by applicant]
US 20090007010A1 · Kriss et al. · 2009 [cited by applicant]
US 20090019160A1 · Schuler · 2009 [cited by applicant]
US 20090063857A1 · Bade et al. · 2009 [cited by applicant]
US 20090228474A1 · Chiu et al. · 2009 [cited by applicant]
US 20090271504A1 · Ginter et al. · 2009 [cited by applicant]
US 20090307651A1 · Senthil et al. · 2009 [cited by applicant]
US 20090327328A1 · Woodall et al. · 2009 [cited by applicant]
US 20100042823A1 · Arndt et al. · 2010 [cited by applicant]
US 20100094767A1 · Miltonberger · 2010 [cited by applicant]
US 20100114931A1 · Xie et al. · 2010 [cited by applicant]
US 20100172261A1 · Shinbo et al. · 2010 [cited by applicant]
US 20100274785A1 · Procopiuc et al. · 2010 [cited by applicant]
US 20110055138A1 · Khanduja et al. · 2011 [cited by applicant]
US 20110119100A1 · Ruhl et al. · 2011 [cited by applicant]
US 20110154287A1 · Mukkamala et al. · 2011 [cited by applicant]
US 20120005243A1 · Merwe et al. · 2012 [cited by applicant]
US 20120143898A1 · Bruno et al. · 2012 [cited by applicant]
US 20120159333A1 · Mital et al. · 2012 [cited by applicant]
US 20120317151A1 · Ruf et al. · 2012 [cited by applicant]
US 20120323956A1 · Dumitru et al. · 2012 [cited by applicant]
US 20130024412A1 · Gong et al. · 2013 [cited by applicant]
US 20130151453A1 · Bhanot et al. · 2013 [cited by applicant]
US 20130304915A1 · Kawai · 2013 [cited by applicant]
US 20130305357A1 · Ayyagari et al. · 2013 [cited by applicant]
US 20140067750A1 · Ranganathan et al. · 2014 [cited by applicant]
US 20140115001A1 · Arroyo et al. · 2014 [cited by applicant]
US 20140115011A1 · Buemner et al. · 2014 [cited by applicant]
US 20140125672A1 · Winternitz et al. · 2014 [cited by applicant]
US 20140208191A1 · Zaric et al. · 2014 [cited by applicant]
US 20140245443A1 · Chakraborty · 2014 [cited by applicant]
US 20140279779A1 · Zou et al. · 2014 [cited by applicant]
US 20140280068A1 · Dhoopar et al. · 2014 [cited by applicant]
US 20140359558A1 · Chamberlain · 2014 [cited by applicant]
US 20150058619A1 · Sweet et al. · 2015 [cited by applicant]
US 20150135312A1 · Wada et al. · 2015 [cited by applicant]
US 20150180894A1 · Sadovsky · 2015 [cited by examiner]
US 20150188751A1 · Vasseur et al. · 2015 [cited by applicant]
US 20150310649A1 · Winternitz et al. · 2015 [cited by applicant]
US 20150341379A1 · Lefebvre et al. · 2015 [cited by applicant]
US 20150356144A1 · Chawla et al. · 2015 [cited by applicant]
US 20160078365A1 · Baumard · 2016 [cited by applicant]
US 20160080404A1 · Kohout et al. · 2016 [cited by applicant]
US 20160110434A1 · Kakaraddi et al. · 2016 [cited by applicant]
US 20160120070A1 · Myrah et al. · 2016 [cited by applicant]
US 20160149937A1 · Katmor et al. · 2016 [cited by applicant]
US 20160205125A1 · Kim et al. · 2016 [cited by applicant]
US 20160218911A1 · Wessels et al. · 2016 [cited by applicant]
US 20160357521A1 · Zhang et al. · 2016 [cited by applicant]
US 20160359592A1 · Kulshreshtha et al. · 2016 [cited by applicant]
US 20160359872A1 · Yadav et al. · 2016 [cited by applicant]
US 20170054724A1 · Maple · 2017 [cited by examiner]
US 20170063888A1 · Muddu et al. · 2017 [cited by applicant]
US 20170063903A1 · Muddu et al. · 2017 [cited by applicant]
US 20170063905A1 · Muddu et al. · 2017 [cited by applicant]
US 20170063906A1 · Muddu et al. · 2017 [cited by applicant]
US 20170063908A1 · Muddu et al. · 2017 [cited by applicant]
US 20170063909A1 · Muddu et al. · 2017 [cited by applicant]
US 20170063910A1 · Muddu et al. · 2017 [cited by applicant]
US 20170063911A1 · Muddu et al. · 2017 [cited by applicant]
US 20170063912A1 · Muddu et al. · 2017 [cited by applicant]
US 20170070594A1 · Oetting et al. · 2017 [cited by applicant]
US 20170102961A1 · Hilemon et al. · 2017 [cited by applicant]
US 20170118099A1 · Huang · 2017 [cited by applicant]
US 20170118240A1 · Reddy et al. · 2017 [cited by applicant]
US 20170134240A1 · Hévizi et al. · 2017 [cited by applicant]
US 20170142140A1 · Muddu et al. · 2017 [cited by applicant]
US 20170147646A1 · Lee et al. · 2017 [cited by applicant]
US 20170148197A1 · Winternitz et al. · 2017 [cited by applicant]
US 20170155570A1 · Maheshwari et al. · 2017 [cited by applicant]
US 20170155672A1 · Muthukrishnan et al. · 2017 [cited by applicant]
US 20170163666A1 · Venkatramani et al. · 2017 [cited by applicant]
US 20170223036A1 · Muddu et al. · 2017 [cited by applicant]
US 20170230183A1 · Sweet et al. · 2017 [cited by applicant]
US 20170251013A1 · Kirti et al. · 2017 [cited by applicant]
US 20170272344A1 · Tang et al. · 2017 [cited by applicant]
US 20170277553A1 · Zada et al. · 2017 [cited by applicant]
US 20170279827A1 · Savalle et al. · 2017 [cited by applicant]
US 20170288974A1 · Yoshihira et al. · 2017 [cited by applicant]
US 20170318043A1 · Shin · 2017 [cited by examiner]
US 20170330096A1 · Gupta et al. · 2017 [cited by applicant]
US 20170346683A1 · Li et al. · 2017 [cited by applicant]
US 20170359361A1 · Modani et al. · 2017 [cited by applicant]
US 20170366492A1 · Ho et al. · 2017 [cited by applicant]
US 20180004835A1 · Piechowicz et al. · 2018 [cited by applicant]
US 20180004859A1 · Piechowicz et al. · 2018 [cited by applicant]
US 20180007145A1 · Piechowicz et al. · 2018 [cited by applicant]
US 20180013650A1 · Khanal et al. · 2018 [cited by applicant]
US 20180019932A1 · Giura et al. · 2018 [cited by applicant]
US 20180020015A1 · Munro et al. · 2018 [cited by applicant]
US 20180034840A1 · Marquardt et al. · 2018 [cited by applicant]
US 20180063178A1 · Jadhav et al. · 2018 [cited by applicant]
US 20180069885A1 · Patterson et al. · 2018 [cited by applicant]
US 20180089132A1 · Atta et al. · 2018 [cited by applicant]
US 20180103052A1 · Choudhury et al. · 2018 [cited by applicant]
US 20180115578A1 · Subbarayan et al. · 2018 [cited by applicant]
US 20180123864A1 · Tucker et al. · 2018 [cited by applicant]
US 20180137858A1 · Saxena et al. · 2018 [cited by applicant]
US 20180173789A1 · Llagostera et al. · 2018 [cited by applicant]
US 20180174062A1 · Simo et al. · 2018 [cited by applicant]
US 20180181750A1 · Lamothe-Brassard · 2018 [cited by applicant]
US 20180191781A1 · Palani et al. · 2018 [cited by applicant]
US 20180196867A1 · Wiesmaier · 2018 [cited by examiner]
US 20180211425A1 · Winternitz et al. · 2018 [cited by applicant]
US 20180219888A1 · Apostolopoulos · 2018 [cited by applicant]
US 20180219897A1 · Muddu et al. · 2018 [cited by applicant]
US 20180248901A1 · Rieke · 2018 [cited by applicant]
US 20180268078A1 · Gianetto et al. · 2018 [cited by applicant]
US 20180288063A1 · Koottayi et al. · 2018 [cited by applicant]
US 20180329958A1 · Choudhury et al. · 2018 [cited by applicant]
US 20180336353A1 · Manadhata et al. · 2018 [cited by applicant]
US 20180357422A1 · Telang et al. · 2018 [cited by applicant]
US 20180359162A1 · Savov et al. · 2018 [cited by applicant]
US 20180367548A1 · Stokes, III et al. · 2018 [cited by applicant]
US 20190028327A1 · Silva et al. · 2019 [cited by applicant]
US 20190042950A1 · Lin et al. · 2019 [cited by applicant]
US 20190050445A1 · Griffith et al. · 2019 [cited by applicant]
US 20190058626A1 · Knowles et al. · 2019 [cited by applicant]
US 20190075126A1 · Muddu et al. · 2019 [cited by applicant]
US 20190101622A1 · Wilson · 2019 [cited by applicant]
US 20190109870A1 · Bedhapudi et al. · 2019 [cited by applicant]
US 20190132224A1 · Verma et al. · 2019 [cited by applicant]
US 20190132347A1 · Wakid · 2019 [cited by examiner]
US 20190158524A1 · Zadeh et al. · 2019 [cited by applicant]
US 20190163555A1 · Zheng et al. · 2019 [cited by applicant]
US 20190222597A1 · Crabtree et al. · 2019 [cited by applicant]
US 20190259033A1 · Reddy et al. · 2019 [cited by applicant]
US 20190312796A1 · Giura et al. · 2019 [cited by applicant]
US 20190312898A1 · Verma et al. · 2019 [cited by applicant]
US 20190327251A1 · Muddu et al. · 2019 [cited by applicant]
US 20190339965A1 · Garvey et al. · 2019 [cited by applicant]
US 20190342307A1 · Gamble et al. · 2019 [cited by applicant]
US 20190342311A1 · Muddu et al. · 2019 [cited by applicant]
US 20190349305A1 · Wang et al. · 2019 [cited by applicant]
US 20190354554A1 · Piechowicz et al. · 2019 [cited by applicant]
US 20190356555A1 · Bai · 2019 [cited by applicant]
US 20190364067A1 · Yona et al. · 2019 [cited by applicant]
US 20190227860A1 · Gefen et al. · 2019 [cited by applicant]
US 20190378050A1 · Edkin et al. · 2019 [cited by applicant]
US 20200007397A1 · Fainberg · 2020 [cited by examiner]
US 20200014718A1 · Durairaj et al. · 2020 [cited by applicant]
US 20200021607A1 · Muddu et al. · 2020 [cited by applicant]
US 20200028867A1 · Monsen · 2020 [cited by examiner]
US 20200065857A1 · Lagi et al. · 2020 [cited by applicant]
US 20200076685A1 · Vaidya et al. · 2020 [cited by applicant]
US 20200175361A1 · Che et al. · 2020 [cited by applicant]
US 20200192690A1 · Gupta et al. · 2020 [cited by applicant]
US 20200228555A1 · Wittenschlaeger · 2020 [cited by applicant]
US 20200252376A1 · Feng et al. · 2020 [cited by applicant]
US 20200272740A1 · Obee et al. · 2020 [cited by applicant]
US 20200278892A1 · Nainar et al. · 2020 [cited by applicant]
US 20200280592A1 · Ithal et al. · 2020 [cited by applicant]
US 20200287922A1 · Wang · 2020 [cited by examiner]
US 20200287923A1 · Raghavendra et al. · 2020 [cited by applicant]
US 20200287927A1 · Zadeh et al. · 2020 [cited by applicant]
US 20200311644A1 · Willard, III et al. · 2020 [cited by applicant]
US 20200320106A1 · Goldfarb · 2020 [cited by applicant]
US 20200334293A1 · Piechowicz et al. · 2020 [cited by applicant]
US 20200351151A1 · Dang et al. · 2020 [cited by applicant]
US 20200403860A1 · Lewis et al. · 2020 [cited by applicant]
US 20200404008A1 · Venkatramani et al. · 2020 [cited by applicant]
US 20200412752A1 · Shapoury · 2020 [cited by applicant]
US 20210019209A1 · Krishnaswamy et al. · 2021 [cited by applicant]
US 20210232420A1 · Dhruvakumar et al. · 2021 [cited by applicant]
US 20210286798A1 · Li et al. · 2021 [cited by applicant]
US 20210294798A1 · Binkley et al. · 2021 [cited by applicant]
US 20210306354A1 · Raghuramu · 2021 [cited by examiner]
US 20210329019A1 · Shua · 2021 [cited by applicant]
US 20210336976A1 · Shua · 2021 [cited by applicant]
US 20210352136A1 · Dojka · 2021 [cited by examiner]
US 20210377287A1 · Shua · 2021 [cited by applicant]
US 20210406917A1 · Erickson et al. · 2021 [cited by applicant]
US 20220004718A1 · Quamar et al. · 2022 [cited by applicant]
US 20220050840A1 · Parravicini et al. · 2022 [cited by applicant]
US 20220058193A1 · Smith et al. · 2022 [cited by applicant]
US 20220067186A1 · Thakur et al. · 2022 [cited by applicant]
US 20220086179A1 · Levin et al. · 2022 [cited by applicant]
US 20220092481A1 · Neithalath et al. · 2022 [cited by applicant]
US 20220121741A1 · Araujo et al. · 2022 [cited by applicant]
US 20220124108A1 · Gamble et al. · 2022 [cited by applicant]
US 20220129803A1 · Bikumala et al. · 2022 [cited by applicant]
US 20220191226A1 · Chan et al. · 2022 [cited by applicant]
US 20220247768A1 · Datar · 2022 [cited by examiner]
US 20220327119A1 · Gasper et al. · 2022 [cited by applicant]
US 20220342690A1 · Shua · 2022 [cited by applicant]
US 20220345480A1 · Shua · 2022 [cited by applicant]
US 20220345481A1 · Shua · 2022 [cited by applicant]
US 20220345483A1 · Shua · 2022 [cited by applicant]
US 20220350789A1 · Yang et al. · 2022 [cited by applicant]
US 20220350931A1 · Shua · 2022 [cited by applicant]
US 20220374800A1 · Adinarayan et al. · 2022 [cited by applicant]
US 20220376970A1 · Chawathe et al. · 2022 [cited by applicant]
US 20220382611A1 · Kapish et al. · 2022 [cited by applicant]
US 20220394082A1 · Keren et al. · 2022 [cited by applicant]
US 20220414072A1 · Tandon et al. · 2022 [cited by applicant]
US 20220414105A1 · Umay et al. · 2022 [cited by applicant]
US 20230025252A1 · Erickson et al. · 2023 [cited by applicant]
US 20230039566A1 · Ghag et al. · 2023 [cited by applicant]
US 20230052827A1 · Araujo et al. · 2023 [cited by applicant]
US 20230086473A1 · Deliwala · 2023 [cited by examiner]
US 20230088960A1 · Popelka et al. · 2023 [cited by applicant]
US 20230096930A1 · Dasdan · 2023 [cited by applicant]
US 20230101773A1 · Katahanas et al. · 2023 [cited by applicant]
US 20230138371A1 · Bandukwala et al. · 2023 [cited by applicant]
US 20230153084A1 · Mohamedali · 2023 [cited by examiner]
US 20230199025A1 · Xu · 2023 [cited by examiner]
US 20230244523A1 · Gorantla et al. · 2023 [cited by applicant]
US 20230251960A1 · Sharma et al. · 2023 [cited by applicant]
US 20230259390A1 · Howley · 2023 [cited by examiner]
US 20230275909A1 · Shivamoggi et al. · 2023 [cited by applicant]
US 20230291755A1 · Siebel et al. · 2023 [cited by applicant]
US 20240007492A1 · Shen · 2024 [cited by examiner]
“How can I use the AWS CLI to create a CloudWatch alarm based on anomaly detection?,” AWS Post, Surbhi. (Year: 2024). [cited by examiner]
“RFC: Anomaly Detection CLI,” Jun. 2020. (Year: 2020). [cited by examiner]
Ai-Yaseen et al., “Real-Time Intrusion Detection System Using Multi-Agent System”, IAENG International Journal of Computer Science, vol. 43, No. 1, Feb. 2016, pp. 80-90, International Association of Engineers (IAENG), H… [cited by applicant]
Akoglu et al., “Graph-based Anomaly Detection and Description: A Survey”, Apr. 28, 2014. [cited by applicant]
Amidon et al., “Program Fracture and Recombination for Efficient Automatic Code Reuse”, In 2015 IEEE High Performance Extreme Computing Conference (HPEC), Sep. 2015, pp. 1-6, IEEE.org (online), DOI: 10.1109/HPEC.2015.73… [cited by applicant]
Ammar et al., “Query Optimization Techniques in Graph Databases”, International Journal of Database Management Systems (IIDMS), vol. 8, No. 4, Aug. 2016, pp. 1-14 (Year: 2016). [cited by applicant]
Balasubramaniyan et al., “An Architecture For Intrusion Detection Using Autonomous Agents”, In Proceedings 14th Annual Computer Security Applications Conference (Cat. No. 98EX217), 19 pages, Jun. 1998, IEEE, DOI: 10.110… [cited by applicant]
Beutel et al., “User Behavior Modeling with Large-Scale Graph Analysis”, Computer Science Department, Carnegie Mellon University, May 2016. [cited by applicant]
Bugiel et al., “Towards Taming Privilege-Escalation Attacks on Android”, In NOSS (vol. 17, p. 19), Feb. 2012. [cited by applicant]
Cited By (8)
US 1,098,136 US 12,468,807 US 12,475,230 US 12,542,650 US 12,592,917 US 12,592,931 US 12,640,977 US 12,693,832