Upload 1323 files

API_Playground_1.md

@@ -0,0 +1,19 @@
+# API Playground
+
+Source: https://docs.rubrik.com/en-us/saas/gql/api_playground_2.html
+
+---
+
+# API Playground
+
+API Playground is a development environment integrated with Rubrik Security Cloud that you can use to run various GraphQL API operations on the data managed in real time by RSC.
+
+API Playground is an integrated development environment (IDE) that you can use to browse, explore, and run GraphQL APIs offered by Rubrik Security Cloud (RSC). The IDE also provides reference to the latest Rubrik GraphQL API documentation. Running GraphQL queries and mutations in API Playground validates the GraphQL operations so that you can confirm that your queries or mutations will achieve the expected result when included in automation scripts.
+
+After logging in to API Playground with your RSC user account credentials, you can choose to run GraphQL queries and mutations either as yourself or with a service account. The level of access you have for running the GraphQL queries and mutations depends on the RBAC roles assigned to your user account or to the service account you are using. For enhanced security, API Playground does not persist the service account access credentials.
+
+Warning:
+
+If not used cautiously, the GraphQL mutations that you run in API Playground can result in data loss because they affect the data managed in real time by RSC.
+
+In addition to using the API Playground, you can also use the PowerShell SDK for RSC to enable seamless automation and management of various operations within RSC. You can download the SDK from the [PowerShell Gallery](https://www.powershellgallery.com/packages/RubrikSecurityCloud) or from the [Rubrikinc GitHub repository](https://github.com/rubrikinc/rubrik-powershell-sdk).

Annapurna_1.md

@@ -0,0 +1,35 @@
+# Annapurna
+
+Source: https://docs.rubrik.com/en-us/saas/ai/annapurna.html
+
+---
+
+# Annapurna
+
+Rubrik Security Cloud includes the Annapurna application which you can use to obtain answers from your data, using generative AI.
+
+Annapurna is an enterprise application. By using the generative AI capabilities of Annapurna, you can leverage your protected data to obtain natural language answers to business questions through retrieval-augmented generation (RAG).
+
+You can use Annapurna in two different ways: 
+
+  * Custom chatbots can be created in Rubrik Security Cloud (RSC) to process your prompts through the large language model (LLM) of Azure OpenAI Service.
+  * Data chunks generated via RAG can be retrieved using an API endpoint, and these chunks can then be sent to your specified LLM within your custom GenAI application.
+
+To begin using Annapurna with your enterprise data, your administrators create chatbots. Each chatbot specifies which workload data to index and which sensitive data filters to apply. A chatbot can be configured to exclude sensitive user data based on your Data Security Posture policies. Data sources from the following workloads can be included:
+
+  * Microsoft 365
+  * Jira Cloud
+  * Salesforce
+  * Confluence[1](#fntarg_1)
+
+After specifying the data to include, your administrators assign a role to the chatbot. Only users with the assigned role will be able to use the chatbot. The data available to a user through a chatbot depends on the access permissions the user has for that data. Annapurna uses the permissions assigned by each source application to determine the access a user has to data from that application.
+
+Once chatbots are created, your enterprise users can launch a chatbot and ask natural language questions about the data available through the chatbot. Based on the query, Annapurna uses RAG to get relevant data from the available data sources. The retrieved data and the query are combined into a prompt and sent to the LLM. The user gets a natural language response to their query that is based on the data included in the prompt. This process does not involve training the LLM.
+
+The chatbots that your administrators create can use multiple data sources from different workload types. This means a chatbot can query data from various workloads at the same time. Queries through such a chatbot can give answers that combine data from different sources.
+
+Important:
+
+Annapurna uses generative AI to respond to your prompts. AI-generated content may contain errors or inaccuracies. Independent verification of such content is strongly recommended.
+
+[1](#fnsrc_1) To enable Confluence as a data source, contact Rubrik Support.

Anomaly_Detection_1.md

@@ -0,0 +1,52 @@
+# Anomaly Detection
+
+Source: https://docs.rubrik.com/en-us/saas/saas/anomaly_detection.html
+
+---
+
+# Anomaly Detection
+
+Anomaly Detection examines a range of file system statistics to check for anomalies in file system usage patterns.
+
+Anomaly Detection provides details about potentially anomalous incidents, including their location, Rubrik cluster, file details, and snapshot time. When you enable Orchestrated Recovery, objects that are part of a Recovery Plan are grouped together.
+
+When you enable Anomaly Detection for the data, Large Language Model (LLM) analysis for Anomaly Detection is enabled by default. When LLM analysis for Anomaly Detection is enabled, RSC uses a pre-trained LLM in Microsoft Azure OpenAI to detect suspicious activity. The model differentiates suspicious activity from legitimate changes caused by routine operations, such as upgrading an application or operating system.
+
+Identifying and differentiating malicious behavior from legitimate activities helps reduce the frequency of false alerts and enhances the experience of using Anomaly Detection to protect data. When you do not want to use LLM analysis on Anomaly Detection, you can disable it and use Anomaly Detection without it.
+
+When you enable Data Security Posture for an object that has an anomalous snapshot and a user account that has Data Security Posture privileges, the Sensitive files and Sensitive hits columns display values based on the base snapshot of the anomalous snapshot. The Sensitive files column shows the number of files that contain sensitive data, and the Sensitive hits column shows the number of sensitive hits for that object.
+
+Note:
+
+Anomaly Detection supports protected objects running in single-stack IPv6 environments.
+
+On the Anomaly Detection page, you can:
+
+  * View the list of new and resolved investigations.
+  * Use the filters on the page to sort anomalies by time range, severity, encryption, object type, Rubrik cluster, and SLA Domain.
+  * Sort anomalous data by sensitive files or sensitive hits when you enable Data Security Posture.
+  * Filter anomalies by the selected policies when you enable Data Security Posture.
+  * Investigate and recover anomalous files in protected workloads.
+  * Recover a full snapshot for a virtual machine.
+  * Use the Search filter to search for protected workloads or Recovery Plans that have an identified anomaly.
+  * Initiate bulk recovery for vSphere-protected workloads or for Recovery Plans that have an identified anomaly.
+  * Perform cyber recovery on virtual machines based on threat hunting results to a local, isolated recovery environment.
+  * Download a CSV file of the changes identified for each protected workload. When you click Download CSV, RSC prepares a secure link for the file and displays a message about the download. You can also visit the File Preparation Center to access the downloaded file.
+
+RSC supports Anomaly Detection for:
+
+  * VMware, AHV, and Hyper-V virtual machines
+  * NAS filesets
+  * Linux and Windows servers
+  * Windows Volume groups
+  * NAS CD data sets
+  * Azure virtual machines
+  * Azure Blob storage
+  * Microsoft OneDrive and SharePoint
+  * Amazon S3 buckets
+  * Amazon EC2 instances and EBS volumes
+  * Kubernetes virtual machines
+  * Kubernetes protection sets
+  * GCP GCE Instance
+  * GCP Persistent Disk
+

Anomaly_Detection_reports_1.md

@@ -0,0 +1,13 @@
+# Anomaly Detection reports
+
+Source: https://docs.rubrik.com/en-us/saas/saas/ri_reports.html
+
+---
+
+# Anomaly Detection reports
+
+Anomaly Detection reports provide information about the changes in snapshots for anomaly events. You can also download, save, or delete the reports.
+
+The Anomaly Detection report displays information about anomalies detected in the Scanned Objects and Unscannable Objects tab. You can view details, including snapshot date, resource name, resource type, change in byte size, anomaly indicator, number of files added, number of files removed, and number of files modified.
+
+You can also download a CSV or PDF file of the report, send the report to an email address, and save or delete the report.

CLI_administrator_role_1.md

@@ -0,0 +1,15 @@
+# CLI administrator role
+
+Source: https://docs.rubrik.com/en-us/saas/cdm/cli_administrator_role.html
+
+---
+
+# CLI administrator role
+
+As a CLI administrator, a Rubrik cluster user can connect to nodes in Rubrik clusters through the CLI Secure Shell (SSH) protocol.
+
+As both an administrator and a CLI administrator, you can assign the CLI administrator role (CliAdminRole) to others who have the administrator role. With that role, they can connect to nodes in the Rubrik cluster through the Secure Shell (SSH) protocol and use the full range of CLI commands.
+
+The CLI administrator role cannot be assigned to a username that contains a dot (.) character.
+
+Regardless of their assigned roles, only Rubrik CDM local users can connect using SSH. LDAP and SSO users are denied SSH access.

Cluster_configuration_considerations_1.md

@@ -0,0 +1,19 @@
+# Cluster configuration considerations
+
+Source: https://docs.rubrik.com/en-us/saas/install/rsc_cluster_config_considerations.html
+
+---
+
+# Cluster configuration considerations
+
+You determine network related settings and capabilities of a Rubrik cluster through the set up task.
+
+The initial setup of the cluster involves node discovery, and the configuration of data and management interfaces and services for all the nodes on the cluster. A UI to perform the initial configuration is available through any of the nodes. Alternatively, you can configure the cluster at the command line using the Rubrik CLI.
+
+If you have an IPv4 cluster deployment, you can optionally configure VLAN tagging for both the management network and the data network. You can configure VLAN tagging through either the UI or the Rubrik CLI.
+
+If your cluster deployment supports encryption of data at rest, Rubrik CDM enables data encryption by default during the initial configuration. You can disable the encryption of data at rest but this must be done through the CLI and should be done before protecting any data. If the encryption of data at rest setting is changed after system setup, a cluster reset is required, which will delete all stored data.
+
+The setting for encryption of data at rest is supported only on Brik models that have the hardware Trusted Platform Module (TPM).You will not have this option during setup for Brik models that use hardware data encryption at rest, such as the r6xxxF series Briks.
+
+Virtual clusters allow you to configure an encryption password when you enable encryption.

Cluster_registration_1.md

@@ -0,0 +1,17 @@
+# Cluster registration
+
+Source: https://docs.rubrik.com/en-us/saas/install/rsc_cluster_registration.html
+
+---
+
+# Cluster registration
+
+Rubrik offers two modes for registering clusters with Rubrik Security Cloud, online and offline.
+
+After configuring a Rubrik cluster, the next required task is to register it through your Rubrik Security Cloud account. Registration is performed over the internet using a web browser.
+
+The online registration method uses a secure internet connection from the Rubrik cluster to your Rubrik Security Cloud account to retrieve the registration key. When physical hardware is in use, that hardware must also be available and have access to the network.
+
+The offline registration method uses a manual method of retrieving the registration key and providing it to the Rubrik cluster. Offline registration requires access to a web browser for a one-time login to the Rubrik Security Cloud account to retrieve a unique registration key for each cluster. The registration key is valid only for two days from the time it is generated.
+
+Either way, the registration process requires signing into your Rubrik Security Cloud account using a web browser on a computer with an internet connection, even when the configuration of the cluster was performed through the CLI. The domain URL of your Rubrik Security Cloud account is available in the Rubrik Welcome email or on the Rubrik Support portal.

Comments_and_suggestions_2.md

@@ -0,0 +1,33 @@
+# Comments and suggestions
+
+Source: https://docs.rubrik.com/en-us/saas/reuse/comments_suggestions.html
+
+---
+
+# Comments and suggestions
+
+We welcome your comments and suggestions about our products and our product documentation.
+
+## Products
+
+To provide comments and suggestions about our products contact Rubrik Support, as described in [Support](support.html "Use one of the following methods to contact Rubrik Support.").
+
+## Product documentation
+
+To provide comments and suggestions about the product documentation, send an email to: [[email protected]](mailto:[email protected]). 
+
+To help our writers identify the area that you are referencing, include the following requested information.
+
+For HTML documentation, include:
+
+  * Page title
+  * Page address
+  * Page date
+
+For PDF documentation, include:
+
+  * PDF title
+  * Part number
+  * Revision
+  * Relevant page numbers
+

Data_Security_Posture_1.md

@@ -0,0 +1,29 @@
+# Data Security Posture
+
+Source: https://docs.rubrik.com/en-us/saas/dspm/data_security_posture.html
+
+---
+
+# Data Security Posture
+
+Data Security Posture provides agile data security across multi-cloud environments for posture management and access governance. It also includes threat monitoring and response to protect your data.
+
+Organizations have innovated how they use cloud data, but not how they secure it. Users create, copy, share, and move cloud data rapidly. This drastic expansion and replication of data for business advantage protected by traditional data security controls creates a security gap. Data Security Posture provides the capability to effectively manage data security, for data located on premises, in the cloud, or on SaaS applications. This unified approach enables you to define, manage, and monitor policies regardless of where data resides. Rubrik Data Security Posture discovers and classifies all data across all your environments, including managed and self-hosted technologies to provide the following benefits:
+
+  * Automated data discovery across on-prem, cloud, and SaaS workloads
+  * Data classification without impact on production workloads
+  * Built-in and customizable data categories and data types
+  * Identity inventory showing sensitive data access and blast radius
+  * Identification of data at risk and appropriate access remediation
+  * User Insights highlighting changes to sensitive data
+  * Detection of suspicious data activity
+
+Data Security Posture automatically discovers and classifies an extensive range of data detected across your multi-cloud environment while ensuring that sensitive data never leaves your environment. Data Security Posture focuses on the following:
+
+  * Identifying sensitive and regulated data across your organization
+  * Locating objects that have sensitive data and their location and flagging their exposure
+  * Detecting violations of your data policy and identifying misconfigured, misplaced, or obsolete data
+  * User access to data and remedying access issues
+  * Monitoring for allowed access and providing alerts of anomalous activities
+
+You can use the insights from Data Security Posture with third-party integrations to maintain a data security environment resilient to external threats.

Data_Threat_Analytics_dashboard_1.md

@@ -0,0 +1,23 @@
+# Data Threat Analytics dashboard
+
+Source: https://docs.rubrik.com/en-us/saas/saas/dta_dashboard.html
+
+---
+
+# Data Threat Analytics dashboard
+
+The Data Threat Analytics dashboard provides a comprehensive analysis of data threats including a summary of anomalies, threat monitoring matches, matched threat hunts for protected objects, and object timeline analysis.
+
+Widget | Description  
+---|---  
+Threat Summary | Displays the number of backups completed with the percentage of healthy backups and the following Data Threat Analytics summary:
+
+  * Anomaly Detection analysis completed and the number of anomalous objects found
+  * Threat Monitoring results with the details of the objects scanned for IOCs appear
+  * Active threat hunts with the number of matched hunts
+
+You can filter the data for the past 24 hours, 7 days, or 30 days.  
+Known IOCs | Displays a pie chart of the known IOCs for which Threat Monitoring checks. The chart displays known IOCs divided into file hashes and YARA rules. This widget also displays the time at which the known IOCs were updated.  
+Anomaly Detection | Displays the total percentage of anomalous and non-anomalous objects for the past 24 hours, 7 days, and 30 days.  
+Threat Monitoring | Displays the total percentage of objects with and without threats for the past 24 hours, 7 days, and 30 days.This widget is visible when Threat Monitoring is enabled. Threat Monitoring is available as part of the Rubrik Enterprise edition.  
+Timeline Analysis | The chart shows the number of anomalies and threats found over the past 7 days and 30 days.

Data_Threat_Analytics_events_1.md

@@ -0,0 +1,15 @@
+# Data Threat Analytics events
+
+Source: https://docs.rubrik.com/en-us/saas/saas/ri_events.html
+
+---
+
+# Data Threat Analytics events
+
+Data Threat Analytics provides filters and real-time search capabilities that can be used to find specific events.
+
+When events are enabled, Data Threat Analytics sends an alert email when an anomaly is detected. The alert email contains a link to RSC. Accessing the link allows you to perform further investigation and, if necessary, recover files. The recovery process allows you to replace only the affected data without requiring that you perform a new analysis of the entire data set.
+
+Click on a Data Threat Analytics event to view the time line of snapshots taken for a specific time range, examine the file system of a series of snapshots, and determine approximately when the ransomware attack occurred. From this view, select the snapshot with the most recent clean versions of the files that were identified as compromised. Those files can be used as the starting point for file recovery.
+
+To support RBAC, CSV file downloads are only available from the Anomalies page and the anomaly details page. When you click Download CSV, RSC prepares a secure link for the file and displays a message about the download. You can also visit the File Preparation Center to access the downloaded file.

Downloading_and_installing_Rubrik_CDM_1.md

@@ -0,0 +1,121 @@
+# Downloading and installing Rubrik CDM
+
+Source: https://docs.rubrik.com/en-us/saas/install/download_install_cdm_on_appliance_nodes.html
+
+---
+
+# Downloading and installing Rubrik CDM
+
+Before you set up your Rubrik cluster, you can install a version of Rubrik CDM that is different from the one already installed on the Rubrik appliance nodes. This involves downloading the software, transferring it to one of the nodes, and running the installation.
+
+## About this task
+
+Rubrik appliance nodes are shipped with a recent major GA release package already installed. However, you will often want to install a more recent version of Rubrik CDM before you set up a new cluster. Or you may want to install a specific version on a new node before you add the node to an existing cluster.
+
+## Procedure
+
+  1. Download the Rubrik CDM installation package from the [Rubrik Support portal](https://support.rubrik.com/) to a computer with network access to the Rubrik appliance nodes.
+
+Part of the download process involves accepting the EULA. To be able to read and accept the EULA, you must disable the pop-up blocker setting in your web browser.
+
+When downloading a installation package for a new a node that you are adding to a running Rubrik cluster, select the installation package that contains the same version of Rubrik CDM that is on the running Rubrik cluster.
+
+  2. Unzip the package.
+
+The zip file contains an installation zip file and a signature file:
+     * rubrik-image-xyz.tar.gz
+     * rubrik-image-xyz_tar.gz.sig
+
+Where xyz is the release and patch number.
+
+  3. Use SSH over IPv6 to connect to the node.
+
+`ssh -6 admin@node_serial_number.local`
+
+Where `node_serial_number` is the serial number of the node. You can retrieve the serial number of the cluster node from the sticker attached to the node or by connecting directly to the node and running network ifconfig from the Rubrik CLI.
+
+  4. At the username prompt, enter `admin`.
+  5. At the password prompt, enter `rubrik`.
+
+The Rubrik CLI prompt appears.
+
+  6. In the SSH session, enter the version-dependent command to view the IP address of the node.
+
+For Rubrik CDM version 5.0.4 and later, enter:
+         
+         network ifconfig
+
+For versions of Rubrik CDM earlier than 5.0.4, enter:
+         
+         ifconfig bond0
+
+Keep the SSH session open to use later in this task.
+
+If cluster setup was previously run on the node, the IP address that appears will be an IPv4 address. If this is the first time you are configuring the node, the IP address will be an IPv6 address. The command also displays the interface name.
+
+  7. In a new terminal session, use SFTP to connect to the new node.
+
+For an IPv6 address, at the prompt, enter:
+         
+         sftp adminstaging@[ipv6address]%interface
+
+Where ipv6address is the IPv6 address and interface is the interface name determined in a previous step. For example:
+         
+         sftp adminstaging@[fe80::ae1f:6bff:fe55:8c77]%bond0
+
+For an IPv4 address, at the prompt, enter:
+         
+         sftp adminstaging@ipv4address
+
+Where ipv4address is the IPv4 address determined in a previous step. For example:
+         
+         sftp [email protected]
+
+  8. When prompted, enter the password.
+
+The password is `rubrik`.
+
+  9. Use SFTP to upload the installation package to the node.
+
+At the prompt, enter:
+         
+         put install-package /upgrade/
+
+Where install-package is the name of the installation package.
+
+  10. Use SFTP to upload the signature file to the node.
+
+At the prompt, enter:
+         
+         put sig-file /upgrade/
+
+Where sig-file is the name of the signature file.
+
+  11. Return to the SSH session and start the software installation.
+
+Enter: 
+         
+         cluster install start
+
+A list of available versions of the CDM software appears.
+
+  12. When prompted, enter the number assigned to the software version that you want to install.
+
+A list of the available nodes appears.
+
+  13. When prompted, select the number assigned to a node that you want the software installed on.
+
+The installation script installs the software on the selected node and displays the list of nodes again, with an asterisk by the entry for each node that has the software successfully installed.
+
+  14. Repeat the previous step until all of the nodes that you want the software on are listed with an asterisk.
+  15. **Optional:** To view the installation log, enter:
+
+`support log_view installer.log`
+
+## Results
+
+The installation script installs the selected software on all of the selected nodes.
+
+## What to do next
+
+After successfully completing the software installation process, perform the system setup task.

Downloading_quarantined_files_for_forensic_analysis_1.md

@@ -0,0 +1,46 @@
+# Downloading quarantined files for forensic analysis
+
+Source: https://docs.rubrik.com/en-us/saas/saas/downloading_quarantined_files_analysis.html
+
+---
+
+# Downloading quarantined files for forensic analysis
+
+Download quarantined files to examine and analyze them for malicious content.
+
+## Before you begin
+
+Ensure that you have a user account with permissions to add files to quarantine and remove files from quarantine.
+
+## Procedure
+
+  1. Log in to RSC.
+  2. Click  and select **Data Threat Analytics**.
+
+The Data Threat Analytics dashboard appears.
+
+  3. Click Hunts.
+
+The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact.
+
+  4. Click the threat hunt of interest.
+
+If added to quarantine, the quarantined objects are listed along with details of their location, files matched, and match type.
+
+  5. Click an object to view the files in that object.
+  6. Select the files to download.
+  7. Click  and select Download For Forensics.
+
+The Download for Forensics dialog box appears.
+
+  8. **Optional:** Click the snapshot column to choose any other non-expired snapshot containing the file.
+
+By default, the Download For Forensics wizard selects the latest non-expired snapshot for each file.
+
+  9. Click Download.
+
+Downloading the files can be dangerous if these files are malicious. Exercise caution to keep your systems safe.
+
+## Results
+
+RSC downloads the files as specified.

Getting_started_with_RSC_1.md

@@ -0,0 +1,15 @@
+# Getting started with RSC
+
+Source: https://docs.rubrik.com/en-us/saas/saas/common/getting_started_with_rsc.html
+
+---
+
+# Getting started with RSC
+
+To start using Rubrik Security Cloud, add authorized user accounts before adding Rubrik clusters.
+
+Rubrik sets up the initial user account for the RSC domain and sends an email invitation to the primary owner from this account. After setting up the initial user account, the owner can invite other users to set up accounts on the domain.
+
+Any user account in the RSC domain with cluster-management permissions can add Rubrik clusters to the domain.
+
+RSC uses HTTPS to transmit data between RSC and Rubrik clusters. RSC requires that each Rubrik cluster enable outbound port 443 in both firewall and proxy settings.

Guidelines_for_choosing_a_strong_password_1.md

@@ -0,0 +1,34 @@
+# Guidelines for choosing a strong password
+
+Source: https://docs.rubrik.com/en-us/saas/install/guidelines_strong_password.html
+
+---
+
+# Guidelines for choosing a strong password
+
+When choosing a password, you are required to follow the guidelines recommended by Rubrik to set a strong password that is difficult to guess or extract through a password cracker application, but is something that is easy to remember.
+
+When choosing a password, the goal is to make it difficult to guess but easy to remember.
+
+Rubrik recommends avoiding passwords with the following criteria:
+
+  * Single words that can be found in a dictionary.
+  * Common passwords, such as passw0rd, letmein, or abc123.
+  * Repeated characters, such as aaaa or 2222.
+  * Character sequences, such as abcd or 1234.
+  * L33t speak, where numbers and symbols are used in place of letters, for example, 3 for e, @ for a, and $ for s.
+  * Patterns made up of adjacent keys on a keyboard, such as qwerty or ujm.
+
+You are required to incorporate the following characteristics to make a password difficult to guess but easy to remember:
+
+  * Long strings (up to 1000 characters) of uncommon, unrelated words combined in a sequence, such as CorrectHorseBreadStaple. Rubrik clusters do not support passwords longer than 1000 characters.
+  * Unexpected caPitalizAtion.
+  * Numbers at the beginning or middle of the password or distributed throughout the password.
+
+As most users put a number at the end of their password, you must increase unpredictability by putting it at the beginning or in the middle, or distributing numbers throughout the password.
+
+  * A series of short keyboard patterns with lots of turns.
+
+A turn corresponds to a change of direction on the keyboard from one character to the next. A turn can also refer to the gap between pattern segments in the password.
+
+To make the password easy to remember, you can try a long password (up to 1000 characters) made up of a series of dictionary words that are not commonly combined in a sequence, and include one or more numbers.

Identities_in_Identity_Resilience_1.md

@@ -0,0 +1,32 @@
+# Identities in Identity Resilience
+
+Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_identitites.html
+
+---
+
+# Identities in Identity Resilience
+
+The identities page in Identity Resilience provides visibility into identities discovered in your environment.
+
+The Identities page within Identity Resilience provides a centralized and comprehensive view of all identities, both human and non-human, across your hybrid identity environment. This page is crucial for understanding the identity landscape and assessing associated risks.
+
+The Identities page offers a high-level summary of total identities discovered and the number of identities in your hybrid identity environment.
+
+RSC organizes identities into distinct categories, accessible through tabs for focused analysis:
+
+  * All Identities: Displays a complete list of every discovered identity.
+  * Users: Focuses specifically on human user accounts.
+  * Groups: Lists security and distribution groups.
+  * Service Accounts: Highlights non-human identities often used by applications and services such as Group Managed Service Accounts (gMSA), Standalone Managed Service Accounts (sMSA), and enterprise apps.
+
+The Identities page is important for:
+
+  * Visibility: Gaining a complete inventory of all identities and their characteristics.
+  * Identity insights: Quickly identifying identities that are at risk, privileged, or have access to highly sensitive data.
+
+Note:
+
+The highly sensitive data is available only if you have the DSPM license enabled.
+
+  * Policy enforcement: Understanding which identities violate defined security policies.
+

Identity_Resilience_1.md

@@ -0,0 +1,17 @@
+# Identity Resilience
+
+Source: https://docs.rubrik.com/en-us/saas/identity_resilience/identity_resilience.html
+
+---
+
+# Identity Resilience
+
+Rubrik Identity Resilience secures, monitors, and recovers the Identity Providers.
+
+Identity Resilience in Rubrik Security Cloud (RSC) offers protection services for identities in hybrid environments and safeguards the identity infrastructure in an organization. Identities, both human and non-human, are the most common entry points for cyberattacks, and any form of compromise in the identity infrastructure can cripple the ability of an organization to recover from a breach.
+
+Identity Resilience comprises security and recovery of identities in your hybrid identity infrastructure. Identity Resilience requires purchasing the Rubrik Identity Resilience License.
+
+Identity Resilience provides extensive capabilities, including protection, active risk identification, and robust remediation. It simplifies managing complexities in hybrid identity environments and addresses the increasing instances of cyberattacks, thereby minimizing the risks of identity compromise and data breaches. Additionally, it offers real-time monitoring to detect critical changes with Active Directory (AD), including modifications to privileged group membership and Group Policy Objects (GPOs). This enables immediate awareness of crucial security events.
+
+Identity Resilience provides automated, clean-room recovery, enabling swift restoration of compromised identities, and minimizes downtime. It also proactively mitigates risks by identifying risky privilege escalations and problematic access combinations. When combined with Data Security Posture Management (DSPM), Identity Resilience provides a holistic view of both data and identity, significantly strengthening the overall data security posture.

Identity_Resilience_reports_1.md

@@ -0,0 +1,28 @@
+# Identity Resilience reports
+
+Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_reports.html
+
+---
+
+# Identity Resilience reports
+
+The Identity Resilience Reports page offers comprehensive analytics and actionable insights into your identity security posture. It provides various report templates for protection status, identity violations, audit trails, and operational activities across Identity Providers.
+
+The Reports page in Rubrik Identity Resilience serves as the central hub for generating and managing analytical reports that provide deep insights into your identity security posture, protection status, and operational activities across your hybrid identity environments. This feature is crucial for compliance, auditing, risk assessment, and demonstrating the effectiveness of your identity resilience strategy.
+
+The page aggregates various reporting capabilities, allowing administrators to access predefined reports relevant to their specific needs. RSC organizes reports into categories, enabling users to quickly navigate to relevant areas of interest.
+
+You can generate the following reports for Identity Resilience:
+
+  * Protection
+  * Protection Tasks Details
+  * Object Capacity
+  * SLA Audit
+  * Object Audit
+  * Recovery Tasks Details
+  * Event
+  * Identity Violations
+
+The Identity Violations report analyzes various identity-related security risks.
+
+The reports can transform raw operational and security data from your identity infrastructure into digestible, insightful formats, empowering organizations to make data-driven decisions regarding their identity resilience posture.

Identity_summary_1.md

@@ -0,0 +1,37 @@
+# Identity summary
+
+Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_identity_summary.html
+
+---
+
+# Identity summary
+
+RSC provides a summary of an individual identity and insights about various components of an identity.
+
+The identity summary overview page provides a detailed, centralized view of different aspects of a specific identity and activity within your hybrid environment. It serves as a single source for deep-dive investigations into any user, group, or service account. It also displays the essential attributes such as identity type, unique identifier, and current status.
+
+## Identity summary graph
+
+A dynamic graph illustrates the relationships of a specific identity within the environment and highlights immediate security concerns. This includes summarized insights such as risk status, privilege levels, and authentication posture, along with real-time counts of identity violations and alerts.
+
+For privileged identities, the graph also provides insights into their associated privileged memberships or roles.
+
+## Policy Violations
+
+The policy violations widget displays details of the violations associated with the identity and categorizes the violations based on severity.
+
+On the right, specific policy violations associated with the identity are detailed. This provides direct insight into non-compliance, alongside information about its data access by sensitivity, if available.
+
+## Snapshot Based Vulnerabilities Summary
+
+RSC provides a time-series trend graph that visually tracks the vulnerabilities or overall security posture of an identity over time. This allows administrators to observe historical trends, identify changes, and assess improvements or deteriorations in security state of the identity.
+
+RSC updates the vulnerabilities graph using the snapshot of the Identity Provider (IdP) object. When there are multiple snapshots of the IdP object in a day, the graph is updated only once after the last snapshot.
+
+## Data Access by Sensitivity
+
+Note:
+
+This requires a DSPM license.
+
+The data access by sensitivity widget provides information about the access to sensitive data, categorized by its sensitivity level. When data is available, it offers insights into the potential blast radius if the identity were compromised, based on data context.

Jumbo_frame_support_1.md

@@ -0,0 +1,31 @@
+# Jumbo frame support
+
+Source: https://docs.rubrik.com/en-us/saas/cdm/jumbo_frame_support.html
+
+---
+
+# Jumbo frame support
+
+For Rubrik CDM versions 9.4 and later, you can set the value for the maximum transmission unit to a maximum value of 10000, instead of the default value of 1500. This larger unit size is called jumbo frames.
+
+You can use the Rubrik CLI to set the maximum transmission units (MTUs) for Rubrik CDM versions 9.4 and later to a maximum of 10000 bytes instead of the default value of 1500 bytes. This larger MTU size, called jumbo frames, provides a more efficient and much faster network throughput. The typical value for jumbo frames is 9000.
+
+Rubrik supports changing the MTU value for a Rubrik cluster only on bootstrapped physical machines, but not on cloud clusters. Changing the MTU is a cluster-wide parameter. If you set the MTU value on a node for an interface, this value applies to all the nodes in the cluster for that interface. If the Rubrik cluster includes a VLAN interface, this interface inherits the MTU value from the corresponding parent interface.
+
+Changes to the MTU value are persisted across:
+
+  * Node and cluster reboots
+  * Cluster upgrades
+  * Node additions 
+
+The MTU value from the Rubrik cluster is applied to the added node.
+
+  * Node replacement 
+
+The MTU value from Rubrik cluster is applied to the replacement node.
+
+Changes to the MTU value are not persisted across:
+
+  * Node resets
+  * Operations that change the IP address
+

Key_features_of_Identity_Resilience_1.md

@@ -0,0 +1,46 @@
+# Key features of Identity Resilience
+
+Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_key_features.html
+
+---
+
+# Key features of Identity Resilience
+
+RSC provides unified identity management, identity protection, and identity security for human and non-human identities in hybrid identity environments.
+
+Rubrik Identity Resilience is a critical product offering designed to provide comprehensive security and recovery for the identity infrastructure in hybrid identity environments.
+
+The key features of Identity Resilience include:
+
+## Hybrid identity protection and recovery
+
+  * Scope: Secures identities in complex hybrid setups.
+  * Automated discovery and protection: RSC automatically discovers AD domains, domain controllers (including FSMO roles, DNS, DHCP services), and Microsoft Entra ID tenants and objects for streamlined protection.
+  * Recovery: Offers automated, orchestrated recovery workflows to restore AD domain controllers, AD forests, and Microsoft Entra ID tenants quickly after attacks, reducing downtime.
+  * Clean-room recovery: Restores AD identities in a secure, isolated environment to prevent attacks by malware or persistent threats.
+  * SLA-based management: Applies defined SLA Domains for consistent backup frequency, retention, replication, and archival policies across your identity infrastructure.
+  * Granular restoration: Recovers specific AD or Microsoft Entra ID objects, such as users, groups, and service accounts, without full system rollback.
+  * Simplified process: Reduces manual recovery steps and accelerates restoration.
+
+## Real-time monitoring and alerts
+
+  * Tamper-resistant monitoring: Provides real-time tracking of critical changes within AD.
+  * Privilege change tracking: Monitors additions or removals of users and groups from privileged AD groups, flagging potential escalations or unauthorized de-provisioning.
+  * GPO modification alerts: Immediately identifies and alerts on any changes to Group Policy Objects (GPOs), which are critical for maintaining security configurations.
+  * Notifications: Enables management of notification channels and email alerts for detected events.
+  * Rapid response: Enables early detection and faster response to identity-based threats.
+
+## Comprehensive risk analysis
+
+  * Unified visibility: Provides a single dashboard to monitor human identities, such as user accounts and groups, and non-human identities, such as service accounts.
+  * Risk detection: Utilizes risk policies aimed at detecting security gaps across your identity and identity infrastructure configurations, enabling proactive remediation.
+  * Actionable remediation: Detects security violations and provides workflows to drive their remediation through IT Service Management (ITSM) integration, remediation guidance, and in-app remediation actions to close security gaps directly from RSC.
+
+## Identity and data context integration
+
+This requires a DSPM license.
+
+  * Holistic view: Combines identity and sensitive data context for better prioritization of identity risks, identifies highly sensitive identities that require additional security measures, and assesses the potential blast radius of a compromised identity.
+  * Time-series data: Tracks identity and access changes over time for continuous monitoring and historical analysis.
+  * Enhanced threat investigation: Correlates identity risks with data access patterns to identify and respond to threats faster.
+

Legal_Notices_2.md

@@ -0,0 +1,29 @@
+# Legal Notices
+
+Source: https://docs.rubrik.com/en-us/saas/reuse/notices.html
+
+---
+
+# Legal Notices
+
+## Copyright
+
+Copyright © 2025 Rubrik, Inc.
+
+All rights reserved. This document may be used free of charge. Selling without prior written consent is prohibited. Obtain permission before redistributing. In all cases, this copyright notice and disclaimer must remain intact.
+
+THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
+
+COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF.
+
+## Trademarks
+
+Registered in the U.S. Trademark Office
+
+Rubrik, the Rubrik graphic, and Datos IO are registered trademarks of Rubrik, Inc. in the U.S. and other countries.
+
+## Data Security Posture Legal Notices
+
+By using the Data Security Posture application, you understand and acknowledge that the pre-existing Policies and Analyzers of Data Security Posture contain general suggestions for data elements and formats based on common data sets and formats. The suggested data elements and formats in Data Security Posture are not intended to be a comprehensive or exhaustive list of data elements and formats regulated by the GDPR, CCPA or any other applicable laws and regulations. We also do not guarantee that your Data Security Posture search results will include every instance of each data element and format within your data set. We strongly recommend that you consult legal counsel for specific advice regarding compliance with applicable laws and regulations.
+
+Data Security Posture is designed to assist customers with identifying certain data elements and formats and should not be solely relied upon to identify all data elements and formats of a certain type for any purpose, including legal or compliance.

Polaris_to_RSC_upgrade_1.md

@@ -0,0 +1,28 @@
+# Polaris to RSC upgrade
+
+Source: https://docs.rubrik.com/en-us/saas/install/upgrade_to_rubrik_security_cloud.html
+
+---
+
+# Polaris to RSC upgrade
+
+Rubrik Security Cloud provides a unified user interface to manage all your Rubrik tasks.
+
+Upgrading to Rubrik Security Cloud (RSC) provides:
+
+  * Global dashboard for an overview of data health and security
+  * Data Security Command Center (DSCC) to identify security gaps and provide recommendations for improving data security status
+  * Cluster dashboard offering meaningful insights into individual cluster health
+  * Unified user interface for managing all data center, cloud, and SaaS workloads
+  * Global search capability across RSC
+  * Ability to create and schedule custom reports or use predefined reports
+
+When you login to the Polaris web UI, a dialog box appears on the screen, prompting you to upgrade to the RSC experience. The upgrade dialog box provides an overview of the RSC upgrade and its capabilities. The dialog box does not prevent you from performing any operations. To learn more about the upgrade, you can watch the overview video or refer to the RSC upgrade documentation.
+
+The RSC upgrade is instantaneous and does not need any scheduled downtime. Rubrik cluster backups will continue as configured. Once upgraded, you can use RSC for daily operations. You can also upgrade SLA Domains created on a Rubrik cluster to RSC SLA Domains as required for centralized management.
+
+Limitations of RSC management are as follows:
+
+  * Configuring the two-person rule (TPR) for changes or actions cannot be completed using RSC. These actions require Rubrik CDM workflows.
+  * Adding NAS systems managed in Rubrik CDM to RSC will trigger a new full backup and cause duplicate data protection of the NAS system. You can add the NAS host to RSC when the storage overhead is acceptable or continue to manage NAS hosts using Rubrik CDM.
+

Quarantine_overview_1.md

@@ -0,0 +1,59 @@
+# Quarantine overview
+
+Source: https://docs.rubrik.com/en-us/saas/saas/quarantine.html
+
+---
+
+# Quarantine overview
+
+The Quarantine feature in Data Threat Analytics isolates potentially malicious files or objects to allow seamless data recovery and to avoid reinfection.
+
+Data recovery risks restoring malware, ransomware, or other unwanted applications. To restore data rapidly without compromising the recovered systems, you must:
+
+  * Restore to a pre-malware infection state.
+  * Restore only uninfected files.
+
+By quarantining the snapshots that contain malware, you can quickly isolate potentially malicious files and identify healthy snapshots to use for performing a full system restore.
+
+## Quarantine operation and file version
+
+When you quarantine a file from a threat hunt or Threat Monitoring match, the system creates a quarantine operation. A quarantine operation is expressed as the unique combination of the object, file path, and file version. This operation fundamentally blocks the recovery of a specific file version. The file version is defined by its modification time (MTime). The MTime is a unique metadata stamp that records the exact date and time the file was last modified on the source object. This precision ensures you block the recovery of the specific malicious content that existed at that exact point in time.
+
+The quarantine operation applies to that specific file version across all existing and future snapshots for that object, including any replica and archival copies. This is the recommended behavior, as the operation uses file version metadata to automatically apply the quarantine to all current and future snapshots. If the file is modified and its MTime changes, the new version is not covered by the original operation.
+
+Note:
+
+In some cases, if the file version information is unavailable, such as with older Threat Monitoring matches or a threat hunt performed on Rubrik clusters running a version earlier than 9.2.3, the system will fall back to a limited quarantine scope that only affects the specific snapshots where the match was detected. To initiate the recommended full-scope quarantine for such a file, run a new threat hunt on the object to ensure the necessary file version metadata is populated, and then quarantine the file again.
+
+## Quarantine processing and recovery restrictions
+
+It is important to understand the following concepts regarding the quarantine mechanism and their impact on recovery:
+
+  * Quarantine scope: Quarantining a file implicitly quarantines the file path and the snapshot. The operation applies to all snapshots, including future snapshots of the object that contain the relevant file path and version.
+  * Quarantine processing: When an object has active quarantine operations, RSC processes every snapshot to determine if the relevant file version exists. Until this process is complete, the snapshot is marked as Quarantine processing. Recovery is automatically blocked for any snapshot in this state.
+
+Snapshots are marked as Quarantine processing in two primary cases:
+
+  * When a new snapshot first arrives at RSC, if the associated object has any active quarantine operations. Processing of the new snapshot usually completes in seconds to minutes, but can take up to 30 minutes in certain conditions.
+  * When a new quarantine operation or a remove from quarantine operation is applied to the object. All snapshots are temporarily reset to the Quarantine processing status and reprocessed. Processing of all affected snapshots usually completes in seconds to minutes, but can take up to 30 minutes in certain conditions.
+
+Recovery block: Quarantining a file or object blocks all image-level recovery options for the affected snapshot, including Live Mount, Export, and Instant Recovery. The following exceptions apply:
+
+  * Exception for forensics: The quarantined data remains accessible for security operations only by using the password-protected Download for Forensics feature.
+  * RBAC override: This recovery block is automatically bypassed for users who have the Recover From Quarantine RBAC permission.
+
+## Supported workloads
+
+RSC supports quarantining on the following objects:
+
+  * VMware virtual machines
+  * Linux filesets
+  * Windows filesets
+  * Nutanix AHV virtual machines
+  * Hyper-V virtual machines
+  * Volume groups
+  * NAS filesets
+  * Kubernetes virtual machines
+  * Kubernetes protection sets
+
+Using the Quarantine feature requires access to the Data Protection dashboard, the Data Threat Analytics dashboard, and either the threat hunt or Threat Monitoring feature. For detailed instructions on how to configure user permissions, refer to the [RBAC Permissions for Quarantine](rbac_permissions_for_quarantine.html "RBAC privileges are required to remove files or objects from quarantine, bypass quarantine, and download files for forensic analysis.") topic.

Quarantining_matched_files_or_objects_1.md

@@ -0,0 +1,45 @@
+# Quarantining matched files or objects
+
+Source: https://docs.rubrik.com/en-us/saas/saas/quarantining_matched_objects_or_files.html
+
+---
+
+# Quarantining matched files or objects
+
+Quarantine a matched file or object indicated in a threat hunt to separate potentially malicious objects or files before proceeding with recovery.
+
+## Before you begin
+
+Ensure that you have a user account with permissions to add files to quarantine and remove files from quarantine.
+
+## Procedure
+
+  1. Log in to RSC.
+  2. Click and select **Data Threat Analytics**.
+
+The Data Threat Analytics dashboard appears.
+
+  3. Click Hunts.
+
+The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact.
+
+  4. Click the threat hunt of interest.
+
+Quarantined objects are listed with details of their location, files matched, and match type.
+
+  5. **Optional:** Click an object to view the files in that object.
+  6. Select items at the object or file level and click Quarantine.
+
+Matched files are quarantined only on the snapshots where they were matched in the threat hunt and cannot be recovered. When the file exists in a previous or later snapshot, it might still be recoverable.
+
+Quarantining a file implicitly quarantines the snapshot. Snapshots with a matched file have limited recovery options unless they are removed from quarantine.
+
+The Quarantine Objects wizard shows the files selected for quarantine.
+
+  7. In the Quarantine Objects wizard, click Quarantine.
+
+When the total request size exceeds the limit, you can make further selections on a subsequent request.
+
+## Results
+
+RSC quarantines the file and provides no recovery options in any quarantined snapshot until the file is removed from quarantine. Users with the Recover From Quarantine permission can still download the file for forensics or perform image-level recovery options for the snapshot.

RBAC_privileges_for_quarantine_1.md

@@ -0,0 +1,28 @@
+# RBAC privileges for quarantine
+
+Source: https://docs.rubrik.com/en-us/saas/saas/rbac_permissions_for_quarantine.html
+
+---
+
+# RBAC privileges for quarantine
+
+RBAC privileges are required to remove files or objects from quarantine, bypass quarantine, and download files for forensic analysis.
+
+All Data Threat Analytics users can view quarantined objects and files. Additional threat containment privileges are required to: 
+
+  * Add files to quarantine and remove files from quarantine
+  * Bypass quarantine and continue with recovery, and download for forensics
+
+You can assign additional threat containment privileges from the Users and Roles page. The administrator and owner roles are assigned these privileges by default. You can also assign these additional privileges to custom roles.
+
+Privilege | Description  
+---|---  
+Add files to quarantine and remove files from quarantine | Users with this privilege can add files to quarantine and remove files from quarantine. The administrator and owner roles are assigned this privilege by default and this privilege can also be assigned to custom roles.  
+Recover quarantined files and snapshots | Users with this privilege can bypass quarantine and perform most recoveries for:
+
+  * Image-level recoveries such as Live Mount, Export, and Instant Recovery
+  * File-level recoveries from the Hunts page
+
+Users can only download quarantined files or folders containing quarantined files. Other file recovery options are not available for quarantined files.  
+  
+All users with permission to view a workload in the Data Protection room can view the snapshots quarantined for that workload, as well as the files quarantined in a particular snapshot, in the Data Protection object details page.

RSC_Data_Threat_Analytics_1.md

@@ -0,0 +1,17 @@
+# RSC Data Threat Analytics
+
+Source: https://docs.rubrik.com/en-us/saas/saas/ri_ransomware_monitoring.html
+
+---
+
+# RSC Data Threat Analytics
+
+RSC Data Threat Analytics provides Anomaly Detection and data recovery services on protected resources.
+
+Data Threat Analytics comprises Anomaly Detection, Threat Monitoring, Threat Hunting, and data recovery services on protected resources.
+
+Anomaly Detection identifies and analyzes anomaly events that can indicate a ransomware attack. When an attack is discovered, you can use Anomaly Detection to directly recover the original data. Anomaly Detection works in combination with other data security methods to provide an additional layer of protection.
+
+For each protected object, Anomaly Detection captures the changes in file system behavior and file content behavior that occur between snapshots. Anomaly Detection analyzes this information and provides a view of the changed behavior and changed content over time, when an incident has occurred. RSC retains the history of the metadata tracked by Data Threat Analytics for 30 days.
+
+Anomaly Detection does not support deep scanning for encryption for NAS Direct Archive.

RSC_Orchestrated_Application_Recovery_1.md

@@ -0,0 +1,32 @@
+# RSC Orchestrated Application Recovery
+
+Source: https://docs.rubrik.com/en-us/saas/saas/oar.html
+
+---
+
+# RSC Orchestrated Application Recovery
+
+The Orchestrated Application Recovery feature automates end-to-end recovery as well as disaster recovery and application migration from an on-premises data center to a secondary recovery site.
+
+Orchestrated Recovery uses Recovery Plans to group virtual machines for proactive testing and reporting and for production recovery situations. RSC creates Recovery Plans for a group of virtual machines and their associated target resource specifications for recovery. Orchestrated Recovery options to recover objects using a Recovery Plan include the following:
+
+  * Disaster recovery
+  * Cyber recovery
+  * In-place recovery
+
+You can also initiate a cyber recovery as needed without a Recovery Plan by using the Cyber Recovery wizard.
+
+Orchestrated Recovery supports the following recovery types. You can filter for a recovery point based on Anomaly Detection and Quarantine results.
+
+You can use Orchestrated Recovery for the following workloads:
+
+  * VMware virtual machines
+  * AHV virtual machines
+  * Azure virtual machines
+
+Only Cyber recovery is available for Azure virtual machines.
+
+  * AWS EC2 instances
+
+Only Cyber recovery is available for AWS EC2 instances.
+

Removing_a_quarantined_file_or_object_1.md

@@ -0,0 +1,44 @@
+# Removing a quarantined file or object
+
+Source: https://docs.rubrik.com/en-us/saas/saas/removing_quarantined_file_or_object.html
+
+---
+
+# Removing a quarantined file or object
+
+Remove a quarantined file or object to make it available for recovery.
+
+## Before you begin
+
+Ensure that you have a user account with permissions to add files to quarantine and remove files from quarantine.
+
+## Procedure
+
+  1. Log in to RSC.
+  2. Click  and select **Data Threat Analytics**.
+
+The Data Threat Analytics dashboard appears.
+
+  3. Click Hunts.
+
+The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact.
+
+  4. Click the threat hunt of interest.
+
+When added to quarantine, the quarantined objects are listed with details of the location, files matched, and match type.
+
+  5. **Optional:** Click an object to view the files in that object.
+  6. Select items for quarantining at the object or file level.
+  7. Click  select Remove from Quarantine.
+
+Releasing the selected files from quarantine removes the restrictions placed on those files. All matched snapshots in the threat hunt that contain the selected files then have full recovery options.
+
+The Remove from Quarantine wizard shows the files you selected for removal from quarantine.
+
+  8. In the Remove from Quarantine wizard, enter `REMOVE` to confirm and then click Remove.
+
+When the total request size exceeds the limit, you can make further selections on a subsequent request.
+
+## Results
+
+RSC removes the selected objects from quarantine and makes the object available for recovery.

Rubrik_CDM_software_upgrade_1.md

@@ -0,0 +1,36 @@
+# Rubrik CDM software upgrade
+
+Source: https://docs.rubrik.com/en-us/saas/saas/rbk_cdm_software_upgrade.html
+
+---
+
+# Rubrik CDM software upgrade
+
+To take advantage of the latest features and improvements, you can upgrade your Rubrik CDM software running on your Rubrik clusters to the latest version.
+
+An upgrade is an operation for updating an older software version to a newer version, representing significant changes or improvements. Rubrik CDM software upgrades offer considerable changes and new functionality over previous versions, effectively superseding them.
+
+Some key advantages of upgrading your Rubrik CDM software to the latest version are as follows:
+
+  * Maintaining business continuity and preventing unnecessary failures.
+  * Benefiting from essential security updates, new features, and integration with current technology trends and advancements, giving your business a competitive advantage.
+  * Safeguarding your systems and applications from viruses, spyware, and other malicious software that can harm or steal data or cause lengthy delays in problem resolution.
+  * Enhancing the quality of user experiences.
+
+If you are considering upgrading your Rubrik CDM software, Rubrik recommends that you evaluate the latest version available. Rubrik maintains a comprehensive Compatibility Matrix document that outlines which systems, protocols, and interfaces are supported for each product release. You can also check the Release Notes for the latest CDM software version to learn about new features, enhancements, and resolved issues. This way, you can ensure you are making the best choice for your needs.
+
+Rubrik follows the N-2 lifecycle policy, which supports the three most recent major releases (N, N-1, and N-2) of Rubrik CDM software. Each major release comes with a minimum support duration of 18 months. The Rubrik CDM Software Support Lifecycle documentation provides more information about the lifecycle policy.
+
+The Rubrik CDM Upgrades page provides all the information you need to make an informed decision about upgrading the CDM software. Some critical pieces of information you can gather include:
+
+  * Checking the installed CDM software versions for your Rubrik clusters.
+  * Opening the Rubrik CDM Releases table to view details about the major release, its release notes, release adoption, release dates, latest minor release, Rubrik CDM software support policy, and Compatibility Matrix documentation.
+
+After you have decided to upgrade the Rubrik CDM software, you need to consider:
+
+  * Choosing between a rolling upgrade and a fast upgrade.
+  * Reviewing the list of prerequisites and prechecks for your chosen upgrade type and ensuring you fulfill them for a successful upgrade.
+  * Selecting RSC or Rubrik CLI to perform the upgrade.
+
+Rubrik does not support using CLI commands to upgrade Rubrik clusters to the Rubrik CDM software version 9.0 or later.
+

Rubrik_MFA_with_TOTP_1.md

@@ -0,0 +1,17 @@
+# Rubrik MFA with TOTP
+
+Source: https://docs.rubrik.com/en-us/saas/saas/common/rsc_rmfa_totp.html
+
+---
+
+# Rubrik MFA with TOTP
+
+The Rubrik two-step verification feature uses time-based one-time passwords in addition to the user login credentials to enforce multi-factor authentication on user accounts.
+
+Rubrik two-step verification is an implementation of 2FA for Rubrik Security Cloud (RSC). You can enable Rubrik two-step verification to use 2FA mediated by time-based one-time password (TOTP), which provides an additional layer of authentication security. By using TOTP, Rubrik enforces multi-factor authentication (MFA) with the help of a single-use numeric code in addition to your login credentials. You can use an application running on your personal device, for example a smart phone, to generate the single-use numeric code. Rubrik two-step verification works with any TOTP application that complies with RFC 6238.
+
+MFA enforcement is mandatory for all local RSC user accounts. Administrators must enforce Rubrik two-step verification for users at the global level. When enforced, each user must configure Rubrik two-step verification on an individual basis.
+
+Note:
+
+MFA enforcement does not impact user accounts authenticated through SAML-based SSO authentication providers.

Rubrik_Security_Cloud_-_Offline_Recovery_1.md

@@ -0,0 +1,283 @@
+# Rubrik Security Cloud - Offline Recovery
+
+Source: https://docs.rubrik.com/en-us/latest/offrec/index.html
+
+---
+
+[Rubrik CDM offline recovery](offrec/rubrik_offrec_or.html)
+
+In the unlikely event of a service disruption between the Rubrik cluster and RSC, Rubrik CDM version 9.2 and later can switch between running in recovery mode and in fully functional, read-write mode. 
+
+[Logging in to Rubrik cluster](offrec/logging_in_off_rec.html)
+
+Log in to Rubrik cluster to recover workloads when RSC is 
+
+[Logging out of the Rubrik cluster](offrec/logging_out_rsc_offrec_or.html)
+
+Log out of the Rubrik cluster.
+
+[Live Mounts in the Rubrik cluster](offrec/live_mounts_offrec.html)
+
+The Rubrik cluster displays a list of Live Mounts that are available for workload recovery.
+
+[The Rubrik cluster Events page](offrec/offrec_events_page.html)
+
+The Events page displays the events of the Rubrik cluster.
+
+[Viewing the Rubrik cluster inventory](offrec/viewing_rsc_offline_recovery_inventory.html)
+
+View the workloads inventory included with the Rubrik cluster.
+
+[SMB security in the Rubrik cluster](offrec/smb_security_or.html)
+
+With the SMB security, the Rubrik cluster provides security for SMB shares by requiring Active Directory authentication and enforcing SMB security.
+
+[Cyber Event Lockdown in Rubrik cluster](offrec/cyber_event_lockdown_or.html)
+
+When a suspected cyber attack, ransomware attack, or other event affecting data integrity impacts your environment, you can use Cyber Event Lockdown on the Rubrik cluster to protect the data.
+
+[Cluster details page in the Rubrik cluster](offrec/cluster_details_page_or.html)
+
+Information about Rubrik clusters and their configurations.
+
+[Viewing the cluster settings in the Rubrik cluster](offrec/viewing_the_cluster_settings.html)
+
+View the cluster settings for the Rubrik cluster.
+
+[Changing the cluster settings in the Rubrik cluster](offrec/changingl_cluster_settings.html)
+
+Change the general cluster settings for the Rubrik cluster.
+
+[Changing the network settings in the Rubrik cluster](offrec/changing_network_settings.html)
+
+Change the network settings for the Rubrik cluster.
+
+[Adding an NTP server to a Rubrik cluster](offrec/adding_ntp_server_cdm.html)
+
+Add an NTP server to the Rubrik cluster for network time synchronization.
+
+[Adding a VLAN to a Rubrik cluster](offrec/adding_vlan_cdm.html)
+
+Add a VLAN to the Rubrik cluster for a logical segmentation of networks.
+
+[Deleting a VLAN from a Rubrik cluster](offrec/deleting_vlans_offrec_or.html)
+
+Delete a VLAN if multiple VLANs are associated with a Rubrik cluster.
+
+[Pause and resume protection activity](offrec/pause_protection_activity_or.html)
+
+When you are performing maintenance activities on a Rubrik cluster, you can temporarily pause the protection activity and then resume it by using the pause and resume protection activity feature.
+
+[Support tunnel for Rubrik cluster](offrec/support_tunnels_or.html)
+
+Support tunnel allows authorized Rubrik Support engineers to gain secure, logged access to Rubrik clusters for diagnosis and resolution of hardware and software issues.
+
+[Checking RSC connectivity](offrec/checking_rsc_connectivity.html)
+
+Check the connectivity between RSC and the Rubrik cluster.
+
+[Creating a support bundle on Rubrik cluster](offrec/creating_a_support_bundle.html)
+
+Create a support bundle that Rubrik Support can use to evaluate any issues that occur during offline workload recovery.
+
+[Adding a static route in Rubrik cluster](offrec/adding_routing_table_cluster_or.html)
+
+Add a static route for a network destination in Rubrik cluster with other network details such as netmask, gateway, and interface for efficient network routing and better performance.
+
+[Deleting a static route from the Rubrik cluster](offrec/deleting_static_route_cluster_or.html)
+
+Delete an unnecessary static route from the routing table on Rubrik cluster.
+
+[Node Management](offrec/node_management_or.html)
+
+You can use Rubrik cluster to optimize the performance of the cluster nodes by adding nodes and setting up or removing disks.
+
+[Rubrik cluster workloads](offrec/offrec_workloads.html)
+
+Rubrik cluster securely manages and protects data from a wide variety of workload types.
+
+[File systems](offrec/filesystems/fs_filesystems_or.html)
+
+Rubrik cluster provides management and protection of file system data on supported Linux, Unix, and Windows hosts through filesets.
+
+[SQL Server databases](offrec/mssql/sql_server_databases_or.html)
+
+A Rubrik cluster provides data management and protection for Microsoft SQL Server databases.
+
+[AHV virtual machines](offrec/nutanix_ahv/virtual_machines_or.html)
+
+Rubrik cluster provides data management and protection for virtual machines deployed in a Nutanix Acropolis environment.
+
+[Managed Volumes and SLA Managed Volumes](offrec/managed_volumes/mv_managed_volumes_sla_managed_volumes_or.html)
+
+Managed Volumes in Rubrik cluster protect and manage data while SLA Managed Volumes schedule and initiate backups using an SLA Domain.
+
+[On-premises Active Directory](offrec/on_prem_ad/on_prem_active_directory_or.html)
+
+You can protect and recover on-premises Active Directory domains by using the protection services offered by Rubrik cluster.
+
+[NAS systems on Rubrik cluster](offrec/nas/nas_systems_or.html)
+
+Rubrik cluster manages and protects NFS and SMB shares on NAS systems for efficient data storage and retrieval.
+
+[Oracle databases on Rubrik cluster](offrec/oracle/oracle_databases_rsc_or.html)
+
+You an use Rubrik cluster to back up, archive, replicate, and recover Oracle databases.
+
+[VMware Cloud Director vApps](offrec/vcd/vmware_cloud_director_vapps_or.html)
+
+The Rubrik cluster provides SLA Domain protection and data management for VMware Cloud Director vApps.
+
+[Hyper-V virtual machines](offrec/hyper_v/hyperv_vm_or.html)
+
+The Rubrik cluster provides data management and protection for virtual machines that are deployed in a Microsoft Hyper-V environment. the Rubrik cluster can manage and protect virtual machines in an environment with multiple Hyper-V servers and virtual machines.
+
+[vSphere virtual machines](offrec/vsphere/vs_virtual_machines_or.html)
+
+Rubrik cluster provides data management and SLA Domain protection for virtual machines that are deployed in a VMware vSphere environment.
+
+[vCenter management](offrec/vsphere/vs_vcenter_management_or.html)
+
+The Rubrik cluster accesses virtual machine data through a connection with the VMware vCenter Server that manages the hypervisor running the virtual machine.
+
+[Windows volume groups](offrec/wvg/windows_volume_groups_or.html)
+
+A volume group is a Rubrik workload comprised of at least one data storage volume on a Windows host.
+
+[Archiving of data center workloads](offrec/archival/arch_dc_workloads_or.html)
+
+With a Rubrik cluster, you can recover your data from your data center archival locations in the event of a disaster or cyber event.
+
+[Archival Locations](offrec/archival/arch_loc_page_or.html)
+
+The Archival Locations page provides summary information about existing archival locations on the Rubrik cluster.
+
+[Connecting as a reader to the Rubrik cluster archival location](offrec/conn_as_reader_or_arch_loc.html)
+
+Connect to an Rubrik cluster archival location as a reader to recover snapshot data.
+
+[Disaster recovery using an archival location](offrec/archival/disaster_rec_using_arch_loc_or.html)
+
+Rubrik CDM supports recovering data from an existing archival location using a different Rubrik cluster than the Rubrik cluster that archived the data.
+
+[Azure archival locations](offrec/archival/arch_azure_or.html)
+
+With Rubrik cluster, you can connect as a reader to an existing Azure archival storage to read existing data to perform a recovery during a service disruption. The Azure archival storage was previously configured from a different Rubrik cluster.
+
+[Amazon S3 archival locations](offrec/archival/arch_amazon_s3_or.html)
+
+With Rubrik cluster, you can connect as a reader to an existing Azure archival storage to read existing data to perform a recovery during a service disruption. The Amazon S3 archival storage was previously configured from a different Rubrik cluster.
+
+[Google Cloud Platform archival locations](offrec/archival/arch_gcp_or.html)
+
+With the Rubrik cluster, you can connect as a reader to an existing Azure archival storage to read existing data to perform a recovery during a service disruption. The Google Cloud Platform archival storage was previously configured from a different Rubrik cluster.
+
+[NFS archival locations](offrec/archival/nfs_arch_loc_or.html)
+
+An NFS archival location is storage on an NFS server where you can archive snapshots from your Rubrik cluster. You must identify a specific location on the NFS server to serve as the archival location.
+
+[Object Store archival locations](offrec/archival/obj_store_archival_locations_or.html)
+
+With Rubrik cluster, you can connect as a reader to an existing Object Store archival storage configured from another cluster to read existing data to perform a recovery during a service disruption.
+
+[QStar tape archive](offrec/archival/archiving_qstar_tape_archive_or.html)
+
+QStar tape archive enables the Rubrik cluster to store data on tape for long-term retention and regulatory compliance using QStar Archive Manager on Windows servers.
+
+[User accounts for Rubrik cluster](offrec/security/security_or.html)
+
+Rubrik cluster provides RBAC and several methods for authenticating a user account.
+
+[Authentication for Rubrik cluster](offrec/security/cdm_authentication_or.html)
+
+The Rubrik cluster authenticates all login attempts.
+
+[Local authentication for Rubrik cluster](offrec/security/local_authentication_or.html)
+
+Local authentication methods control access to local accounts on the Rubrik cluster.
+
+[Roles for Rubrik cluster](offrec/security/roles_or.html)
+
+Roles help define privileges for user accounts on a Rubrik cluster. With the admin account, you can assign administrator roles that grant varying access permissions to user accounts for specific purposes.
+
+[Requirements for BIND user credentials for Rubrik cluster](offrec/security/requirements_for_bind_user_credentials_or.html)
+
+Rubrik CDM has specific requirements for BIND credentials.
+
+[LDAP authentication for Rubrik cluster](offrec/security/ldap_authentication_or.html)
+
+The Rubrik cluster uses LDAP to authenticate users who log in through the Rubrik cluster welcome screen.
+
+[Single Sign-on for Rubrik cluster](offrec/security/single_signon_or.html)
+
+Rubrik CDM supports single sign-on using the Security Assertion Markup Language 2.0 standard.
+
+[ADFS integration workflow for Rubrik cluster](offrec/security/cdm_adfs_integration_workflow_or.html)
+
+The workflow gives a high-level view of the tasks involved in configuring single sign-on with ADFS.
+
+[Okta integration workflow for Rubrik cluster](offrec/security/okta_sso_integration_workflow_or.html)
+
+The Okta integration workflow gives a high-level view of the tasks involved in configuring single sign-on with Okta.
+
+[Multifactor authentication for Rubrik cluster](offrec/security/multifactor_auth_or.html)
+
+Multifactor authentication is the practice of adding more factors to the basic authentication process. By using multifactor authentication, you can prevent unauthorized users from accessing your Rubrik clusters.
+
+[Certificate management for Rubrik cluster](offrec/security/certificate_management_or.html)
+
+Rubrik cluster Certificate Management provides a centralized dashboard to manage certificates for Rubrik cluster workflows.
+
+[Rubrik MFA with TOTP for Rubrik cluster](offrec/security/cdm_rmfa_totp_or.html)
+
+Rubrik MFA for Rubrik clusters uses time-based one-time passwords to provide secure authentication for local and LDAP users. Rubrik MFA does not apply for users authenticated via SAML-based SSO integrations.
+
+[CLI administrator role for Rubrik cluster](offrec/security/cli_administrator_role_or.html)
+
+As a CLI administrator, a Rubrik cluster user can connect to nodes in Rubrik clusters through the CLI SSH protocol.
+
+[Rubrik port specifications](ports/rubrik_port_specifications.html)
+
+Information about the ports that Rubrik clusters use.
+
+[Additional network requirements](ports/additional_network_requirement.html)
+
+To provide IPMI management information, Rubrik nodes must be able to receive packets sent from a local ping program.
+
+[Archiving ports](ports/archiving_ports.html)
+
+The Rubrik cluster requires a number of outbound ports for archiving.
+
+[Azure ports](ports/azure_ports.html)
+
+Configure the following ports for Azure virtual machines.
+
+[GCP ports](ports/gcp_ports.html)
+
+The Rubrik cluster requires specific ports to be configured for GCP virtual machines.
+
+[Kubernetes ports](ports/kubernetes_ports.html)
+
+The Rubrik cluster requires specific ports to be configured for Kubernetes clusters.
+
+[AWS ports](ports/aws_ports.html)
+
+The Rubrik cluster requires the following ports to be configured for AWS virtual machines.
+
+[Replication port information](ports/replication_port_information.html)
+
+Information about the assigned port number and behavior of the replication service. The replication service manages the incoming traffic for the Rubrik replication feature, which directs the management of replica snapshots or backups from a source Rubrik cluster to a target Rubrik cluster.
+
+[Legal Notices and additional resources](reuse/notices.html)
+
+Rubrik legal notices for this documentation, and topics with additional resources and information.
+
+[Legal Notices](reuse/notices.html)
+
+[Comments and suggestions](reuse/comments_suggestions.html)
+
+We welcome your comments and suggestions about our products and our product documentation.
+
+[Support](reuse/support.html)
+
+Use one of the following methods to contact Rubrik Support.

Rubrik_Security_Cloud_1.md

@@ -0,0 +1,57 @@
+# Rubrik Security Cloud
+
+Source: https://docs.rubrik.com/en-us/saas/index.html
+
+---
+
+[Setup](install/rsc_cluster_deployment.html)
+
+Rubrik CDM software can be installed on many different platforms, both physical and virtual. The software can run on a single node computer and on multiple node computing clusters.
+
+[Data Protection](saas/common/getting_started_with_rsc.html)
+
+Rubrik Security Cloud - Data Protection provides the core tools and features for protecting, managing, and analyzing your data.
+
+[Workloads](rubrik/supported_workloads.html)
+
+Rubrik Security Cloud - Data Protection securely manages and protects data from a wide variety of workload types.
+
+[Identity Resilience](identity_resilience/identity_resilience.html)
+
+Rubrik Identity Resilience is designed to protect, monitor, and recover identities, both human and non-human identities, in hybrid identity environments.
+
+[Data Threat Analytics](saas/ri_ransomware_monitoring.html)
+
+Rubrik Security Cloud Data Threat Analytics provides anomaly detection and data recovery services on protected resources such as VMware virtual machines, NAS, and Linux and Windows servers.
+
+[Data Security Posture](dspm/data_security_posture.html)
+
+Rubrik Security Cloud Data Security Posture enables organizations to find specific types of data within the data that has been indexed by Rubrik clusters.
+
+[Annapurna](ai/annapurna.html)
+
+Annapurna is an enterprise application for querying your protected data. It allows you to create custom chatbots that use advanced language models and retrieval-augmented generation to answer natural language questions about your data.
+
+[Orchestrated Application Recovery](saas/oar.html)
+
+Rubrik Security Cloud Orchestrated Application Recovery provides disaster recovery and application migration from an on-premises data center to a secondary recovery site.
+
+[Ruby](saas-ai/ruby_2.html)
+
+Ruby is an AI assistant designed to help you ask natural language questions to better understand and use Rubrik Security Cloud.
+
+[GraphQL API Playground](gql/api_playground_2.html)
+
+The API Playground is a tool that allows you to browse, explore, and run the GraphQL APIs of Rubrik Security Cloud.
+
+[Offline Recovery](https://docs.rubrik.com/en-us/latest/offrec/index.html)
+
+In the unlikely event that you cannot connect to Rubrik Security Cloud, you can use the offline recovery UI on your Rubrik clusters to perform basic recovery and maintenance.
+
+[Legal Notices and additional resources](reuse/notices.html)
+
+Rubrik legal notices for this documentation, and topics with additional resources and information.
+
+[Comments and suggestions](reuse/comments_suggestions.html)
+
+We welcome your comments and suggestions about our products and our product documentation.

Rubrik_Security_Cloud_service_types_1.md

@@ -0,0 +1,17 @@
+# Rubrik Security Cloud service types
+
+Source: https://docs.rubrik.com/en-us/saas/install/rsc_service_types.html
+
+---
+
+# Rubrik Security Cloud service types
+
+Rubrik Security Cloud offers two distinct service types, SaaS mode and software mode, which provide different sets of functionality.
+
+Rubrik Security Cloud (RSC) can be configured in SaaS mode or software mode.
+
+RSC in SaaS mode provides many benefits through a unified control plane across multiple Rubrik clusters. The benefits of SaaS mode include a common UI, security layer and RBAC, common policy management, and reporting. Rubrik Security Cloud in SaaS mode cannot be converted to the software mode.
+
+If Rubrik Security Cloud becomes temporarily unavailable, the Rubrik cluster UI offers a recovery mode to handle critical tasks such as restoring data from a backup.
+
+RSC in software mode provides standalone, on-premises access to Rubrik CDM for data protection and recovery. The software mode uses appliances provided by Rubrik or selected compatible hardware. RSC in software mode provides a UI on the Rubrik cluster for your management tasks.

Rubrik_Security_Cloud_workloads_1.md

@@ -0,0 +1,47 @@
+# Rubrik Security Cloud workloads
+
+Source: https://docs.rubrik.com/en-us/saas/rubrik/supported_workloads.html
+
+---
+
+# Rubrik Security Cloud workloads
+
+RSC securely manages and protects data from a wide variety of workload types.
+
+Supported workload types:
+
+  * [Active Directory forest](../adds/active_directory_forest.html "Rubrik Security Cloud offers protection services for the Active Directory forest hierarchy. You can protect and recover the entire forest hierarchy in the event of a disaster or ransomware attack.")
+  * [Active Directory domains and domain controllers](../adds/active_directory_domain_dc.html "You can protect and recover Active Directory domains and domain controllers by using the protection services offered by Rubrik Security Cloud.")
+  * [AHV virtual machines](../nutanix_ahv/ahv_virtual_machines.html "RSC provides data management and protection for virtual machines deployed in a Nutanix Acropolis environment.")
+  * [Amazon Web Services workloads](../saas/aws_workloads.html "RSC protects the following types of Amazon Web Services workloads: EC2 instances, EBS volumes, Amazon S3, Amazon RDS and Aurora databases, and Amazon DynamoDB.")
+  * [Azure DevOps](../azure_devops/azr_devops.html "RSC protects the data and resources of Azure DevOps projects and repositories within the Azure DevOps organization.")
+  * [Atlassian Jira](../jira/jira.html "To protect your Atlassian Jira data, you can back up and restore data, such as projects, settings, workflows, and issues, in your Jira site .")
+  * [File systems](../saas/fs_filesystems.html "RSC provides management and protection of file system data on supported Linux, Unix, and Windows hosts through filesets.")
+  * [Google Cloud Platform workloads](../gcp/gcp.html "RSC protects the following types of Google Cloud Platform workloads: Google Compute Engine instances and persistent disks.")
+  * [Hyper-V virtual machines](../saas/hyper_v/hyperv_virtual_machines.html "A Rubrik cluster provides data management and protection for virtual machines that are deployed in a Microsoft Hyper-V environment. The Rubrik cluster can manage and protect virtual machines in an environment with multiple Hyper-V servers and virtual machines.")
+  * [IBM Db2](../db2/ibm_db2.html "With IBM Db2 workloads, you can automate complex tasks such as database discovery and data protection for managing databases.")
+  * [Kubernetes protection](../kubernetes/k8s_workload_protection.html "You can use Kubernetes protection to protect your on-premise or cloud-native Kubernetes clusters using a protection set.")
+  * [Managed Volumes and SLA Managed Volumes](../managedvolumes/mv_managed_volumes_sla_managed_volumes.html "Managed Volumes in RSC protect and manage data while SLA Managed Volumes schedule and initiate backups using an SLA Domain.")
+  * [Microsoft Azure workloads](../saas/azr_workloads.html "RSC protects the data and resources of Azure virtual machines, Azure managed disks, Azure Blob Storage, and Azure SQL workloads in Azure subscriptions.")
+  * [Microsoft 365](../saas/m365.html "Using the data management and protection services offered by Rubrik Security Cloud, you can protect Microsoft 365 data operations.")
+  * [Microsoft 365 Backup Storage](../m365_backup_storage/m365_backup_storage.html "With the Microsoft 365 Backup Storage feature, you can back up Microsoft 365 applications such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes. You can also restore large volumes of data during ransomware attacks, accidental deletion, or malicious data deletion and overwrite events.")
+  * [Microsoft Dynamics 365](../microsoft_dynamics_365/microsoft_dynamics_365.html "RSC protects the tables and metadata in your Microsoft Dynamics 365 subscription.")
+  * [Microsoft Entra ID](../saas/ms_entra_id.html "RSC supports backup and recovery of Microsoft Entra ID.")
+  * [Microsoft Exchange Server](../saas/ms_exchange_server.html "Rubrik Security Cloud provides protection for Microsoft Exchange Servers.")
+  * [MongoDB workloads](../mongodb/mongodb_workloads.html "Rubrik Security Cloud protects your MongoDB sources, databases, and collections, ensuring optimal storage efficiency and smooth database operations with its advanced security features and strong data protection.")
+  * [MySQL](../mysql/mysql.html "RSC protects the MySQL databases from accidental deletions, ransomware attacks, and other potential threats.")
+  * [NAS CD data sets](../saas/ncd_data_sets.html "Rubrik NAS Cloud Direct offers secure data protection with high-performance, scalable enterprise backup, and archive services for unstructured file data.")
+  * [NAS systems](../nas/nas_systems.html "RSC manages and protects NFS and SMB shares on NAS systems for efficient data storage and retrieval.")
+  * [Okta IdP](../okta/okta_idp.html "Rubrik Security Cloud provides protection and recovery for Okta Identity Provider objects. By integrating your Okta tenant with Rubrik, you can leverage a comprehensive set of data protection features designed for security, simplicity, and reliability.")
+  * [Oracle databases](../oracle/oracle_databases_rsc.html "You can use RSC to back up, archive, replicate, and recover Oracle databases.")
+  * [OpenStack virtual machines](../openstack/openstack_virtual_machines.html "RSC provides data management, SLA Domain protection, and recovery for OpenStack virtual machines.")
+  * [PostgreSQL](../postgresql/postgresql.html "Rubrik Security Cloud protects your PostgreSQL cluster by simplifying complex backup and recovery processes, discovering the databases automatically, and protecting data using SLA Domains.")
+  * [Salesforce Data Protection](../salesforce/salesforce_management.html "Salesforce Data Protection is a Rubrik-hosted SaaS service that extends RSC by securely backing up your critical Salesforce data and metadata for standard and custom objects.")
+  * [SAP HANA databases](../saas/sap_hana_protection.html "RSC enables administrators to implement backup policies on SAP HANA databases running on public clouds and on-premises.")
+  * [SnapMirror Cloud](../saas/snapmirror_cloud.html "RSC protects user data replicated by the NetApp SnapMirror Cloud service.")
+  * [Microsoft SQL Server databases](../common/sql_server_databases.html "A Rubrik cluster provides data management and protection for Microsoft SQL Server databases.")
+  * [VMware Cloud](../vmware_cloud/vmware_cloud.html "A Rubrik Cloud Cluster effectively protects virtual machines deployed on VMware Cloud on AWS, Microsoft Azure VMware Solution, and Google Cloud VMware Engine.")
+  * [vSphere virtual machines](../saas/vs_virtual_machines.html "Rubrik Security Cloud provides data management and SLA Domain protection for vSphere virtual machines, including vSphere VM templates that are managed either through a VMware vSphere environment or a content library.")
+  * [VMware Cloud Director vApps](../vcd/vmware_cloud_director_vapps.html "The Rubrik cluster provides SLA Domain protection and data management for VMware Cloud Director vApps.")
+  * [Windows volume groups](../saas/windows_volume_groups.html "A volume group is a Rubrik workload comprised of at least one data storage volume on a Windows host.")
+

Rubrik_cluster_deployment_1.md

@@ -0,0 +1,37 @@
+# Rubrik cluster deployment
+
+Source: https://docs.rubrik.com/en-us/saas/install/rsc_cluster_deployment.html
+
+---
+
+# Rubrik cluster deployment
+
+Deploying a Rubrik cluster running on Rubrik appliance nodes involves installing the CDM software on the nodes and setting up that software for your environment.
+
+## Appliance nodes
+
+Getting your Rubrik cluster up and running on Rubrik appliance nodes involves the following tasks:
+
+  * Downloading and installing the Rubrik CDM software
+  * Setting up the Rubrik cluster
+  * Registering the Rubrik cluster
+
+Rubrik appliance nodes come with a recent version of the Rubrik CDM software already preloaded. Rubrik recommends that instead of running your Rubrik cluster with this factory loaded version, you consider downloading and installing the most recent GA version of the CDM software. By doing this you can avoid running multiple upgrades to get the cluster running the latest GA version. However, selecting a Rubrik CDM version that is not preloaded adds approximately 30 minutes to the setup process.
+
+Installing and configuring the Rubrik CDM software on a cluster usually involves running the configuration wizard from the UI provided by a node of the cluster. The wizard ensures that all nodes pass the pre-checks and meet the requirement of running the same version of Rubrik CDM before installing and configuring the software.
+
+When required, installing and configuring the software can also be done from the Rubrik CLI.
+
+After installing the software on all of your nodes, you perform the set up task. The set up task involves configuring each node to operate as part of a cluster. It also involves configuring the nodes with your network preferences.
+
+Your last step is registering the new Rubrik cluster. If your Rubrik cluster can connect to your Rubrik Security Cloud (RSC) domain, you can easily register your Rubrik cluster using a web browser. If your Rubrik cluster cannot connect to your RSC domain, you can use the offline method to register the cluster.
+
+## Other platforms
+
+Supported hardware other than the Rubrik appliance hardware is available from manufacturers such as Dell, Cisco, and Hewlett Packard Enterprise. Rubrik provides hardware-specific installation and configuration guides for each supported platform. These guides are available through the [Rubrik Support portal](https://support.rubrik.com/).
+
+The process of installing Rubrik CDM software on virtual instances such as Rubrik Edge, Rubrik Virtual Cluster, and Rubrik Cloud Cluster includes preparing the virtual hardware for those deployments. Rubrik provides documentation for each deployment type through the [Rubrik Support portal](https://support.rubrik.com/).
+
+## RSC association
+
+After the Rubrik cluster is successfully configured, you establish an association between the Rubrik cluster and Rubrik Security Cloud by registering the cluster using your RSC account.

Ruby_2.md

@@ -0,0 +1,31 @@
+# Ruby
+
+Source: https://docs.rubrik.com/en-us/saas/saas-ai/ruby_2.html
+
+---
+
+# Ruby
+
+Ruby is a generative AI assistant that extends Rubrik Security Cloud capabilities. You can interact with Ruby to use and manage RSC security features.
+
+Ruby is built on Microsoft Azure Open AI. This Rubrik partnership with Microsoft secures a private entry point into generative AI and ensures that your data remains private. Ruby uses Rubrik threat intelligence information based on machine learning to develop interactive workflows for data recovery during a security incident.
+
+Using RSC Data Threat Analytics, Data Security Posture, and Orchestrated Application Recovery, you can detect anomalies, uncover sensitive data, and identify and isolate threats in the environment. Ruby streamlines these multi-step workflows within RSC into a single process, allowing backup administrators to perform security-related tasks and collaborate with security teams.
+
+When Threat Monitoring detects an anomaly, you receive a security incident notification. Ruby is then available in the Notifications tab in the Inbox in RSC dashboards to guide you through an integrated and interactive message window. Ruby provides recommendations to remediate the security incident using Sensitive Data Monitoring, Threat Hunting, and Orchestrated Application Recovery.
+
+Ruby matches user intent to a defined workflow based on a pre-trained model. The Ruby workflow involves the following:
+
+  * Viewing the threat details, including the indicators of compromise (IOCs), snapshot location, and time of the snapshot
+  * Searching for additional IOCs by using threat hunting
+  * Discovering the location of the sensitive data, including violations and the policies and objects impacted. For Microsoft 365 objects, you can also use Ruby to take remedial actions to address the issues identified.
+  * Quarantining snapshots that contain potentially malicious files or objects
+  * Creating Recovery Plans for data recovery
+
+While the notifications in the Inbox on the RSC dashboard are available to all users, Ruby only performs tasks for user accounts with the owner and administrator roles. Ruby recommends actions based on the RBAC permissions of the user account. Actions that do not correlate to user account permissions are not available. Ruby asks for user confirmation before proceeding with any recovery or quarantine action. The audit logs also indicate the user account that confirmed the specific actions performed using Ruby.
+
+Ruby is available as part of the Rubrik Enterprise edition. Enabling Ruby requires that Rubrik clusters are running CDM version 9.0.1 or later. For the threat detection and remediation use case, enabling Threat Monitoring is required.
+
+Note:
+
+Ruby is an AI assistant. AI-generated content may contain errors or inaccuracies. Independent verification of such content is strongly recommended.

System_shutdown_1.md

@@ -0,0 +1,11 @@
+# System shutdown
+
+Source: https://docs.rubrik.com/en-us/saas/install/system_shutdown.html
+
+---
+
+# System shutdown
+
+A system shutdown can be done from the Rubrik CLI.
+
+Typical operation of a Rubrik cluster does not require a system shutdown, but is occasionally necessary for business purposes or at the request of Rubrik Support.

Threat_Monitoring_1.md

@@ -0,0 +1,34 @@
+# Threat Monitoring
+
+Source: https://docs.rubrik.com/en-us/saas/saas/threat_monitoring.html
+
+---
+
+# Threat Monitoring
+
+Threat Monitoring automatically and continuously scans snapshots for new and existing indicators of compromise, and provides visibility into potential threats.
+
+With an initial full scan at feature enablement, followed by incremental scans, Threat Monitoring scans snapshots for threats based on indicators of compromise (IOCs) from multiple threat intelligence sources. Threat Monitoring detects risk early by:
+
+  * Identifying threat indicators within backups.
+  * Accelerating threat investigation.
+  * Reducing the threat duration and risk of reinfection during recovery.
+
+IOCs provide forensic evidence of potential intrusions on a host system or network. When enabled, Threat Monitoring automatically pushes a threat feed of Yet Another Recursive Acronym (YARA) rules and file hashes every 24 hours to all applicable Rubrik deployments. RSC uses a hash database created during backup indexing to perform the file hash scanning. After the threat feed is downloaded to the Rubrik cluster, subsequent Threat Monitoring jobs start YARA rule analysis using the threat feed details. The threat feed updates periodically to import new intelligence, as available, to identify threats.
+
+Threat Monitoring scans executable files in snapshots that are smaller than 15 MB in size. Threat Monitoring scans Windows files that have the following extensions: .acm, .ax, .bat, .cmd, .com, .cpl, .dll, .drv, .efi, .exe, .js, .jse, .msi, .mui, .ocx, .ps1, .psc1, .scr, .sys, .tsp, .vbe, .vbs, .wsf, and .wsh. Threat Monitoring scans only Linux files that have the executable bit set.
+
+Threat Monitoring uses two key detection methods:
+
+  * YARA rule-based detection, which applies pattern-based analysis to identify potential threats, but does not rely on exact file-matching. As a result, YARA rules can sometimes generate false positives, detecting both malicious and benign files under the same logic. To maintain accuracy, RSC continuously monitors, reviews, and refines YARA rules, removing those that generate excessive false positives.
+  * Hash-based detection, which uses exact file-matching, ensuring high confidence in identifying known threats.
+
+Threat Monitoring uses only file hashes as IOCs to identify threats for Azure virtual machines and managed disks, Microsoft SharePoint and OneDrive objects, AWS EC2 instances and EBS volumes, and GCP GCE instances and persistent disks. For other workloads, Threat Monitoring supports monitoring with both YARA rules and file hashes as IOCs.
+
+For Rubrik clusters running CDM version 9.1.3-p2 and later, RSC offers the following capabilities:
+
+  * Scanning using a full set of YARA rules and file hashes.
+  * File hash scanning using a hash database created during backup indexing.
+  * Incremental and full scanning of existing data. Incremental scans handle new data, while RSC performs full scans of existing data when IOC updates occur. For example, when hash IOCs are processed against the hash database and new YARA rules are applied to the last completed backups.
+  * Retroactively processing IOC updates, as well as up to 100 custom IOCs.
+

Threat_hunts_1.md

@@ -0,0 +1,39 @@
+# Threat hunts
+
+Source: https://docs.rubrik.com/en-us/saas/saas/ri_threat_hunts.html
+
+---
+
+# Threat hunts  
+  
+On-demand threat hunts scan Rubrik backups for user-defined indicators of compromise and identify the systems potentially affected by an attack.
+
+When ransomware attacks happen, it is essential to respond quickly. Identifying which systems were compromised and when indicators of compromise (IOCs) were first present in those systems can be challenging. A threat hunt identifies files that might be at risk by scanning Rubrik backups to find when a compromise related to the attack occurred.
+
+Threat hunting is not a pattern-based anti-malware scanner, but an analysis tool for identifying specific IOCs. You can use threat hunt results to identify potentially malicious files and the snapshots in which they were present, avoiding malware reinfection during recovery.
+
+Threat hunting employs a full/incremental scanning method in which the initial scan is a full scan, but all subsequent scans are incremental. This reduces the number of files in subsequent scans and reduces the time to scan, optimizing the threat hunt.
+
+The presence of IOCs on a system indicates that malware might have compromised the system. You can configure threat hunts with the following key IOCs:
+
+  * Yet Another Recursive Acronym (YARA) rules, which use scripts that look for certain characteristics to identify malware. YARA rules are available only for advanced threat hunts.
+  * File hashes, which use specific file hash values to search for malware (MD5, SHA1, or SHA256).
+  * File patterns, which use specific file paths to search for malware. File patterns are available only for advanced threat hunts.
+
+RSC limits the number of threat hunts it supports. For each 30-day period, the product of the number of threat hunts and the number of snapshots per threat hunt should be fewer than 10,000.
+
+Threat hunting is supported for the following workloads:
+
+  * VMware, AHV, and Hyper-V virtual machines
+  * NAS filesets, excluding NAS Direct Archive filesets
+  * Microsoft Windows filesets
+  * Linux and Unix filesets
+  * Microsoft SharePoint and OneDrive
+  * Azure virtual machines, Blob storage, and managed disks
+  * AWS EC2 instances, S3 buckets, and EBS volumes
+
+Only turbo threat hunts are supported for Azure virtual machines, Blob storage, and managed disks, AWS EC2 instances, S3 buckets, and EBS volumes, Microsoft SharePoint, and OneDrive.
+
+  * GCP GCE Instances
+  * GCP Disks
+

Viewing_quarantined_files_or_objects_in_threat_hunts_1.md

@@ -0,0 +1,28 @@
+# Viewing quarantined files or objects in threat hunts
+
+Source: https://docs.rubrik.com/en-us/saas/saas/viewing_quarantined_files.html
+
+---
+
+# Viewing quarantined files or objects in threat hunts
+
+You can view threat hunts that have quarantined files or objects as well as the number of impacted snapshots.
+
+## Procedure
+
+  1. Log in to RSC.
+  2. Click  and select **Data Threat Analytics**.
+
+The Data Threat Analytics dashboard appears.
+
+  3. Click Hunts.
+
+The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact.
+
+  4. Select One or More in the Quarantined Matches filter.
+
+This allows you to view threat hunts that have multiple quarantined files or objects.
+
+## Results
+
+Threat hunts with quarantined matches, the number of quarantined files, and the number of impacted objects and snapshots appear.

adds_active_directory_domain_dc.md

@@ -0,0 +1,20 @@
+# Active Directory domains and domain controllers
+
+Source: https://docs.rubrik.com/en-us/saas/adds/active_directory_domain_dc.html
+
+---
+
+# Active Directory domains and domain controllers
+
+You can protect and recover Active Directory domains and domain controllers by using the protection services offered by Rubrik Security Cloud.
+
+Active Directory (AD) is a database that stores user credentials and information about computers and other resources on a network. Hence, AD services are used to authorize and authenticate users to access the resources within a network. By keeping access management within the network, AD provides an extra layer of security, which reduces the risk of unauthorized access.
+
+With Rubrik Security Cloud (RSC), you can protect your AD domains by recovering the domain controllers in the event of data threats. Additionally, RSC helps you to identify the changes made to AD objects.
+
+You can protect your AD domain controller by performing the following actions:
+
+  * Installing Rubrik Backup Service (RBS) on a domain controller that you want to protect
+  * Adding the domain controller to Rubrik cluster as a Windows host
+  * Assigning an SLA Domain
+

adds_active_directory_forest.md

@@ -0,0 +1,23 @@
+# Active Directory forest
+
+Source: https://docs.rubrik.com/en-us/saas/adds/active_directory_forest.html
+
+---
+
+# Active Directory forest  
+  
+Rubrik Security Cloud offers protection services for the Active Directory forest hierarchy. You can protect and recover the entire forest hierarchy in the event of a disaster or ransomware attack.
+
+Protecting and recovering the entire Active Directory (AD) forest requires purchasing Rubrik Identity Recovery License. RSC supports protection and recovery of an AD forest for Rubrik clusters running Rubrik CDM version 9.2.2 or later. The object and attribute comparison feature also requires the Rubrik Identity Recovery License.
+
+An AD forest is the topmost organizational boundary and logical container in an AD environment. It comprises one or more AD domains that share a common schema, configuration, and global catalog, enabling centralized management and coherent structure. Within an AD forest, domains can collaborate through trusted relationships, resource sharing, and unified security policies. This hierarchical framework facilitates the integration of diverse organizational units, users, computers, and policies, ensuring consistent access control and administration across large and complex enterprise networks.
+
+AD forest offers several key advantages for managing and organizing directory services in large, complex environments.
+
+RSC enables comprehensive recovery and protection of entire AD forest in the event of data threats. Key benefits include centralized domain management and discovery, SLA Domain assignment for protection, and automated recovery processes following best practices recommended by Microsoft. The solution minimizes downtime and mitigates the risk of malware reintroduction. It also enhances security, provides a detailed view of forest hierarchies, and supports various recovery use cases. Additional features include DNS recovery, advanced recovery settings, metadata erasure for unselected domain controllers, and recovery progress tracking.
+
+You can protect your AD forest by:
+
+  * Adding the domain controller to Rubrik cluster as a Windows host: This task ensures that the AD domain controller is part of the Rubrik backup environment.
+  * Assigning an SLA Domain at the forest level: This task ensures that all domains within the forest receive the same level of protection.
+

adds_active_directory_inventory_management.md

@@ -0,0 +1,20 @@
+# Active Directory inventory management
+
+Source: https://docs.rubrik.com/en-us/saas/adds/active_directory_inventory_management.html
+
+---
+
+# Active Directory inventory management  
+  
+The Active Directory inventory provides a summary of the actions involved in protecting the AD domain controllers in RSC. You can manage your domains and domain controllers using the information available in the AD inventory.
+
+With RSC, you can manage the domains and domain controllers in the AD inventory page by adding domain controllers to a Rubrik cluster. When you add a domain controller to a Rubrik cluster as a Windows host, RSC discovers the AD domain of the domain controller and the other domain controllers associated with that AD domain and displays them in the AD inventory page. You can start protecting a domain controller by assigning an SLA Domain.
+
+AD domains are logical entities that can be used to design a network hierarchy that meets your requirements. AD domain controllers, which are Windows servers running Active Directory, authenticate users and manage access to resources in an AD Domain.
+
+Information about all the discovered AD domains and associated domain controllers is displayed in the following tabs:
+
+  * Domains: This tab displays information about all the discovered AD domains.
+  * Domain Controllers: This tab displays information about all the discovered domain controllers.
+
+  *[ > ]: and then

adds_active_directory_snapshots.md

@@ -0,0 +1,27 @@
+# Active Directory snapshots
+
+Source: https://docs.rubrik.com/en-us/saas/adds/active_directory_snapshots.html
+
+---
+
+# Active Directory snapshots
+
+RSC protects and manages data by taking snapshots of the domain controller. You can take an on-demand snapshot, or you can configure an SLA Domain to take scheduled snapshots.
+
+RSC provides support for on-demand snapshots and scheduled snapshots. Scheduled snapshots are created based on the policies and rules of an assigned SLA Domain.
+
+The supported snapshot types are described as follows:
+
+  * On-demand: Snapshots of AD domain controller that you can take whenever required using the take on-demand snapshot option.
+  * Scheduled: Snapshots created on a schedule according to the frequency specified in the SLA Domain. RSC takes scheduled snapshots using the manual snapshot API technology.
+
+The SLA Domain feature provides a configurable set of policies that you can apply to domains or domain controllers to achieve specific data protection objectives. The SLA Domain directs when to schedule backups of domain controller data and how long to keep the data.
+
+With RSC, you can perform the following actions for snapshots:
+
+  * Take on-demand snapshots
+  * Change the retention policy for snapshots taken
+  * Delete the snapshots that have a Forever retention policy
+  * Recover the snapshots using the various recovery options RSC offers
+
+  *[ > ]: and then

adds_ad_dc_recovery_options.md

@@ -0,0 +1,23 @@
+# AD domain controller recovery options
+
+Source: https://docs.rubrik.com/en-us/saas/adds/ad_dc_recovery_options.html
+
+---
+
+# AD domain controller recovery options
+
+With RSC, you can recover Active Directory domain controller snapshots using either granular recovery or domain controller recovery options.
+
+You can take snapshots of the Active Directory (AD) domain controller using scheduled backups or take on-demand snapshots of the domain controller. RSC provides two options for recovering the snapshot information.
+
+The following table provides the AD domain controller recovery options. Recovery type | Description  
+---|---  
+Granular recovery | Recovers the selected objects in an AD. The protected objects include containers, organization units, users, groups, contacts, group policies, and computers.  
+Domain controller recovery | Recovers the domain from the selected domain controller and restores it to one of the following destinations:
+
+  * Restore to alternate host: Recovers the domain controller data to the alternative host that you selected.
+  * Restore to original domain controller: Recovers the domain controller data to the same domain controller by replacing the information with the selected snapshot information.
+  * Restore to new host or VM using bare-metal recovery: Recovers a failed server or domain controller to a separate host or a new virtual machine.
+
+Note: The AD domain controller recovery options restore additional roles, such as Active Directory Certificate Service (ADCS) and Network Policy and Access Services (NPAS), along with recovering data in an AD.
+  *[ > ]: and then

adds_ad_domain_controller_protection.md

@@ -0,0 +1,33 @@
+# Active Directory domain controller protection
+
+Source: https://docs.rubrik.com/en-us/saas/adds/ad_domain_controller_protection.html
+
+---
+
+# Active Directory domain controller protection
+
+To protect the information on your AD domain controllers by applying RSC data protection policies, you can assign SLA Domains to the domain controllers
+
+RSC uses SLA Domains to apply data protection policies to Active Directory (AD) objects. The AD objects are domains and domain controllers. If there is no SLA Domain assigned to a domain controller, the SLA Domain assigned to the parent AD domain is inherited by the domain controllers of that specific AD domain.
+
+The minimum SLA Domain frequency required for AD domain controllers is four hours. You cannot assign an SLA Domain with a frequency of less than four hours to AD domain controllers. When you try to assign an SLA Domain with a frequency of less than four hours, RSC displays an error message indicating the minimum requirement of SLA Domain frequency to protect domain controllers.
+
+Rubrik recommends installing the Rubrik Backup Service (RBS) software on your Windows host to start taking backups of the information that resides on your AD domain controllers.
+
+You can start protecting the information on your domain controllers by:
+
+  * Adding the DNS IP entries to a Rubrik cluster
+  * Assigning SLA Domains to domain controllers
+  * Configuring an SMB domain
+
+When RBS is running with an AD domain user account, the user account should be a member of backup operators and server operators AD groups for the AD backups to work as expected. However, to recover an entire AD or AD objects using Rubrik AD recovery, the service account must have Domain Admin privileges or LocalSystem account. To enhance security, you can initially add the user accounts to the backup operators and server operator AD groups. When a restore is needed, you can temporarily raise the user account privileges to Domain Admin or set it to LocalSystem.
+
+Rubrik requires you to restart the RBS services in the following scenarios for the changes to take effect:
+
+  * When you change the logon user privileges
+  * When you change the logon user
+
+The logon user account that RBS is running with requires Write permission to the C:\programdata\Rubrik directory of the host that RBS is installed on. You must assign the Write permission recursively to all the child directories of the C:\programdata\Rubrik directory. An administrator can assign the permission to the user account using the Advanced option in the Windows Security tab for the C:\programdata\Rubrik directory.
+
+Rubrik recommends that you use a Microsoft Group Managed Service Account for the RBS service account instead of a traditional AD service account. Microsoft documentation provides more information about Microsoft Group Managed Service Account.
+  *[ > ]: and then

adds_ad_domain_controllers_info.md

@@ -0,0 +1,25 @@
+# AD domain controllers information
+
+Source: https://docs.rubrik.com/en-us/saas/adds/ad_domain_controllers_info.html
+
+---
+
+# AD domain controllers information  
+  
+Information about the Active Directory domain controllers registered with Rubrik clusters. You can view information about domain controllers and start protecting a domain controller by assigning an SLA Domain.
+
+The Domain Controllers tab in the inventory page contains fields related to the Active Directory (AD) domain controllers registered with Rubrik clusters. You can also customize the view by adding, removing, pinning, and re-ordering the columns using the  icon.
+
+Field | Description  
+---|---  
+Domain Controller | The name associated with an AD domain controller.  
+FSMO Role | The FSMO roles assigned to the domain controller.  
+Server Role | The server roles assigned to the domain controller, for example, DNS and DHCP.  
+Domain | The domain name associated with the domain controller.  
+Rubrik Cluster | The Rubrik cluster associated with the domain controller.  
+SLA Domain | The SLA Domain assigned to the domain controller.If the domain controller does not have an SLA Domain assigned, it will inherit the SLA Domain of the parent AD domain.  
+RBS Status | The status of RBS. Only the domain controllers registered with a Rubrik cluster display the RBS status as Connected.  
+Snapshots | Number of snapshots available for the domain controller.  
+DC Location | Details about the location where the domain controller resides in your network.  
+Assignment | Type of assignment, indicating whether the SLA Domain assigned to the domain controller is direct or inherited from the AD domain.
+  *[ > ]: and then

adds_ad_forest_discovery.md

@@ -0,0 +1,34 @@
+# AD forest discovery
+
+Source: https://docs.rubrik.com/en-us/saas/adds/ad_forest_discovery.html
+
+---
+
+# AD forest discovery
+
+When you add an Active Directory domain controller to a Rubrik cluster as a Windows host, RSC discovers the Active Directory forest and all the domains in the forest hierarchy.
+
+RSC discovers the Active Directory (AD) domains in a forest after:
+
+  * You install Rubrik Backup Service (RBS) on a domain controller
+  * You add the domain controller to a Rubrik cluster as a Windows host
+
+RSC retrieves information about the applications running on the Windows host and identifies the Windows host as a domain controller.
+
+After you install RBS on a domain controller and add the domain controller to a Rubrik cluster as a Windows host, RSC performs the following actions as part of AD forest discovery:
+
+Discovery task | Description  
+---|---  
+Discovering all AD domains | Discovers all the AD domains in an AD forest.  
+Discovering domain controllers | Discovers the other domain controllers that exist in the same AD domain and displays the discovered domains and domain controllers in RSC.  
+Identifying FSMO roles | Identifies the FSMO roles assigned to each of the discovered domain controllers and displays them in RSC.  
+Identifying Windows services | Identifies other Windows services, such as DNS and DHCP, if any domain controller in the AD domain is hosting these services.  
+  
+For Windows installations, all non-administrator RBS accounts must have access to the Rubrik registry at Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Rubrik Inc.\Backup Service\ and must be part of the backup operators group. If you install RBS on a host running CDM versions 9.0.3-p12, 9.1.3-p4, 9.2.1-p1, 9.2.2, or 9.3.0 and then later perform a CDM upgrade, all Windows hosts that are running RBS with a non-administrator account will be disconnected.
+
+You can reactivate RBS in one of the following ways:
+
+  * By giving the user account or service account running RBS full access to the C:/Program Files/Rubrik directory. Restart RBS after adding the necessary permissions.
+  * By performing a clean reinstallation of RBS on the Windows host after upgrading CDM to versions 9.0.3-p12, 9.1.3-p4, 9.2.1-p1, 9.2.2, 9.3.0 or above.
+
+  *[ > ]: and then

adds_ad_forest_inventory_management.md

@@ -0,0 +1,25 @@
+# AD forest inventory management
+
+Source: https://docs.rubrik.com/en-us/saas/adds/ad_forest_inventory_management.html
+
+---
+
+# AD forest inventory management
+
+The Active Directory inventory provides a summary of the actions involved in protecting and recovering the Active Directory domains in forest hierarchy using RSC. You can manage the domain controllers in a forest using the information available in the Active Directory inventory.
+
+With RSC, you can manage the domains and domain controllers in the Active Directory (AD) inventory page by adding domain controllers to a Rubrik cluster. When you add a domain controller to a Rubrik cluster as a Windows host, RSC discovers the AD forest and all the domains in the forest and displays the discovered domains in the inventory page.
+
+Information about all the discovered forests and domains and associated domain controllers is displayed in the following tabs:
+
+  * Forests/Domains: This displays information about all the discovered AD forests and domains.
+  * Domain Controllers: This displays information about all the discovered domain controllers.
+
+As part of inventory management for domains in a forest, you can:
+
+  * Add your domain controllers to a Rubrik cluster as Windows hosts.
+  * Remove domain controllers from the Rubrik cluster if the AD domain data is corrupted or the Windows server fails.
+
+If all the domain controllers in a forest are deleted, the AD forest is automatically removed from RSC.
+
+  *[ > ]: and then