01
Agree ownership in writing
Your project agreement should identify ownership of content, data, custom work, accounts and third-party licences. Ask how information can be exported and who can authorise access.
Loading content…
Security and data ownership
Your project agreement should identify ownership of content, data, custom work, accounts and third-party licences. Ask how information can be exported and who can authorise access.
01
Your project agreement should identify ownership of content, data, custom work, accounts and third-party licences. Ask how information can be exported and who can authorise access.
02
The local Business Core foundations use scoped permissions and non-production validation. This is engineering evidence, not a certification or proof that a client's production environment is secured.
03
Hosting, backup frequency, restore testing, incident contacts and maintenance coverage must be selected and documented for each implementation. No universal recovery-time guarantee is published.
04
Define account transfers, export formats, documentation and licence dependencies before work starts. Agree the assistance and costs associated with a later provider change.
Continue exploring
Continue with the related decision, evidence or assessment.
Continue with the related decision, evidence or assessment.
Recommended next step · awareness
Use the Digital Systems Score to identify the weakest handoff, or discuss the current workflow directly with Zoihost.