▣
Workspace isolation
Each organisation has an isolated workspace inside the multi-tenant cloud system.
Data protection and trust
Clear privileges.
And questions without ambiguity.
Data protection starts with who can access data and what they can do. This is a look at the controls available in TenXshift, and what should be fixed in writing before contracting.
⌘
Role-based privileges
Define roles and policies using RBAC, with segregation of duties per organisation settings.
◎
Identity verification
Multi-factor authentication (MFA) and step-up verification when additional checks are needed.
↔
Session and IP management
Controls for sessions and IP addresses within the available security settings.
✓
Configurable approvals
Define the review and approval path to fit internal procedures.
↗
Export audit
Audit of export operations to support review of how data is handled.
Before signing the agreement
Details worth settling
A written answer.
Technical controls alone do not answer every question. Ask the TenXshift team to document the following points in the proposal and agreement.
Hosting and backup
Data storage location, hosting provider, encryption, backup frequency, and restore-test mechanism.
Data ownership and exit
Organisation data ownership, export formats and scope, retrieval window, and deletion on service termination.
Support and response
Support channels, coverage hours, incident classification, and agreed response and recovery times.
No uptime promises, compliance certificates, or unconfirmed hosting locations are published here. This page describes controls; it is not a data processing agreement or contractual policy.
Test your grant. Then choose your scope.
Self-explore, then a 20-minute demo, then a subscription by modules and users.