Abstract: In response to detected attempts to gain unauthorized access to user accounts of an online system, a security module of an online system applies an attack response policy to take actions in response to the attempts. Possible responses of the policy include reordering credential types requested by the online system during multi-factor authentication-enabled login, switching to a mode in which login requests are accepted but login is not permitted for the requesting user, and logging information about the login requests. Logged information may be applied to enhance the ability to prevent future unauthorized accesses, such as adding credential values to a list of common credential values and prohibiting users from associating those values with their accounts, or training a model based on the logged information to predict a probability that a given login request is unauthorized.

Abstract: In response to detected attempts to gain unauthorized access to user accounts of an online system, a security module of an online system applies an attack response policy to take actions in response to the attempts. Possible responses of the policy include reordering credential types requested by the online system during multi-factor authentication-enabled login, switching to a mode in which login requests are accepted but login is not permitted for the requesting user, and logging information about the login requests. Logged information may be applied to enhance the ability to prevent future unauthorized accesses, such as adding credential values to a list of common credential values and prohibiting users from associating those values with their accounts, or training a model based on the logged information to predict a probability that a given login request is unauthorized.

Abstract: A bookmark file is stored in persistent storage and is updated as various tasks are completed during an installation process. The bookmark file may be read when an installation process is started so that the installation process may continue from a point after the last successfully completed task, if the installation process had failed and was restarted. The bookmark file may also include data collected from a user interface during the installation process. When an installation process is restarted, some embodiments may present the data in a user interface for the user to modify. The installation process may be defined in a configuration file that includes metadata that defines the sequence of installation tasks as well as some error handling for various tasks.

Abstract: A computer environment analysis tool may have a modular architecture that comprises data collection modules and data analysis modules. The data collection modules may populate multiple data sets defined by a schema, and the data analysis modules may analyze or interpret the data from the database to produce report output. A reporting module may generate information that may be consumed by a user or other service. The data collection modules may be specialized modules that collect specific types of data from local and remote devices, and the data analysis modules may analyze the data for specific business logic, such as determining if a computer environment is capable of upgrading or deploying various changes.

Abstract: A backup system stores configuration data for several interdependent systems in a single backup store. As the systems are being configured and when changes are made to the systems, the backup store is updated with the change. The systems may be configured with each system having a designated role. During a restore operation, an otherwise unallocated system may assume a particular role and use the configuration logic defined for the role that may be taken from the backup store. The system may perform the restore in conjunction with the other systems and the interdependencies with the systems.

Abstract: A bookmark file is stored in persistent storage and is updated as various tasks are completed during an installation process. The bookmark file may be read when an installation process is started so that the installation process may continue from a point after the last successfully completed task, if the installation process had failed and was restarted. The bookmark file may also include data collected from a user interface during the installation process. When an installation process is restarted, some embodiments may present the data in a user interface for the user to modify. The installation process may be defined in a configuration file that includes metadata that defines the sequence of installation tasks as well as some error handling for various tasks.

Abstract: A setup or installation operation is divided into discrete task components, each of which has a data input. The data input may be in the form of an information file that is populated by user input, discovery routines, or from predefined data. When an installation is successfully completed, the information file may be saved and be used to track a configuration history. The same information file may be used for a silent setup where an installation operation may be executed without any user input. The setup system may be extensible by adding additional discrete task components and extending the information file to include data used by the additional components.