Operational workflow — altasaasprotection 3.13.1 | Cohesity Documentation

Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist

Operational workflow — altasaasprotection 3.13.1 | Cohesity Documentation

Cohesity Alta SaaS Protection Administrator's Guide

Operational workflow

These are the typical tasks and activities you will perform as part of Cohesity Alta SaaS Protection operations, which can be communicated during the on-boarding process:

Table:

Tasks	Reference links:
1:: Tenant deployment Cohesity will set up your tenant and environment within Cohesity Alta SaaS Protection to get you started.
2:: Pre-requisite Perform the pre-requisite activities depending on the workload you have subscribed to protect.	See Pre-requisites to setup protection for M365. See Prerequisites to setup Google Drive protection with Cohesity Alta SaaS Protection. See Prerequisites to setup Gmail protection with Cohesity Alta SaaS Protection. See Key considerations and prerequisites for adding Salesforce connectors. See Prerequisites for Box connectors configuration. See Prerequisite for Email/message connector.
3:: User role assignment Default role assignment: (Applicable for Microsoft 365 workload backups) After Azure Active Directory (AD) synchronization, users are initially assigned the Default system role. This grants them access to the End-User portal, where they can search, share, and perform self-restores for their accessible content. Administrative role assignment: Assign appropriate administrative roles to users responsible for managing Cohesity Alta SaaS Protection. These roles ensure that users have the required permissions aligned with their business responsibilities.	See Role-based access control.
4:: Policy creation You are responsible for creating policies that define how data will be managed within Cohesity Alta SaaS Protection. These policies cover backup schedules, retention periods, and more, ensuring that the system aligns with your business and compliance requirements.	See About WORM policies .
5:: Connector creation You will need to create connectors to integrate Cohesity Alta SaaS Protection with your data sources, such as Microsoft 365, Google Drive, and other supported platforms. These connectors facilitate the secure backup of data from these sources into the Cohesity Alta SaaS Protection environment.	See Add Audit log connectors . See Add Salesforce connectors. See Add Slack connectors. See Add Email/Messages file.
6:: Data backup Once your connectors and policies are configured: Perform secure data backups from connected sources. Cohesity Alta SaaS Protection ensures that critical data is backed up according to your defined policies, preserving it for future restoration need.	See Perform on-demand/ad-hoc backup.
7:: Data restore In the event of data loss, initiate the restore process through the following options: Administrator restores: Restore backed-up data to its original or an alternate location, ensuring business continuity. End-User Self-Service restores: End users can restore their own data and share it with others through the End-User portal.	See Restore Exchange Online mailboxes. See Restore SharePoint/OneDrive/Teams Sites and data. See Restore Teams chat messages and Teams channel conversations. See Restore Box data. See Restore Google Drive data. See Restore Gmail data. See About Entra ID (Azure AD) objects and records restore . See About Salesforce Data, Metadata, and CRM Content restore and Sandbox seeding.

Feedback

Was this page helpful?

Feedback

Was this page helpful?