Scope the cloud estate by tenant and workflow
Fortra Cloud Data Protection is a portfolio-level enquiry covering cloud data and access controls. Selection should begin with the applications, tenants, users and data flows that require protection. A list of cloud brands does not establish that every edition, access method or action is supported by the proposed components.
Record who owns each tenant and whether the business uses approved services, personal accounts or third-party integrations. Separate stored-data exposure from information in transit and from private-application access. These are connected requirements, but the technical control points and customer permissions can differ. The proposal should show the role of each selected component rather than presenting cloud protection as one unexplained switch.
Prove policy at the relevant integration points
Confirm the current licence composition, supported connectors and deployment architecture with Fortra. Identify required administrative access before onboarding a tenant, and approve where telemetry or inspected content will be processed. UAE entities should determine their applicable handling requirements with authorised privacy and sector advisers.
Use a bounded pilot with representative users and synthetic information. Validate approved sharing, a prohibited data action and the exception process. Include integration failure and removal of the connection in the test plan. Handover should describe tenant permissions, policy ownership and coverage limits, including paths that bypass the selected controls. Implementation, subscription renewal and ongoing policy review should appear as separate responsibilities in the quotation.
Evidence to request for this scope
- List tenants, cloud applications and precise actions included in the initial phase.
- Obtain a current component and connector schedule with required permissions.
- Test policy effect and investigation context for an authorised sample cloud workflow.