Identify what is being outsourced
For a French business, an IT support handover might include Linux servers, a cloud account and a deployment pipeline while leaving employee devices or application code with another team. Make that split explicit. Inventory production and non-production environments, technical owners, critical dependencies and the customer contact who can approve a change.
The French ANSSI outsourcing security guide discusses risks around loss of control, remote intervention and shared hosting. Use it as a starting point for the questions in the agreement, checking current rules and advice for your sector separately.
Prepare controlled remote access
Create named accounts where the platform supports them, assign the minimum permissions required, and define how emergency access is granted and removed. Identify the customer's account owner and keep an independent recovery path. Record where access events and support tickets are stored and how sensitive logs are handled. Never send administrator passwords in an ordinary project document.
Walk through a real operating scenario
Choose a representative deployment or server alert. Have the incoming operator show where the runbook, logs, ownership list and escalation contacts are kept. Agree a test change, its approval, the health check and the rollback decision. A successful SSH login is only an access check; it does not demonstrate that the application can be recovered.
Define the end of the engagement
Document how configuration, runbooks and data are returned, which accounts are revoked and who verifies the handover. Record open issues and third-party dependencies. Agree support hours, languages and response expectations for the actual contract. Clouvenix can scope managed infrastructure support around those responsibilities.