(19)
(11)EP 3 080 741 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
07.03.2018 Bulletin 2018/10

(21)Application number: 14868736.1

(22)Date of filing:  13.11.2014
(51)Int. Cl.: 
G06F 21/00  (2013.01)
H04L 29/06  (2006.01)
(86)International application number:
PCT/US2014/065523
(87)International publication number:
WO 2015/088702 (18.06.2015 Gazette  2015/24)

(54)

SYSTEMS AND METHODS FOR CLOUD SECURITY MONITORING AND THREAT INTELLIGENCE

SYSTEME UND VERFAHREN ZUR CLOUD-SICHERHEITSÜBERWACHUNG UND BEDROHUNGSERKENNUNG

SYSTÈMES ET PROCÉDÉS POUR LE CONTRÔLE DE LA SÉCURITÉ D'UN CLOUD ET LE RENSEIGNEMENT SUR LES MENACES


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 13.12.2013 US 201361916070 P
24.10.2014 US 201414523804

(43)Date of publication of application:
19.10.2016 Bulletin 2016/42

(73)Proprietor: Oracle International Corporation
Redwood Shores, California 94065 (US)

(72)Inventors:
  • KIRTI, Ganesh
    San Jose, CA 95054 (US)
  • GUPTA, Rohit
    Redwood City, CA 94065 (US)
  • BISWAS, Kamalendu
    San Ramon, CA 94582 (US)
  • TURLAPATI, Ramana Rao Satyasai
    Fremont, CA 94555 (US)

(74)Representative: Gill Jennings & Every LLP 
The Broadgate Tower 20 Primrose Street
London EC2A 2ES
London EC2A 2ES (GB)


(56)References cited: : 
US-A1- 2003 048 174
US-A1- 2012 030 767
US-A1- 2013 066 945
US-A1- 2013 191 921
US-B1- 7 603 452
US-A1- 2011 185 055
US-A1- 2013 036 459
US-A1- 2013 066 945
US-A1- 2013 191 921
US-B1- 7 603 452
  
  • GUPTA ET AL.: 'Identification of Effective Public Cloud on User Query', [Online] 07 July 2013, XP055234968 Retrieved from the Internet: <URL:http://ijcttjournal.org/Volume4/issue- 7/IJCTT-V4I7P103.pdf> [retrieved on 2015-01-22]
  
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


Description

FIELD OF THE INVENTION



[0001] The present invention relates generally to cloud computing and more specifically to monitoring, threat intelligence and managing security controls for cloud applications.

BACKGROUND OF THE INVENTION



[0002] The "cloud" has come to represent a conglomerate of remotely hosted computing solutions and the term "cloud computing" to refer to various aspects of distributed computing over a network. Various service models include infrastructure as a service (laaS), platform as a service (PaaS), software as a service (SaaS), and network as a service (NaaS). A "cloud" can also refer to the data store and client application of a single service provider. Cloud applications connect a user's device to remote services that provide an additional functionality or capability beyond what is available solely on the device itself. Cloud application providers such as Box.com and Dropbox synchronize a user's files across different devices and providing sharing and versioning capabilities. Other cloud services such as Office 365 and Docusign facilitate document creation and management. Still other cloud providers include Salesforce.com, Amazon Web Services, and others. The document US2013/0191921, 25th July 2013 (2013-07-25), discloses a local security component on a mobile device that may acquire data concerning a current configuration of the mobile device.

SUMMARY OF THE INVENTION



[0003] Systems and methods for cloud security monitoring and threat intelligence in accordance with embodiments of the invention are disclosed. In one embodiment, a cloud security system for monitoring and controlling the security of cloud application accounts includes memory containing an analytics application, a seeder application, and an analytics repository database, and a processor, where the processor is configured by the analytics application to generate a threat model using at least a first portion of stored activity data in the analytics repository database, and identify, based upon the threat model, a threat using a second portion of stored activity data in the analytics repository database, where the processor is also configured by the seeder application to select a security policy to implement in response to the identified threat, identify cloud security controls in at least one remotely hosted cloud application server system to modify in accordance with the selected security policy, establish a secure connection to the at least one remotely hosted cloud application server system using login credentials associated with a tenant account with the cloud application, and send instructions to the at least one remotely hosted cloud application server system to set the identified cloud security controls with respect to the tenant account in accordance with the selected security policy.

[0004] In a further embodiment, the memory also contains a data loader application and the processor is configured by the data loader application to establish a secure connection to one of the at least one remotely hosted cloud application server system using the login credentials associated with the tenant account with the cloud application, retrieve activity data associated with the tenant account from the remotely hosted cloud application server system, and store the retrieved activity data in the analytics repository database.

[0005] In another embodiment, the activity data is retrieved at predetermined intervals.

[0006] In a still further embodiment, the activity data includes information concerning login and logout statistics, IP addresses and devices used to access the cloud service.

[0007] In still another embodiment, the activity data includes values that are set for security controls associated with the tenant account.

[0008] In a yet further embodiment, the processor is also configured by the data loader application to normalize the retrieved activity data into a common format.

[0009] In yet another embodiment, the threat model models user behavior.

[0010] In a further embodiment again, the threat model correlates activities across a plurality of cloud applications using user profile information associating a particular user's accounts across the plurality of cloud applications and the user's accounts are associated with the tenant account at each of the cloud applications.

[0011] In another embodiment again, the user profile information associating a particular user's accounts across the plurality of cloud applications is retrieved from a user identity repository.

[0012] In another additional embodiment, the processor is also configured by the data loader application to determine whether a portion of the activity data matches predefined policy alerts.

[0013] In a still yet further embodiment, the processor is also configured by the analytics application to send an alert containing information concerning the identified alert and recommended remediation actions.

[0014] In still yet another embodiment, a recommended remediation action prescribes a task to be performed outside of the system and the result of the task is entered into the system.

[0015] In a still further embodiment again, a recommended remediation action is to disable a user's account.

[0016] In still another embodiment again, the memory also contains an incident remediation application, a recommended remediation action prescribes a task to be performed by the cloud security system, and the processor is also configured by the incident remediation application to perform the task and save the result of the task into memory.

[0017] In a still further additional embodiment, the processor is also configured by the seeder application to collect registration information from a tenant.

[0018] In still another additional embodiment, the registration information includes an authorization token secured by encryption.

[0019] In a yet further embodiment again, the identified cloud security controls include password requirements.

[0020] In yet another embodiment again, the memory also includes a cloud crawler application and the processor is also configured by the cloud crawler application to collect software defined security configuration data from the cloud service provider, where the software defined security configuration data includes information describing the configuration of security controls in the cloud application with respect to the tenant account.

[0021] In a yet further additional embodiment, the processor is also configured by the cloud crawler application to normalize the software defined security configuration data and enter the normalized data into an application catalog database.

[0022] In yet another additional embodiment, the processor being configured to generate a threat model using at least a first portion of stored activity data in the analytics repository database includes the processor being configured to generate a threat model using a machine learning algorithm over the first portion of stored activity data.

[0023] In a further additional embodiment again, a process for monitoring and remediation of security threats to cloud applications includes generating a threat model using at least a first portion of stored activity data in an analytics repository database using a cloud security system, identifying, based upon the threat model, a threat using a second portion of stored activity data in the analytics repository database using the cloud security system, selecting a security policy to implement in response to the identified threat using the cloud security system, identifying cloud security controls in at least one remotely hosted cloud application server system to modify in accordance with the selected security policy using the cloud security system, establishing, using the cloud security system, a secure connection to the at least one remotely hosted cloud application server system using login credentials associated with a tenant account with the cloud application, and sending instructions to the at least one remotely hosted cloud application server system to set the identified cloud security controls with respect to the tenant account in accordance with the selected security policy using the cloud security system.

[0024] Another additional embodiment again also includes establishing, using the cloud security system, a secure connection to a cloud application hosted by a cloud service provider using login credentials associated with a tenant account with the cloud application, retrieving, using the cloud security system, activity data associated with the tenant account, and storing the retrieved activity data in the analytics repository database using the cloud security system.

[0025] In a still yet further embodiment again, the activity data is retrieved at predetermined intervals.

[0026] In still yet another embodiment again, the activity data includes information concerning login and logout statistics, IP addresses and devices used to access the cloud service.

[0027] In a still yet further additional embodiment, the activity data includes values that are set for security controls associated with the tenant account.

[0028] Still yet another additional embodiment also includes normalizing the retrieved activity data into a common format using the cloud security system.

[0029] In a yet further additional embodiment again, the threat model models user behavior.

[0030] In yet another additional embodiment again, the threat model correlates activities across a plurality of cloud applications using user profile information associating a particular user's accounts across the plurality of cloud applications.

[0031] In a still yet further additional embodiment again, the user profile information associating a particular user's accounts across the plurality of cloud applications is retrieved from a user identity repository.

[0032] In still yet another additional embodiment again, the process also includes determining whether a portion of the activity data matches predefined policy alerts using the cloud security system.

[0033] In another further embodiment, the process also includes sending an alert containing information concerning the identified alert and recommended remediation actions.

[0034] In still another further embodiment, a recommended remediation action prescribes a task to be performed outside of the system and the result of the task is entered into the system.

[0035] In yet another further embodiment, a recommended remediation action is to disable a user's account.

[0036] In another further embodiment again, a recommended remediation action prescribes a task to be performed by the cloud security system, and the process also includes performing the task and saving the result of the task into memory using the cloud security system.

[0037] In a further embodiment, the process also includes collecting registration information from a tenant using the cloud security system.

[0038] In another embodiment, the registration information includes an authorization token secured by encryption.

[0039] In a still further embodiment, the identified cloud security controls include password requirements.

[0040] In still another embodiment, the process also includes collecting software defined security configuration data from the cloud service provider using the cloud security system, where the software defined security configuration data includes information describing the configuration of security controls in the cloud application with respect to the tenant account.

[0041] In a yet further embodiment, the process also includes normalizing the software defined security configuration data and enter the normalized data into an application catalog database using the cloud security system.

[0042] In yet another embodiment, generating a threat model using at least a first portion of stored activity data in the analytics repository database includes generating a threat model using a machine learning algorithm over the first portion of stored activity data.

[0043] In a further embodiment again, a process for monitoring and remediation of security threats to cloud applications includes collecting registration information from a tenant using a cloud security system, where the registration information includes an authorization token secured by encryption, establishing, using the cloud security system, a secure connection to a cloud application hosted by a cloud service provider using login credentials associated with a tenant account with the cloud application, collecting software defined security configuration data from the cloud service provider using the cloud security system, where the software defined security configuration data includes information describing the configuration of security controls in the cloud application with respect to the tenant account, retrieving, using the cloud security system, activity data associated with the tenant account, storing the retrieved activity data in an analytics repository database using the cloud security system, generating a threat model using at least a first portion of stored activity data in the analytics repository database using the cloud security system, identifying, based upon the threat model, a threat using a second portion of stored activity data in the analytics repository database using the cloud security system, sending an alert containing information concerning the identified alert and recommended remediation actions, selecting a security policy to implement in response to the identified threat using the cloud security system, identifying cloud security controls in at least one remotely hosted cloud application server system to modify in accordance with the selected security policy using the cloud security system, establishing, using the cloud security system, a secure connection to the at least one remotely hosted cloud application server system using login credentials associated with a tenant account with the cloud application, and sending instructions to the at least one remotely hosted cloud application server system to set the identified cloud security controls with respect to the tenant account in accordance with the selected security policy using the cloud security system.

BRIEF DESCRIPTION OF THE DRAWINGS



[0044] 

FIG. 1 is a system overview illustrating devices and cloud application service providers that can interact with a cloud security monitoring and control service in accordance with an embodiment of the invention.

FIG. 2 is a system overview illustrating a cloud security monitoring and control system in accordance with an embodiment of the invention.

FIG. 3 is a flow chart illustrating a process for retrieving software defined security configuration data from a cloud service in accordance with an embodiment of the invention.

FIG. 4 is a flow chart illustrating a process for collecting activity data from a cloud service in accordance with an embodiment of the invention.

FIG. 5 conceptually illustrates components of a threat intelligence platform for generating analytics in accordance with an embodiment of the invention.

FIG. 6 is a flow chart illustrating a process for remediating a threat in accordance with an embodiment of the invention.

FIG. 7 is a flow chart illustrating a process for provisioning a cloud service to specific security controls in accordance with embodiments of the invention.

FIG. 8A is a user interface screen illustrating a tenant dashboard view of a controls management platform user interface in accordance with embodiments of the invention.

FIG. 8B is a user interface screen illustrating a list of risk events across different cloud applications in accordance with embodiments of the invention.

FIG. 8C is a user interface screen displaying a graphical chart of events in accordance with embodiments of the invention.

FIG. 8D is a user interface showing various summary views of risk events in accordance with embodiments of the invention.

FIG. 8E is a user interface screen showing security controls for a tenant's account with a cloud application and the assignment of security control values at a security level in accordance with embodiments of the invention.


DETAILED DISCLOSURE OF THE INVENTION



[0045] Turning now to the drawings, systems and methods for cloud security monitoring and control are illustrated. Tenants are organizations whose members include users of cloud services offered by cloud providers. Users may have individual accounts with cloud providers and tenants may have enterprise accounts with cloud providers that encompass or aggregate a number of individual user accounts. In many embodiments of the invention, a cloud security provider maintains a cloud security monitoring and control system that enables tenants to view information about security controls in the various clouds that they use, review analytics reports, and configure security controls by a pre-set classification level of security. In several embodiments, the cloud security monitoring and control system analyzes information about user activity in one or more clouds using machine learning and other algorithms to perform threat detection and to provide recommendations concerning appropriate responses to different categories of threat. The analytics can include determining models of normal and/or abnormal behavior in user activity and detecting patterns of suspicious activity in one cloud or across multiple clouds. Some patterns may involve detecting the same action or different actions in multiple clouds that are associated with the same user account or IP address. Analytics may also include providing an alert and recommending remedial measures in the cloud(s) in which suspicious activity is detected and/or remedial measures to be taken in clouds other than those showing suspicious activity. Systems and methods for collecting and analyzing information from cloud services are discussed below.

System Architecture



[0046] A system for cloud security monitoring and control in accordance with embodiments of the invention includes multiple components that may be located on a single hardware platform or on multiple hardware platforms that are in communication with each other. Components can include software applications and/or modules that configure a server or other computing device to perform processes for cloud discovery and management as will be discussed further below.

[0047] A system including a cloud security monitoring and control system 102, client devices 106 that can be used to access the cloud security system 102, and cloud services 110 to be monitored in accordance with embodiments of the invention is illustrated in Fig. 1. The system 100 includes a number of different types of client devices 106 that each has the capability to communicate over a network. The client devices 106 communicate with the cloud security monitoring and control service 102 and present a user interface for interacting with the service. The cloud security and control system 102 can communicate with cloud application services 110 to retrieve security configurations, application data, and other information and set security controls as will be discussed further below.

[0048] In many embodiments of the invention, a system for cloud security includes cloud management applications executing on a hardware platform, user interface components, and data warehouses stored on a hardware platform. A system for cloud security in accordance with embodiments of the invention is illustrated in FIG. 2. Cloud management applications in the system 200 can include a cloud crawler 202, a cloud seeder 204, and a data loader 206. As will be discussed in greater detail further below, a cloud crawler application 202 can retrieve information about security controls from cloud providers, a cloud seeder application 204 can modify the security controls of a tenant account with a cloud provider to reflect a desired security posture, and a data loader application 206 can retrieve activity information on a tenant's account with a cloud provider and generates analytics.

[0049] In several embodiments, data retrieved by the cloud crawler application 202 is entered into an application catalog database 208 and data retrieved by the data loader application 206 is entered into a landing repository 210 and/or analytics and threat intelligence repository database 211. The data entered into a landing repository 210 may be in different formats and/or have different ranges of values - this data may be reformatted and/or structured before being moved to the analytics repository 211. The data concerning activity information in the analytics repository 211 can be utilized to generate reports that may be presented visually to a system administrator via a user interface and to generate analytics for determining threat level, detecting specific threats, and predicting potential threats.

[0050] The aggregation of activity information in the analytics repository 211 concerning access patterns and other event statistics enables the system to establish baselines of user behavior. Machine learning techniques can then be applied to detect threats and provide recommendations concerning how to respond to threats. Threat models can be developed to detect threats that are known or unknown or emerging. Threats can also be identified by comparing activity data with external threat intelligence information, such as information provided by third-party providers, as will be discussed further below.

[0051] The accounts of a particular user in different cloud applications (e.g., different user identities) can be associated together in a user identity repository 209. The user identity repository 209 and/or other memory in the cloud security system can store information concerning tenant accounts and user accounts associated with each tenant account. A user belonging to a tenant organization may have user accounts with various cloud applications. The tenant organization may also have a tenant account with the cloud applications that exercises management authority over the user accounts of users belonging to the organization. The user accounts of a user are typically associated with the tenant account of the tenant to which the user belongs. The association of user accounts to tenant accounts may be used in various ways in accordance with embodiments of the invention including retrieving information about the user activity of users associated with a tenant. As will be discussed further below, a tenant account's credentials may be used to log into cloud application services to retrieve activity data concerning user accounts that are associated with the tenant account.

[0052] As will be discussed in greater detail below, the user identity repository 209 can also be utilized to facilitate user tracking and profile across multiple cloud applications. In addition, collecting information about user behavior across multiple cloud services enables the system to, when a threat is detected based upon behavior on one or more cloud services, preemptively alert a system administrator with respect to threats on other cloud services and/or proactively secure other services on which a user maintains data by applying remedial measures, such as adding additional steps to authentication, changing passwords, blocking a particular IP address or addresses, blocking email messages or senders, or locking accounts.

[0053] In several embodiments of the invention, the system 200 includes applications or software modules to perform analytics on collected data as will be discussed in greater detail further below. The applications or software modules may be stored in volatile or non-volatile memory and, when executed, configure the processor 201 to perform certain functions or processes. These applications can include a threat detection and prediction analytics application 212 and/or descriptive analytics application 213. The threat detection and prediction analytics application 212 can generate analytics using machine learning and other algorithms to identify and predict security threats from patterns of activity and behavioral models. The descriptive analytics application 213 can generate analytics such as, but not limited to, statistics on users, user activity, and resources. Analytics may be performed using data stored in the analytics and threat intelligence repository 211.

[0054] As will be discussed further below, embodiments of the invention may include remediation functions that provide manual and/or automated processes in response to threats. In some embodiments, analytics can utilize information received from tenant systems that describes threat intelligence provided by the tenant. These sources, that can be referred to as customer base lines 217, can include information such as, but not limited to, specific IP addresses to watch or block, email addresses to watch or block, vulnerable browsers or versions thereof, and vulnerable mobile devices or versions of mobile hardware or software. In additional embodiments, analytics can utilize information received from external third party feeds 218, 220, and 221 to augment the threat intelligence by providing external information of security threats such as, but not limited to, identification of infected node points, malicious activity from a particular source IP address, malware infected email messages, vulnerable web browser versions, and known attacks on clouds.

[0055] The incident remediation application 213 can be utilized to coordinate and/or perform remediation actions in response to detected threats. It may be called when a recommended remediation action is presented and selected in an alert. The incident remediation application 213 may perform the selected remediation action or instruct another application, such as a cloud seeder application 204 to perform the selected remediation action. When the selected remediation action is to be manually performed or is external to the cloud security system, the incident remediation application 213 may track the status of the remediation action and whether it is complete. The incident remediation application can be used to save the results of a manual or automated remediation action into memory. In several embodiments, a selected remediation action is to be performed by a system external to the cloud security system, such as by a third-party's or a tenant's incident remediation system. In such cases, the incident remediation application 213 may instruct or invoke the third-party's or tenant's incident remediation system to perform the action using an automated integration process.

[0056] The cloud seeder application 204 can be utilized to implement security policies by setting security controls within a tenant's accounts in various cloud applications. As will be discussed in greater detail further below, a cloud seeder may set security controls in various conditions such as, but not limited to, part of remediation of a threat or on call by a system user.

[0057] In further embodiments of the invention, user interface components include an administration console 214 that provides controls management for a user to set the security controls for one or more clouds and an analytics visualization console 216 for viewing analytics generated by the system. As will be discussed in greater detail further below, the data in the data warehouses can be used to generate the information and reports shown in the user interface. The use of cloud management applications to retrieve security configuration data from cloud applications is discussed below.

Cloud Crawler



[0058] In many embodiments of the invention, a cloud crawler application retrieves software defined security configuration data from cloud services. Software defined security configuration data describes the configuration of security controls in a particular cloud service. Security controls are mechanisms that restrict access to the application and data housed by the cloud. Software defined security configuration data can include data describing: roles that are defined for users, groups and grouping of users, encryption keys, tokens, access controls, permissions, configurations, type of authentication policy, mobile access policy, and many other types of security controls. A process for retrieving software defined security configuration data from cloud services is illustrated in FIG. 3.

[0059] The process includes connecting (302) to the cloud. The cloud may require authorization or some other manifestation of consent for access to the system and internal data. Authorization may be provided by a token (such as using the OAuth open standard for authorization) or by credentials (such as a user name and password). One skilled in the art will recognize that there are various other techniques that can be utilized in authorizing access to a cloud provider's system and data. The connection may also include providing a service URL (universal resource locator).

[0060] The process further includes collecting (304) software defined security configuration data about the cloud application's security controls. The software defined security configuration data can be collected by utilizing an API (application programming interface) made available by the cloud application. API's and classes of API's that may be utilized in accordance with embodiments may include REST (Representational State Transfer), J2EE (Java 2 Platform, Enterprise Edition), SOAP (Simple Object Access Protocol), and native programmatic methods (such as native application API's for Java). The information could also be requested using other techniques including scripting languages (such as Python and PHP), deployment descriptors, log files, database connectivity through JDBC (Java Database Connectivity) or REST, and resident applications (cloud beacons) as will be discussed further below. The information that is sent or received can be represented in a variety of formats including, but not limited to, JSON (JavaScript Object Notation), XML (Extensible Markup Language), and CSV

[0061] (Comma Separated Values). One skilled in the art will recognize that any of a variety of formats may be utilized in accordance with embodiments of the invention as suitable to a specific application. Table 1 below provides a partial list of security controls and the access that is supported by the cloud applications Box and Amazon Web Services. Table 2 provides a partial list of security controls and supported access for Salesforce.com.
TABLE 1
Security ControlsSupport in BoxSupport in Amazon Web Services (AWS)
Users/Group Management REST (Representational State Transfer) API AWS IAM (Identity and Access Management) APIs
Credentials and Identifiers N/A Secure and monitor Accounts, tokens, keys etc
Login/Logout Events REST API AWS CloudTrail - Events API and Log files
IP address of the clients REST API AWS CloudTrail - Events API and Log files
Device (iphone, ipad etc) used by the clients REST API AWS CloudTrail - Events API and Log files
Password Policies REST API AWS IAM policies
Resource Access Permissions Resources: Files, Folders Actions: Editing, Preview, upload, collaboration events Resources: EC2, S3, EBS Actions: Create, Access, Restart, Terminate, etc. IP address based access controls
Restrict or limit Mobile access Limit users from saving content for offline access AWS IAM policies
Roles BOX has pre-defined admin roles Roles can be created using pre-defined policies
TABLE 2
Security ControlsSupport in Salesforce.com 
Users/Group Management SalesForce User/Group/Profiles APIs  
Credentials and Identifiers APIs: Setup changes  
Login/Logout Events APIs: Audit activity  
IP address of the clients APIs: Audit activity  
Device (iphone, ipad etc) used by the clients API to manage Setup changes  
Password Policies APIs: Setup changes  
Resource Access Permissions Salesforce object monitoring using object history  
Restrict or limit Mobile access APIs to manage Setup changes  
Roles Salesforce Profiles  


[0062] The software defined security configuration data received about a cloud application's security controls can be used to generate (306) security controls metadata, that is, normalized descriptors for entering the information into a common database. The security controls metadata is categorized (308) (mapped into categories) and indexed. The categorization may comply with a standard specified by a security organization and/or may be certified and/or audited by a third party. In addition, security controls metadata and/or the categorization of metadata may be formulated around the requirements of a particular regulation or standard. For example, regulations and standards such as the Health Insurance Portability and Accountability Act (HIPAA), Sarbanes-Oxley Act, FedRAMP, and Payment Card Industry Data Security Standard (PCI DSS) may require reporting and audit trails. Security controls metadata can be formatted in a way to display the types of information required by the regulations and standards and facilitate the generation of reports needed.

[0063] The security controls metadata is entered (310) into an application catalog database. In many embodiments of the invention, the application catalog database is a Cassandra database. In other embodiments, the application catalog database is implemented in other types of databases appropriate to the application. One of ordinary skill in the art will recognize that any of a variety of databases can be used to store an application catalog in accordance with embodiments of the invention for later retrieval, report generation, and analytics generation as will be discussed further below.

[0064] A specific process for discovering and storing security controls metadata in accordance with an embodiment of the invention is discussed above. Any of a variety of processes for retrieving software defined security configuration data and generating security controls metadata can be utilized in accordance with embodiments of the invention. One skilled in the art will recognize that the number and types of controls and the mechanisms for retrieving software defined security configuration data may vary in different embodiments of the invention as supported by different cloud applications. For example, other cloud applications such as Office 365, GitHub, Workday, and various Google apps may be supported using retrieval mechanisms specific to the application. Furthermore, processes for retrieving software defined security configuration data can be automated or manual based on target cloud provider support.

Controls Management



[0065] In many embodiments of the invention, a controls management platform provides a user with a normalized view of controls for multiple clouds. The platform can include a user interface that displays a simplified view of controls for different clouds on the same screen. Information provided to the controls management platform can be retrieved from an application catalog database using metadata based schema mapping. The platform can be used to assign consistent access policies across clouds. Controls can be displayed and/or set according to specified classifiers, such as, but not limited to: standard, stringent, custom. A higher level classification corresponds to more stringent controls. In several embodiments, classification and/or designation of security controls complies with criteria specified by organizations such as the National Institute of Standards and Technology (NIST), International Organization for Standardization (ISO), and/or Payment Card Industry Data Security Standard (PCI DSS) and/or a specific certification offered by one such organization. In several embodiments of the invention, the controls management platform can also provide for plug-in interfaces to integrate with SaaS, PaaS, and native applications.

[0066] A controls management platform user interface may display key security indicators in a library format with risk factors that are color coded (such as red, green, yellow). Other statistics or metrics may be displayed such as, but not limited to, user logins attempts, groups with most added users, most deleted files, users with the most deleted files, and users downloading the most files. Some types of information may be specific to a particular cloud application provider, such as Salesforce.com showing who is downloading opportunity/budget data, contracts, or contacts. In several embodiments of the invention, a user interface provides a unified view of security controls for a tenant's registered cloud applications. The user interface may display values set for any or all security controls set for different cloud applications, as well as deviations of the current values from values associated with predetermined policies or configurations. A security policy may include predetermined desirable or recommended values for security controls as will be discussed further below. A user interface may also display events and alerts concerning detected security threats and risks and tools to address them as will be discussed further below. A user interface can provide control over setting security controls values, such as by pushing a security policy using a cloud seeder as will be discussed further below. A tenant's dashboard view of a controls management platform user interface in accordance with embodiments of the invention is illustrated in Fig. 8A. The dashboard view can display high-level information such as a map of IP addresses of user accounts associated with the tenant's account that have accessed cloud applications, number of risk alerts and predicted threats, number of inactive and active users, number of open and closed incidents, etc. The collection of activity data from cloud application providers is described next.

Cloud Data Loader



[0067] In many embodiments of the invention, a cloud data loader application configures a computing device to collect activity data from a cloud service about a tenant's user activity, security configuration, and other related pieces of information. A process for collecting activity data from a cloud service in accordance with embodiments of the invention is illustrated in FIG. 4.

[0068] The process includes connecting (402) to one or more clouds and collecting (404) activity data from the clouds. In many embodiments, the connection is made over an encrypted communication channel. In further embodiments, the connection must be authenticated by a token or using login credentials as in the connection made with a cloud crawler application discussed further above. In several embodiments of the invention, the collection is scheduled to occur periodically (e.g., every 4 hours or every 6 hours). In many embodiments, the schedule for collection is configurable by the tenant. In further embodiments, data is collected and retrieved in real time as events occur utilizing a real-time computation system such as, for example, Storm. The system may be configured to designate certain events or activity as high risk events for retrieval near real-time outside scheduled retrieval.

[0069] Activity data can include various types of information made accessible by a remotely hosted cloud application system to a system external to the cloud application system when the external system holds the proper credentials, which may be issued by the cloud application system or another authorizing entity. Activity data associated with user accounts can include information relating to the use of and/or actions taken with a user account at a cloud application. Activity data can include sources of information such as a user log(s) or audit trail(s). More specific types of activity data can include, but are not limited to, login and logout statistics (including attempts and successes), IP addresses used to access the application, devices used to access the application, and cloud resources that were accessed (including, but not limited to, files and folders in a file management cloud application [such as Box], employees and contractors in a human resource cloud application [such as Workday], and contacts and accounts in a customer relationship management cloud application [such as Salesforce]). Activity data can include the user account or other user identifier for the user associated with the events or statistics. Activity data can include information about system status or activity of a cloud application system such as, but not limited to, server activity, server reboots, security keys used by a server, and system credentials, where this information is visible or accessible to a system using authorized credentials.

[0070] Activity data may also include information about the security configuration of a tenant (and associated users) account. Security configuration can include the values to which security controls (discussed further above) for a tenant (and/or associated users) are set.

[0071] In some embodiments, certain events are considered high risk and activity data related to such events are retrieved near real-time outside of a scheduled interval.

[0072] The retrieved activity data is stored (406) in an analytics and threat intelligence repository database 211. The analytics and threat intelligence repository database 211 may be any database or data repository with query capability. In several embodiments of the invention, the analytics and threat intelligence repository database 211 is built in a NoSQL based infrastructure such as Cassandra or other distributed data processing system, although any data warehouse infrastructure may be utilized as appropriate for the application. In some embodiments, the data is first entered into a landing repository 210 and reformatted and/or structured before being moved to an analytics repository 211.

[0073] In some embodiments of the invention, the data may be received in different formats that are utilized by different cloud applications. For example, the data may be formatted in JSON (JavaScript Object Notation) or other data interchange formats, or may be available as log files or database entries. In further embodiments, the process includes normalizing (408) the data and reformatting the data into a common format for storage in and retrieval from the analytics and threat intelligence repository database 211. Reformatting the data may include categorizing and structuring the data into the common format. In several embodiments of the invention, the database is adaptive to structural changes and new values by running automated processes to check for changed data. In some embodiments, a cloud crawler application (as discussed further above) recognizes differences in the structure or values of the data retrieved and the changes are implemented in the application catalog database 208 and/or analytics and threat intelligence repository database 211. System reports may be pre-generated (410) by jobs that are scheduled to run on the data set. Specific processes for utilizing a cloud loader application to collect activity data are discussed above. Any of a variety of processes can be used for collecting activity data in accordance with embodiments of the invention. Reports that can be pre-generated or generated on demand by a system user or administrator in accordance with embodiments of the invention are discussed below.

Reports



[0074] Data stored in an application catalog database and/or analytics and threat intelligence repository database 211 can be used to generate a variety of reports. Categories of reports can include: authentication and authorization, network and device, systems and change data, resource access and availability, malware activity, and failures and critical errors. Reports can be based on various attributes such as, but not limited to, per application, per user, per secured resource, and per device used for access. Reports may highlight recent changes such as updated features in a cloud application or newly modified policies. Reports may be pre-generated by scheduled jobs (e.g., for performance reasons) or may be requested by a user or administrator.

[0075] In various embodiments of the invention, reports include analytics generated on the data. Analytics may utilize Apache Software Foundation technologies such as Hadoop, Hive, Spark, and Mahout or other features as available in the data storage framework used. Several embodiments utilize the R programming language to generate analytics. In further embodiments, the generation of analytics includes the use of machine learning algorithms, proprietary algorithms, and/or external threat intelligence from external commercial sources such as FireEye and Norse or public threat intelligence communities such as Zeus and Tor. Techniques for generating analytics in accordance with embodiments of the invention are discussed below.

Analytics and Security Intelligence



[0076] A cloud security monitoring and control system in accordance with embodiments of the invention can generate analytics using collected data. Analytics may be generated by an analytics process and/or an analytics module referred to as an analytics engine. An overview of generating analytics using components of a threat intelligence platform in accordance with embodiments of the invention is illustrated in Fig. 5.

[0077] One class of analytics that may be generated is descriptive or statistical analytics. Statistical data can be generated using a pre-defined set of system queries, such as, but not limited to, MapReduce jobs and Spark and Apache Hive queries. Descriptive analytics can be generated either for a single application or across multiple applications using correlation techniques. Examples of reports that can be generated include, but are not limited to, login statistics (e.g., users with the most failed logins, IP address based login history including consideration of IP reputation, geolocation, and other factors), user statistics (e.g., users with the most resources [files, EC2 machines, etc.], entitlements across clouds, number of changed passwords), activity statistics (e.g., activity of a user across clouds), statistics on key rotation (e.g., whether SSH keys have been rotated within the last 30 days), and resource statistics (e.g., number of folders, files downloaded by users, files downloaded by roaming or mobile users). Trends may be identified, such as login activity within a certain time period, password related support issues based on past history of such issues, or identifying types of mobile devices which see the most activity within a certain time period. Data in a report can be displayed on a user interface as an event viewer showing a "wall" of events along with actions that a user can take in response to or to remediate an event. Alerts can be constructed based on pre-defined rules that can include specific events and thresholds.

[0078] Another class of analytics that can be generated is predictive and heuristic analytics. These may incorporate machine learning algorithms to generate threat models, such as, but not limited to, deviations from base line expectations, rare and infrequent events, and behavior analytics to derive suspicious behavior of a user. Algorithms and profiles can be trained to intelligently predict whether an unusual behavior is a security risk. Third party feeds from providers such as, but not limited to, MaxMind, FireEye, Qualys, Mandiant, AlienVault, and Norse STIX can be integrated to augment the threat intelligence by providing external information of and relating to potential security threats such as, but not limited to, IP (Internet Protocol) address reputation, malware, identification of infected node points, vulnerable web browser versions, use of proxy or VPN server by a user, and known attacks on clouds. In several embodiments, threat information is expressed in the Structured Threat Information eXpression (STIX) data format. For example, one or more services may contribute information concerning a particular IP address, such as a reputation (e.g., known for having software vulnerabilities, a host of malicious software, or source of attacks) and/or a geographic location associated with the IP address. This information can be combined with retrieved activity data involving the IP address, such as what time logins were attempted from that IP address, and information derived from activity data, such as how far apart the logins attempts were. These factors can be used to determine a "login velocity" metric. Metrics can be determined for other activities such as file access, sales transactions, or instances of virtual machines.

[0079] In many embodiments of the invention, various types of algorithms can be particularly useful for analyzing the data. Decision tree, time series, naive Bayes analysis, and techniques used to build user behavior profiles are examples of machine learning techniques that can be utilized to generate predictions based on patterns of suspicious activity and/or external data feeds. Techniques such as clustering can be used to detect outliers and anomalous activity. For example, a threat can be identified based on an account accessing one or more files or failing a series of login attempts from an IP address that is flagged (by a third party feed or otherwise) as malicious. In a similar way, a threat can also be based on different patterns of activity in one cloud or across multiple clouds over a series of time. As discussed further above, activity data from different clouds may be in different formats or with different possible values or ranges of values. Normalizing the data in the processes discussed above may include reformatting the data such that it is comparable, have the same meaning, and/or bear the same significance and relevance between different clouds. Thus, algorithms can aggregate and compare data from different clouds in meaningful ways. For example, a series of failed logins with a particular user account in one cloud may be deemed not to be a threat. However, a series of failed logins with user accounts associated with a user across multiple clouds may indicate a concerted effort to crack the user's password and therefore set off an alarm. Clustering and regression algorithms can be used to categorize data and find common patterns. For example, a clustering algorithm can put data into clusters by aggregating all entries of users logging in from a mobile device. Predictive analytics can also include identifying threats based on activity such as a user not accessing a particular cloud application in several months and then showing high activity in the next month or a user downloading one file every week for the past several weeks, demonstrating a potential advanced persistent threat (APT) scenario. In several embodiments of the invention, data collected over time is used to build models of normal behavior (e.g., patterns of events and activity) and flag behavior that deviates from normal as abnormal behavior. After one or more flagged event or activity is characterized as a true or false positive (e.g., by user feedback), the information can be provided back to one or more machine learning algorithms to automatically modify parameters of the system. Thus, machine learning algorithms can be utilized in at least the ways discussed above to make recommendations and reduce false alarms (false positives). Activity data collected from various parameters over period of time can be used with machine learning algorithms to generate patterns referred to as user behavior profiles. The activity data can include contextual information such as IP address and geographic location.

[0080] Algorithms for association rule learning can be used to generate recommendations. In several embodiments of the invention, profile linking algorithms are used to link activities across multiple cloud applications by finding cross application correlation. A single user can be identified across multiple clouds using one or more attributes or identification factors, such as a primary user identifier (ID) that is commonly used across the clouds or a single sign-on (SSO) authentication mechanism (e.g., Active Directory, Okta). Correlation of activities across applications can include finding users with a first entitlement in a first cloud application that have a second entitlement in a second cloud application, users logged into two cloud applications simultaneously from different IP addresses, users who have several failed login attempts and then change their password, and common users with numerous failed logins in two cloud applications.

[0081] In many embodiments of the invention, a user identity repository 109 can be utilized to facilitate user tracking and profile across multiple cloud applications. A particular user's accounts in different cloud applications may be linked by associating together the user identifier associated with the accounts (e.g., jdoe, john.doe, etc.), by a primary (universal) user identifier or SSO mechanism as mentioned above, or other method. A user identity repository 109 can contain information relating together the accounts of each user associated with a tenant. A user who utilizes multiple cloud application accounts that under the control or ownership of a tenant may be referred to as an "enterprise user."

[0082] In several embodiments of the invention, a recommendation engine tracks user activity for anomalous behavior to detect attacks and unknown threats. The recommendation engine can track user activity across multiple clouds for suspicious events. Events can include pre-defined at-risk operations (e.g., downloading a file containing credit card numbers, copying encryption keys, elevating privileges of a normal user). An alarm can be sounded with details of the event and recommendations for remediation.

[0083] Dynamic policy based alerts can be generated for events pertaining to a specific user/employee. A process can monitor activity data associated with the specific user and generate a customized alert for specific actions taken by the user.

[0084] In many embodiments of the invention, an algorithm is designed to simulate normal user activities using user activity data in the analytics and threat intelligence repository database 211. The simulation can be used to train other machine learning algorithms to learn normal behavior of a user in the system. In general, a particular security issue may not always repeat, and hence may not be detected by a purely supervised algorithm. However, techniques such as outlier detection establish a baseline that is useful for detecting anomalous activities. Such anomalous activities along with contextual threat intelligence can provide more accurate prediction of threats with low prediction errors.

[0085] In further embodiments of the invention, analytics can be used to detect security controls drift, which can refer to the changing of one or more security controls in a seemingly arbitrary manner that can increase security risks. A risk event can be generated in response to the change of one or more security controls in one or more cloud applications and actionable intelligence associated with the risk event. As with other types of events, an alert may be sent to a tenant, tenant system, or other monitoring entity. For example, a tenant's password policy in a cloud application may have been changed to impose fewer requirements (e.g., type and/or number of characters). This may generate a risk event and alert to recommend that the password policy be changed back to the original password policy.

[0086] Alerts concerning any of the events discussed above can be shown on a user interface such as a controls management platform discussed further above. An alert can include information about the detected event such as, but not limited to, an event identifier, date, time, risk level, event category, user account and/or security controls associated with the event, cloud application associated with the event, description of the event, remediation type (e.g., manual or automatic), and/or event status (e.g., open, closed). A user interface showing a list of risk events across different cloud applications associated with a tenant's account in accordance with embodiments of the invention is illustrated in Fig. 8B. Information to be displayed about each risk event can include an identifier (ID), affected cloud application and instance, category, priority, date and time, description, recommended remediation type, and status. Each risk event may also have a user-selectable action, such as editing, deleting, marking status complete, and/or performing a remediation action. Selection of a remediation action may invoke an application such as the incident remediation application 213 and/or cloud seeder application 204 to perform the selected remediation.

[0087] Counts of events in different event categories over time can be graphically illustrated in a chart. A user interface displaying a chart of events in accordance with embodiments of the invention is illustrated in Fig. 8C. The chart displays a count of events by date in each of the color coded categories such as activities at an unusual time, after-hours downloads, failed logins, etc. The visual representation (e.g., a line) of an event category can be toggled on and off.

[0088] Threats can also be displayed in a summary view. A user interface showing various summary views of risk events in accordance with embodiments of the invention is shown in Fig. 8D. One window lists risk events showing information similar to the view illustrated in Fig. 8B. A second window shows Key Security Indicators as users with a high count of certain risk events, such as failed login attempts, failed change password attempts, etc.

[0089] Specific processes for retrieving and analyzing activity data in accordance with an embodiment of the invention are discussed above. Any of a variety of processes for retrieving and analyzing activity may be utilized in accordance with embodiments of the invention. Processes for the remediation of identified threats are discussed below.

Remediation



[0090] Identified threats can be addressed by a variety of techniques in accordance with embodiments of the invention. Remediation of threats may be automated or manual, soliciting user or administrator involvement. A process for remediating threats in accordance with embodiments of the invention is illustrated in Fig. 6.

[0091] The process includes identifying (602) a threat. Threats may be identified using processes such as the analytics and security intelligence processes discussed further above. Threats can include activity, events, or security controls that are abnormal or noncompliant. An alert is presented (604) regarding the identified threat. In many embodiments of the invention, an alert may be visual and may appear in a user console such as a controls management platform discussed further above. In several embodiments, an alert is communicated over a network such as by email, short message service (SMS) or text messaging, or web-based user console. Alerts may be communicated as secure messages (e.g., over a secure communication channel or requiring a key or login credentials to view). An alert may contain information concerning recommended or available remediation action(s), such as implementing stronger security controls, and request a selection of which remediation action(s) to pursue.

[0092] In many embodiments, a system for cloud security can interface with third party incident management automation systems such as, but not limited to, ServiceNow and IBM QRadar. External systems may support an API (application programming interface) for interaction. An alert and/or other information concerning an identified threat can be sent to an entity external to the cloud security system such as a tenant's internal IT (information technology) workflow management system or third party incident management automation system for remediation and/or tracking. The external system may return a status (e.g., complete or not complete) to the cloud security system. In this way, remediation may be delegated to an external system with the results reported back to the cloud security system to "close the loop." For example, if a password reset is desired for a user account, the cloud security system can send an alert or message to a tenant's internal IT system managing the user account. An administrator or system may complete the password reset operation and report the status as completed back to the cloud security system. Remediation action(s) to address a threat may be performed automatically, if a response to such threats is predetermined, or may be instructed (606) by a user selecting a remediation option from the alert that was presented.

[0093] The selected remediation action(s) are performed (608). Any of a variety of security measures may be taken to address an identified threat such as, but not limited to, deactivating an account, resetting a password, or setting stronger security controls. In many embodiments, the cloud security system performs remedial actions by carrying out recommended measures directly and automatically with use of any agent or proxy.

[0094] In some embodiments, remedies may be performed "offline" or outside of visibility of the cloud security monitoring and control system. For example, an alert notifies an administrator, who then makes changes to an external system in which the monitoring and control system does not have visibility. In such cases, an actionable incident can be opened in the monitoring and control system as an open item that can be later set to closed when the changes are completed. Remediation may also include utilizing an incident remediation application 213 to coordinate and/or perform remediation actions and/or a cloud seeder application 204 or process to set security controls as discussed further below.

[0095] Specific processes for identification and remediation are discussed above. Any of a variety of processes for identifying and remediating threats can be utilized in accordance with embodiments of the invention. Remediation may include setting the security controls of a tenant's cloud application account. Provisioning a cloud application account with designated security controls is discussed below.

Cloud Seeder



[0096] In many embodiments of the invention, a cloud seeder application configures a computing device to provision a cloud application for a tenant with the tenant's desired security posture or security policy. The security posture/policy may include setting security controls to particular values that are associated with a particular level of security. The security posture/policy may be implemented with respect to controls that are specific to one user, or controls that apply to a group of users or all users. The seeder application may be used to coordinate consistent access policies across clouds. In several embodiments, security controls are coordinated across several accounts that a tenant has among different cloud providers. For example, different levels of security may be defined such that when a higher or lower level of security is selected, the security controls for a tenant's accounts with different cloud services are all set to reflect a higher or lower level of security. In this way, a unified policy and security controls configuration can be enforced. The values for various security controls at different levels of security can be defined by input on a user interface such as a controls management platform discussed further above and the values associated with the security controls at each level of security stored in a database. A user interface showing security controls for a tenant's account with a cloud application and the assignment of security control values at a security level in accordance with embodiments of the invention is illustrated in Fig. 8E. In the illustrated embodiment, security controls at a Stringent level of security include password requirements for a user account such as ten minimum characters, two numbers, one special character, one uppercase letter, no reuse of the last ten passwords, etc.

[0097] A cloud seeder process can be invoked by various applications or by various processes including, but not limited to, a scheduler, incident management system, and/or upon application registration. For example, a cloud seeder process may be initiated by a tenant request, in response to a detected threat, or upon a predetermined schedule. A process for provisioning a cloud application in accordance with embodiments of the invention is illustrated in Fig. 7.

[0098] In several embodiments, the process includes collecting (702) registration information from a tenant when registration information has not been previously obtained. Registration information includes authorization to connect to a cloud provider using a tenant's account. Authorization may be provided by a token (such as using the OAuth open standard for authorization) or by credentials (such as a user name and password). In some embodiments, the authorization (via token, credentials, or otherwise) is only provided with respect to the minimum permissions or privileges necessary to configure the relevant security controls. For example, permissions may be granted only to edit user accounts associated with a particular tenant's account and not to access other portions of the cloud service.

[0099] In several embodiments, authorization to modify a tenant's account is embodied by a secure token or credentials provided by the tenant. The secure token or credentials are encrypted at rest using encryption keys per any of a variety of encryption standards and stored in a hardware security module (HSM) with access strictly audited. Access to the HSM and encryption keys are regulated by secure software and only trusted code has access to encrypted keys. Transport level access also involves secure communication and any of a variety of encryption techniques. One skilled in the art will recognize that there are various other techniques that can be utilized in authorizing access to a cloud provider's system and data and securing registration information.

[0100] The process includes receiving (704) the designation of a security policy. A security policy may be selected or chosen in any of a variety of ways in accordance with embodiments of the invention. Selection may be made by a user from a user interface or automatically by a threat or incident management process in response to a detected threat. A security policy may associate a desired level of security that includes a number of security features with the security controls available in a cloud application to implement that desired level of security. The associations may be stored in a database or other repository and retrieved when the security policy is selected.

[0101] The process includes identifying (706) security controls pertinent to the designated security policy. Available security controls may be discovered via processes such as with a cloud crawler application and/or read from an application catalog database as discussed further above. For example, setting a security policy concerning password strength may involve the security controls for password requirements with each cloud application (e.g., number and type of characters).

[0102] Using the registration information, the process includes connecting (708) to the cloud provider. The process includes reading the security controls associated with the tenant's account and setting (710) the security controls to the desired configuration. For example, a policy concerning password strength may set security controls governing the number and type of characters required in a password to require at least eight characters using symbols, numbers, and upper and lower case characters.

[0103] The processes described above in accordance with embodiments of the invention can be utilized to implement any number of security policies/postures at different levels of security. For example, a security policy at a high level of security may require that user passwords be "strong," e.g., include a variety of characters such as upper and lower case, numbers, and/or symbols. Similarly, security policies at different levels of security may set a session inactivity timer at higher or lower periods of time, e.g., "time out" or automatically log out a user's session. A process to enact a security policy in accordance with embodiments of the invention can identify the relevant security controls in the tenant's accounts with cloud applications to modify and set the controls at the desired values. In several embodiments, software defined security configuration data and/or security controls metadata, discussed further above, can be utilized to identify the relevant security controls.

[0104] Specific processes for setting security controls of a cloud application by a security policy are discussed above. Any of a number of processes for setting security controls of a cloud application may be utilized in accordance with embodiments of the invention.

Cloud Beacon



[0105] As discussed further above, several techniques can be utilized to remotely retrieve event data from a cloud provider. In further embodiments of the invention, a cloud beacon is embedded in a cloud to monitor activity and capture application activity in real-time. In several embodiments, a cloud beacon can be a Java agent configured and co-located in the running application. In other embodiments, a cloud beacon is a Python program. One skilled in the art will recognize that a cloud beacon can be implemented in any language suitable for the computing environment. The cloud beacon can capture events and activity for one or more tenants utilizing the services of the cloud application. Data captured can include user logins, tokens, session attributes, user roles, groups, data filtering, SQL queries, etc. as well as contextual threat intelligence information such as an IP address reputation, user's geographic location, etc. A cloud beacon can be configured to monitor designated top security vulnerabilities ad security configuration controls as well as capture user activity audit log files for detecting abnormal activities. The collected data can be entered into an analytics and threat intelligence repository database utilizing processes similar to those utilized by a cloud data loader as described further above. In a number of embodiments, a cloud beacon can independently send an alarm based on predetermined events and/or thresholds (as opposed to the alarm being triggered by analysis of data once entered into an analytics repository). Information from a cloud beacon can returned on a scheduled basis and/or in near real-time as collection, events, and/or alerts occur.

Cloud-to-Cloud Threat Warning System



[0106] In many embodiments of the invention, a cloud-to-cloud threat warning system provides communications between cloud applications. One cloud application can proactively warn another cloud application of a potential threat. Several business processes require cloud-to cloud-integration. When a threat is identified in a first cloud (e.g., a query from a blocked IP address), a cloud security monitoring and control system in accordance with embodiments of the invention can automatically notify a second cloud that is part of the business process. The notification can include a request or recommendation for a higher level of security controls, such as elevated authentication or OTP validation, in the business process. In several embodiments, the cloud security system can originate and/or coordinate the distribution of notifications and/or alerts to clouds.

[0107] Although the description above contains many specificities, these should not be construed as limiting the scope of the invention but as merely providing illustrations of some of the presently preferred embodiments of the invention. Various other embodiments are possible within its scope. Accordingly, the scope of the invention should be determined not by the embodiments illustrated, but by the appended claims and their equivalents.


Claims

1. A cloud security system for monitoring and controlling security of cloud application accounts comprising:

memory containing:

an analytics application;

a seeder application; and

an analytics repository database; and

a processor;

wherein the processor is configured by the analytics application to:

- generate a threat model using at least a first portion of stored activity data associated with a tenant account in the analytics repository database; and

- identify, based upon the threat model, a threat using a second portion of the stored activity data in the analytics repository database; and

wherein the processor is further configured by the seeder application to:

- select a security policy to implement in response to the identified threat;

- identify cloud security controls in at least one remotely hosted cloud application server system to modify in accordance with the selected security policy;

- establish a secure connection to the at least one remotely hosted cloud application server system using login credentials associated with the tenant account with a cloud application; and

- send instructions to the at least one remotely hosted cloud application server system to set the identified cloud security controls with respect to the tenant account in accordance with the selected security policy.


 
2. The cloud security system of claim 1 wherein the memory further contains a data loader application, and wherein the processor is configured by the data loader application to:

- establish a secure connection to one of the at least one remotely hosted cloud application server system using the login credentials associated with the tenant account with the cloud application;

- retrieve activity data associated with the tenant account from the at least one remotely hosted cloud application server system; and

- store the retrieved activity data in the analytics repository database, wherein the activity data i) is retrieved at predetermined intervals, ii) includes information concerning login and logout statistics, IP addresses, and devices used to access a cloud service, or iii) comprises values that are set for the identified cloud security controls with respect to the tenant account.


 
3. The cloud security system of claim 2 wherein the processor is further configured by the data loader application to normalize the retrieved activity data into a common format.
 
4. The cloud security system of claim 1 wherein the threat model models user behavior.
 
5. The cloud security system of claim 1 wherein the threat model correlates activities across a plurality of cloud applications by using user profile information associating a particular user's accounts across the plurality of cloud applications and the user's accounts are associated with the tenant account at each of the plurality of cloud applications.
 
6. The cloud security system of claim 5 wherein the user profile information associating the particular user's accounts across the plurality of cloud applications is retrieved from a user identity repository.
 
7. The cloud security system of claim 2, wherein the processor is further configured by the data loader application to determine whether a portion of the activity data matches predefined policy alerts.
 
8. The cloud security system of claim 1 wherein the processor is further configured by the analytics application to send an alert including alert information and one or more recommended remediation actions, the one or more recommended remediation actions including i) a first remediation action to disable a user's account, or ii) a second remediation action to prescribe a task to be performed outside of the cloud security system, wherein a result of the task is provided to the cloud security system.
 
9. The cloud security system of claim 8 wherein:

the memory further contains an incident remediation application;
wherein the one or more recommended remediation actions further include a third remediation action prescribing a task to be performed by the cloud security system;
and
wherein the processor is further configured by the incident remediation application to:

- perform said task, and store a result of said task into the memory.


 
10. The cloud security system of claim 1 wherein the processor is further configured by the seeder application to collect registration information from a tenant, and wherein the registration information includes an authorization token secured by encryption.
 
11. The cloud security system of claim 1 wherein the identified cloud security controls include password requirements.
 
12. The cloud security system of claim 1, wherein the memory further comprises a cloud crawler application, wherein the processor is further configured by the cloud crawler application to collect software defined security configuration data from a cloud service provider, wherein the software defined security configuration data comprises information describing a configuration of the identified cloud security controls in the cloud application with respect to the tenant account, and
wherein the processor is further configured by the cloud crawler application to normalize the software defined security configuration data and to enter the normalized software defined security configuration data into an application catalog database.
 
13. The cloud security system of claim 1 wherein the threat model is generated using a machine learning algorithm.
 
14. A method for monitoring and remediation of security threats to cloud applications, the method comprising:

- generating a threat model using at least a first portion of stored activity data associated with a tenant account in an analytics repository database using a cloud security system;

- identifying, based on the threat model, a threat using a second portion of the stored activity data in the analytics repository database using the cloud security system;

- selecting a security policy to implement in response to the identified threat using the cloud security system;

- identifying cloud security controls in at least one remotely hosted cloud application server system to modify in accordance with the selected security policy using the cloud security system;

- establishing, using the cloud security system, a secure connection to the at least one remotely hosted cloud application server system using login credentials associated with the tenant account with a cloud application; and

- sending instructions to the at least one remotely hosted cloud application server system to set the identified cloud security controls with respect to the tenant account in accordance with the selected security policy using the cloud security system.


 
15. A method for monitoring and remediation of security threats to cloud applications, the method comprising:

- collecting registration information from a tenant using a cloud security system, where the registration information includes an authorization token secured by encryption;

- establishing, using the cloud security system, a secure connection to a cloud application hosted by a cloud service provider using login credentials associated with a tenant account with a cloud application;

- collecting software defined security configuration data from the cloud service provider using the cloud security system, where the software defined security configuration data comprises information describing a configuration of security controls in the cloud application with respect to the tenant account;

- retrieving, using the cloud security system, activity data associated with the tenant account;

- storing the retrieved activity data in an analytics repository database using the cloud security system;

- generating a threat model using at least a first portion of stored activity data in the analytics repository database using the cloud security system;

- identifying, based upon the threat model, a threat using a second portion of the stored activity data in the analytics repository database using the cloud security system;

- sending an alert including alert information and one or more recommended remediation actions;

- selecting a security policy to implement in response to the identified threat using the cloud security system;

- identifying cloud security controls in at least one remotely hosted cloud application server system to modify in accordance with the selected security policy using the cloud security system;

- establishing, using the cloud security system, a secure connection to the at least one remotely hosted cloud application server system using login credentials associated with a tenant account with the cloud application; and

- sending instructions to the at least one remotely hosted cloud application server system to set the identified cloud security controls with respect to the tenant account in accordance with the selected security policy using the cloud security system.


 


Ansprüche

1. Cloud-Sicherheitssystem zur Überwachung und Kontrolle der Sicherheit von Cloud-Anwendungskonten, das Folgendes umfasst:

einen Speicher der Folgendes umfasst:

eine Analyseanwendung; eine Seeder-Anwendung und

eine Analysespeicherdatenbank; und

einen Prozessor;

wobei der Prozessor von der Analyseanwendung für Folgendes konfiguriert wird:

- Erstellen eines Bedrohungsmodells unter Verwendung mindestens eines ersten Teils der gespeicherten Aktivitätsdaten, die mit einem Mandantenkonto in der Analysespeicherdatenbank verknüpft sind; und

- Identifizieren einer Bedrohung basierend auf dem Bedrohungsmodell unter Verwendung eines zweiten Teils der gespeicherten Aktivitätsdaten in der Analysespeicherdatenbank; und

wobei der Prozessor ferner durch die Seeder-Anwendung für Folgendes konfiguriert ist:

- Auswählen einer Sicherheitsrichtlinie, die als Reaktion auf die erkannte Bedrohung implementiert werden soll;

- Identifizieren von Cloud-Sicherheitskontrollen in mindestens einem entfernt gehosteten Cloud-Anwendungsserver-System, um sie gemäß der ausgewählten Sicherheitsrichtlinie zu ändern;

- Herstellen einer sicheren Verbindung zu dem mindestens einen entfernt gehosteten Cloud-Anwendungsserver-System unter Verwendung von Anmeldeinformationen, die mit dem Mandantenkonto mit einer Cloud-Anwendung verknüpft sind; und

- Senden von Anweisungen an das mindestens eine entfernt gehostete Cloud-Anwendungsserver-System, um die identifizierten Cloud-Sicherheitskontrollen in Bezug auf das Mandantenkonto gemäß der ausgewählten Sicherheitsrichtlinie festzulegen.


 
2. Cloud-Sicherheitssystem nach Anspruch 1, wobei der Speicher ferner eine Datenladeanwendung umfasst und wobei der Prozessor von der Datenladeanwendung für Folgendes konfiguriert wird:

- Herstellen einer sicheren Verbindung zu einem des mindestens einen entfernt gehosteten Cloud-Anwendungsserver-Systems unter Verwendung der Anmeldeinformationen, die mit dem Mandantenkonto mit der Cloud-Anwendung verknüpft sind;

- Abrufen von Aktivitätsdaten, die mit dem Mandantenkonto verknüpft sind, von dem mindestens einen entfernt gehosteten Cloud-Anwendungsserver-System; und

- Speichern der abgerufenen Aktivitätsdaten in der Analysespeicherdatenbank, wobei die Aktivitätsdaten i) in vorbestimmten Intervallen abgerufen werden, ii) Informationen über Anmelde - und Abmeldestatistiken, IP-Adressen und Vorrichtungen, die für den Zugriff auf einen Cloud-Dienst verwendet werden, umfassen oder iii) Werte umfassen, die für die identifizierten Cloud-Sicherheitskontrollen in Bezug auf das Mandantenkonto festgelegt sind.


 
3. Cloud-Sicherheitssystem nach Anspruch 2, wobei der Prozessor ferner durch die Datenladeanwendung konfiguriert wird, um die abgerufenen Aktivitätsdaten in ein gemeinsames Format zu normalisieren.
 
4. Cloud-Sicherheitssystem nach Anspruch 1, wobei das Bedrohungsmodell das Benutzerverhalten modelliert.
 
5. Cloud-Sicherheitssystem nach Anspruch 1, wobei das Bedrohungsmodell Aktivitäten über eine Vielzahl von Cloud-Anwendungen hinweg korreliert, indem Benutzerprofilinformationen verwendet werden, die die Konten eines bestimmten Benutzers den mehreren Cloud-Anwendungen zuordnen, und wobei die Konten des Benutzers dem Mandantenkonto bei jeder der mehreren Cloud-Anwendungen zugeordnet sind.
 
6. Cloud-Sicherheitssystem nach Anspruch 5, wobei die Benutzerprofilinformationen, die die Konten des bestimmten Benutzers über die Vielzahl von Cloud-Anwendungen hinweg zuordnen, aus einem Benutzeridentitätsspeicher abgerufen werden.
 
7. Cloud-Sicherheitssystem nach Anspruch 2, wobei der Prozessor ferner durch die Datenladeanwendung konfiguriert wird, um zu bestimmen, ob ein Teil der Aktivitätsdaten mit vorbestimmten Richtlinienwarnungen übereinstimmt.
 
8. Cloud-Sicherheitssystem nach Anspruch 1, wobei der Prozessor ferner von der Analyseanwendung konfiguriert wird, um eine Warnung einschließlich Warninformationen und eine oder mehrere empfohlene Korrekturmaßnahmen zu senden, wobei die eine oder die mehreren empfohlenen Maßnahmen Folgendes umfassen: i) eine erste Korrekturmaßnahme zur Deaktivierung eines Benutzerkontos oder ii) eine zweite Korrekturmaßnahme, um eine außerhalb des Cloud-Sicherheitssystems auszuführende Aufgabe vorzuschreiben, wobei ein Ergebnis der Aufgabe dem Cloud-Sicherheitssystem bereitgestellt wird.
 
9. Cloud-Sicherheitssystem nach Anspruch 8, wobei:

der Speicher ferner eine Vorfall-Korrekturanwendung umfasst;

wobei die eine oder die mehreren empfohlenen Korrekturmaßnahmen ferner eine dritte Korrekturmaßnahme umfassen, die eine durch das Cloud-Sicherheitssystem auszuführende Aufgabe vorschreibt; und

wobei der Prozessor durch die Vorfall-Korrekturanwendung ferner für Folgendes konfiguriert ist:

- Ausführen der Aufgabe und Speichern eines Ergebnisses der Aufgabe in dem Speicher.


 
10. Cloud-Sicherheitssystem nach Anspruch 1, wobei der Prozessor ferner von der Seeder-Anwendung konfiguriert wird, um Registrierungsinformationen von einem Mandanten zu sammeln, und wobei die Registrierungsinformationen ein Autorisierungstoken umfassen, das durch Verschlüsselung gesichert ist.
 
11. Cloud-Sicherheitssystem nach Anspruch 1, wobei die identifizierten Cloud-Sicherheitskontrollen Passwortanforderungen enthalten.
 
12. Cloud-Sicherheitssystem nach Anspruch 1, wobei der Speicher ferner eine Cloud-Crawler-Anwendung umfasst, wobei der Prozessor ferner durch die Cloud-Crawler-Anwendung dafür konfiguriert ist, softwaredefinierte Sicherheitskonfigurationsdaten von einem Cloud-Dienstanbieter zu sammeln, wobei die softwaredefinierten Sicherheitskonfigurationsdaten Informationen umfassen, die eine Konfiguration der identifizierten Cloud-Sicherheitssteuerungen in der Cloud-Anwendung in Bezug auf das Mandantenkonto beschreiben, und
wobei der Prozessor ferner durch die Cloud-Crawler-Anwendung konfiguriert ist, um die softwaredefinierten Sicherheitskonfigurationsdaten zu normalisieren und die normalisierten softwaredefinierten Sicherheitskonfigurationsdaten in eine Anwendungskatalogdatenbank einzugeben.
 
13. Cloud-Sicherheitssystem nach Anspruch 1, wobei das Bedrohungsmodell unter Verwendung eines maschinellen Lernalgorithmus erzeugt wird.
 
14. Verfahren zur Überwachung und Behebung von Sicherheitsbedrohungen für Cloud-Anwendungen, wobei das Verfahren Folgendes umfasst:

- Erstellen eines Bedrohungsmodells unter Verwendung mindestens eines ersten Teils der gespeicherten Aktivitätsdaten, die mit einem Mandantenkonto in einer Analysespeicherdatenbank verknüpft sind, unter Verwendung eines Cloud-Sicherheitssystems;

- Identifizieren einer Bedrohung basierend auf dem Bedrohungsmodell unter Verwendung eines zweiten Teils der gespeicherten Aktivitätsdaten in der Analysespeicherdatenbank, unter Verwendung des Cloud-Sicherheitssystems;

- Auswählen einer Sicherheitsrichtlinie, die als Reaktion auf die erkannte Bedrohung implementiert werden soll, unter Verwendung des Cloud-Sicherheitssystems;

- Identifizieren von Cloud-Sicherheitskontrollen in mindestens einem entfernt gehosteten Cloud-Anwendungsserver-System, um sie gemäß der ausgewählten Sicherheitsrichtlinie zu ändern, unter Verwendung des Cloud-Sicherheitssystems;

- Herstellen unter Verwendung des Cloud-Sicherheitssystems einer sicheren Verbindung zu dem mindestens einen entfernt gehosteten Cloud-Anwendungsserver-System unter Verwendung von Anmeldeinformationen, die mit dem Mandantenkonto mit einer Cloud-Anwendung verknüpft sind; und

- Senden von Anweisungen an das mindestens eine entfernt gehostete Cloud-Anwendungsserver-System, um die identifizierten Cloud-Sicherheitskontrollen in Bezug auf das Mandantenkonto gemäß der ausgewählten Sicherheitsrichtlinie festzulegen, unter Verwendung des Cloud-Sicherheitssystems.


 
15. Verfahren zur Überwachung und Behebung von Sicherheitsbedrohungen für Cloud-Anwendungen, wobei das Verfahren Folgendes umfasst:

- Sammeln von Registrierungsinformationen von einem Mandanten unter Verwendung eines Cloud-Sicherheitssystems, wobei die Registrierungsinformationen ein Autorisierungstoken umfassen, das durch Verschlüsselung gesichert ist;

- Herstellen unter Verwendung des Cloud-Sicherheitssystems einer sicheren Verbindung zu einer Cloud-Anwendung, die von einem Cloud-Dienstanbieter gehostet wird, unter Verwendung von Anmeldeinformationen, die mit einem Mandantenkonto mit einer Cloud-Anwendung verknüpft sind;

- Sammeln von softwaredefinierten Sicherheitskonfigurationsdaten von dem Cloud-Dienstanbieter unter Verwendung des Cloud-Sicherheitssystems, wobei die softwaredefinierten Sicherheitskonfigurationsdaten Informationen umfassen, die eine Konfiguration der identifizierten Cloud-Sicherheitssteuerungen in der Cloud-Anwendung in Bezug auf das Mandantenkonto beschreiben, und

- Abrufen von Aktivitätsdaten, die mit dem Mandantenkonto verknüpft sind, unter Verwendung des Cloud-Sicherheitssystems;

- Speichern der abgerufenen Aktivitätsdaten in einer Analysespeicherdatenbank unter Verwendung des Cloud-Sicherheitssystems;

- Erstellen eines Bedrohungsmodells unter Verwendung mindestens eines ersten Teils der gespeicherten Aktivitätsdaten in einer Analysespeicherdatenbank unter Verwendung eines Cloud-Sicherheitssystems;

- Identifizieren einer Bedrohung basierend auf dem Bedrohungsmodell unter Verwendung eines zweiten Teils der gespeicherten Aktivitätsdaten in der Analysespeicherdatenbank, unter Verwendung des Cloud-Sicherheitssystems;

- Senden einer Warnung einschließlich Warninformationen und einer oder mehrerer empfohlener Korrekturmaßnahmen;

- Auswählen einer Sicherheitsrichtlinie, die als Reaktion auf die erkannte Bedrohung implementiert werden soll, unter Verwendung des Cloud-Sicherheitssystems;

- Identifizieren von Cloud-Sicherheitskontrollen in mindestens einem entfernt gehosteten Cloud-Anwendungsserver-System, um sie gemäß der ausgewählten Sicherheitsrichtlinie zu ändern, unter Verwendung des Cloud-Sicherheitssystems;

- Herstellen unter Verwendung des Cloud-Sicherheitssystems einer sicheren Verbindung zu dem mindestens einen entfernt gehosteten Cloud-Anwendungsserver-System unter Verwendung von Anmeldeinformationen, die mit einem Mandantenkonto mit der Cloud-Anwendung verknüpft sind; und

- Senden von Anweisungen an das mindestens eine entfernt gehostete Cloud-Anwendungsserver-System, um die identifizierten Cloud-Sicherheitskontrollen in Bezug auf das Mandantenkonto gemäß der ausgewählten Sicherheitsrichtlinie festzulegen, unter Verwendung des Cloud-Sicherheitssystems.


 


Revendications

1. Système de sécurité de cloud pour le contrôle et la commande de la sécurité de comptes d'applications cloud comprenant :

une mémoire contenant :

une application analytique ;

une application Seeder; et

une base de données de dépôt analytique ; et

un processeur;

dans lequel le processeur est configuré par l'application analytique pour :

- générer un modèle de menace à l'aide au moins d'une première partie de données d'activité associées à un compte propriétaire dans la base de données de dépôt analytique ; et

- identifier, en fonction du modèle de menace, une menace à l'aide d'une seconde partie de données d'activité mémorisées dans la base de données de dépôt analytique ; et dans lequel le processeur est configuré en outre par l'application Seeder pour :

- sélectionner une stratégie de sécurité à mettre en oeuvre en réponse à la menace identifiée ;

- identifier des commandes de sécurité de cloud dans au moins un système de serveur d'applications cloud hébergées à distance à modifier conformément à la stratégie de sécurité sélectionnée ;

- établir une connexion sécurisée avec l'au moins un système de serveur d'applications cloud hébergées à distance à l'aide de références de connexion associées au compte propriétaire avec une application cloud ; et

- envoyer des instructions à l'au moins un système de serveur d'applications cloud hébergées à distance pour établir les commandes de sécurité de cloud identifiées relativement au compte propriétaire conformément à la stratégie de sécurité sélectionnée.


 
2. Système de sécurité de cloud selon la revendication 1 dans lequel la mémoire contient en outre une application de chargement de données et le processeur est configuré par l'application de chargement de données pour :

- établir une connexion sécurisée avec l'un de l'au moins un système de serveur d'applications cloud hébergées à distance à l'aide des références de connexion associées au compte propriétaire avec l'application cloud ;

- recouvrer des données d'activité associées au compte propriétaire auprès de l'au moins un système de serveur d'applications cloud hébergées à distance ; et

- mémoriser les données d'activité recouvrées dans la base de données de dépôt analytique, dans lequel les données d'activité i) sont recouvrées à des intervalles prédéterminés, ii) comportent des informations relatives à des statistiques de connexion et de déconnexion, adresses IP et dispositifs utilisés pour accéder à une service cloud, ou iii) comprennent des valeurs qui sont établies pour les commandes de sécurité de cloud associées au compte propriétaire.


 
3. Système de sécurité de cloud selon la revendication 2 dans lequel le processeur est configuré en outre par l'application de chargement de données pour normaliser les données d'activité recouvrées dans un format commun.
 
4. Système de sécurité de cloud selon la revendication 1 dans lequel le modèle de menace modélise un comportement d'utilisateur.
 
5. Système de sécurité de cloud selon la revendication 1 dans lequel le modèle de menace met en corrélation des activités sur une pluralité d'applications cloud à l'aide d'informations de profil d'utilisateur qui associent les comptes d'un utilisateur particulier sur la pluralité d'applications cloud et les comptes de l'utilisateur sont associés au compte propriétaire pour chacune de la pluralité d'applications cloud.
 
6. Système de sécurité de cloud selon la revendication 5 dans lequel les informations de profil d'utilisateur associant les comptes de l'utilisateur particulier sur la pluralité d'applications cloud sont recouvrées depuis un dépôt d'identités d'utilisateurs.
 
7. Système de sécurité de cloud selon la revendication 2, dans lequel le processeur est configuré en outre par l'application de chargement de données pour déterminer qu'une partie des données d'activité correspond ou non à des alertes de stratégie prédéfinies.
 
8. Système de sécurité de cloud selon la revendication 1 dans lequel le processeur est configuré en outre par l'application analytique pour envoyer une alerte comportant des informations d'alerte et une ou plusieurs actions correctrices recommandées, les une ou plusieurs actions correctrices recommandées comportant i) une première action correctrice pour désactiver un compte d'utilisateur, ou ii) une seconde action correctrice pour prescrire une tâche à exécuter en dehors du système de sécurité de cloud, dans lequel un résultat de la tâche est fourni au système de sécurité de cloud.
 
9. Système de sécurité de cloud selon la revendication 8 dans lequel :

la mémoire contient en outre une application de correction d'incident ;

dans lequel les une ou plusieurs actions correctrices recommandées comportent en outre une troisième action correctrice prescrivant une tâche devant être exécutée par le système de sécurité de cloud ; et

dans lequel le processeur est configuré en outre par l'application de correction d'incident pour :

- exécuter la tâche et mémoriser le résultat de la tâche.


 
10. Système de sécurité de cloud selon la revendication 1 dans lequel le processeur est configuré en outre par l'application Seeder pour coller des informations d'enregistrement d'un propriétaire, et dans lequel les informations d'enregistrement comportent un jeton d'autorisation sécurisé par cryptage.
 
11. Système de sécurité de cloud selon la revendication 1 dans lequel les commandes de sécurité de cloud identifiées comportent des exigences de mots de passe.
 
12. Système de sécurité de cloud selon la revendication 1, dans lequel la mémoire comporte en outre une application d'indexation de cloud et le processeur est configuré en outre par l'application d'indexation de cloud pour collecter des données de configuration de sécurité définies par logiciel auprès d'un fournisseur de service cloud, dans lequel les données de configuration de sécurité définies par logiciel comprennent des informations décrivant une configuration des commandes de sécurité de cloud identifiées dans l'application cloud relativement au compte propriétaire, et dans lequel le processor est configuré en outre par l'application d'indexation de cloud pour normaliser les données de configuration de sécurité définies par logiciel et entrer les données de configuration de sécurité définies par logiciel normalisées dans une base de données de catalogue d'applications.
 
13. Système de sécurité de cloud selon la revendication 1 dans lequel le modèle de menace est généré à l'aide d'un algorithme d'apprentissage de machine.
 
14. Procédé de contrôle et de correction de menaces de sécurité d'applications cloud, le procédé comprenant :

- la génération d'un modèle de menace à l'aide au moins d'une première partie de données d'activité mémorisées associées à un compte propriétaire dans une base de données de dépôt analytique à l'aide d'un système de sécurité de cloud ;

- l'identification, en fonction du modèle de menace, d'une menace à l'aide d'une seconde partie des données d'activité mémorisées dans la base de données de dépôt analytique à l'aide du système de sécurité de cloud ;

- la sélection d'une stratégie de sécurité à mettre en oeuvre en réponse à la menace identifiée à l'aide du système de sécurité de cloud ;

- l'identification de commandes de sécurité de cloud dans au moins un système de serveur d'applications cloud hébergées à distance à modifier conformément à la stratégie de sécurité sélectionnée à l'aide du système de sécurité de cloud ;

- l'établissement, à l'aide du système de sécurité de cloud, d'une connexion sécurisée avec l'au moins un système de serveur d'applications cloud hébergées à distance à l'aide de références de connexion associées au compte propriétaire avec une application cloud ; et

- l'envoi d'instructions à l'au moins un système de serveur d'applications cloud hébergées à distance pour établir les commandes de sécurité de cloud identifiées relativement au compte propriétaire conformément à la stratégie de sécurité sélectionnée à l'aide du système de sécurité de cloud.


 
15. Procédé de contrôle et de correction de menaces de sécurité d'applications cloud, le procédé comprenant :

- la collecte d'informations d'enregistrement auprès d'un propriétaire à l'aide du système de sécurité de cloud, dans lequel les informations d'enregistrement comportent un jeton d'autorisation sécurisé par cryptage ;

- l'établissement, à l'aide du système de sécurité de cloud, d'une connexion sécurisée avec une application cloud hébergée par un fournisseur de service cloud à l'aide de références de connexion associées à un compte propriétaire avec une application cloud ;

- la collecte de données de configuration de sécurité définies par logiciel auprès du fournisseur de service cloud à l'aide du système de sécurité de cloud, dans lequel les données de configuration de sécurité définies par logiciel comprennent des informations décrivant la configuration des commandes de sécurité dans l'application cloud relativement au compte propriétaire ;

- le recouvrement, à l'aide du système de sécurité de cloud, de données d'activité associées au compte propriétaire ;

- la mémorisation des données d'activité recouvrées dans une base de données de dépôt analytique à l'aide du système de sécurité de cloud ;

- la génération d'un modèle de menace à l'aide au moins d'une première partie de données d'activité mémorisées dans la base de données de dépôt analytique à l'aide du système de sécurité de cloud ;

- l'identification, en fonction du modèle de menace, d'une menace à l'aide d'une seconde partie des données d'activité mémorisées dans la base de données de dépôt analytique à l'aide du système de sécurité de cloud ;

- l'envoi d'une alerte comportant des informations d'alerte et une ou plusieurs actions correctrices recommandées ;

- la sélection d'une stratégie de sécurité à mettre en oeuvre en réponse à la menace identifiée à l'aide du système de sécurité de cloud ;

- l'identification de commandes de sécurité de cloud dans au moins un système de serveur d'applications cloud hébergées à distance à modifier conformément à la stratégie de sécurité sélectionnée à l'aide du système de sécurité de cloud ;

- l'établissement, à l'aide du système de sécurité de cloud, d'une connexion sécurisée avec l'au moins un système de serveur d'applications cloud hébergées à distance à l'aide de références de connexion associées à un compte propriétaire avec l'application cloud ; et

- l'envoi d'instructions à l'au moins un système de serveur d'applications cloud hébergées à distance pour établir les commandes de sécurité de cloud identifiées relativement au compte propriétaire conformément à la stratégie de sécurité sélectionnée à l'aide du système de sécurité de cloud.


 




Drawing







































REFERENCES CITED IN THE DESCRIPTION



This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

Patent documents cited in the description