IT Services and System Security Responsibility Procedure
This procedure explains how 2cloud4u and the Client cooperate to maintain and protect IT systems. The scope of services and the Parties’ obligations are defined in their agreement. Publishing this procedure does not amend existing agreements or create a service agreement with a website visitor.
1. General provisions and allocation of responsibilities
The Contractor exercises due diligence within the agreed scope to maintain the functionality and security of the Client’s IT systems. Cybersecurity is an ongoing process requiring cooperation by both Parties. The Contractor provides the tools, recommendations and configuration covered by the agreement; the Client and its employees comply with security instructions and basic cybersecurity hygiene.
The agreement identifies covered systems, service hours, contacts, response arrangements and exclusions. This procedure does not independently promise 24-hour monitoring, a specific response time or services outside the agreement.
2. Obligations of the Client and its employees
- Fully restart computers at least weekly; Friday after work is the routine recommendation. Urgent instructions may require an earlier restart.
- Restart browsers at least every three days and follow urgent update instructions without waiting for that interval.
- Do not independently disable antivirus protection, including Microsoft Defender where used, firewalls or automatic updates.
- Do not use local administrator rights to install software not authorised by the Contractor.
- Promptly report unusual behaviour, suspicious messages, unexpected slowdowns or loss of file access.
- Use named accounts, protect credentials and follow agreed access and multifactor-authentication requirements.
3. Liability and contractual terms
The agreement defines the Parties’ liability. When agreeing its terms, the Parties may consider exclusions concerning damage, data loss, downtime, reputational or financial losses where an infection or breach results from ignoring explicit security, update or restart instructions, intentional acts by a Client employee, or use of local administrator rights to install unauthorised software. Opening a malicious attachment or entering credentials on a fraudulent website does not, by itself, establish intent or determine liability in an individual case.
No 100% protection against attacks is promised, including attacks exploiting previously unknown vulnerabilities. The proposed total liability cap remains one monthly subscription fee or the amount of the most recent invoice paid by the Client. It requires agreement in the relevant contract and does not take effect merely because it appears on this page.
Any exclusions and cap require assessment of causation, applicable exceptions and compatibility with mandatory law. This procedure does not introduce them into an existing agreement, exclude liability that cannot lawfully be excluded or determine a dispute in advance.
4. Procedure when a vulnerability is detected
Within the agreed service scope, the Contractor uses available tools to assess security. When Microsoft Defender or another agreed tool identifies a vulnerability, the Contractor assesses it and attempts remediation, including remote deployment of an appropriate update where authorised and technically possible.
If user action is required, the Contractor notifies the Client through the agreed channel of the affected system, action, risk and recommended deadline. The Client carries out actions within its control. Notification does not automatically transfer every contractual responsibility to the Client. Completion and unresolved exceptions should be recorded.
5. Access and authorisation of changes
Identify authorised contacts and systems before work starts. Use named accounts and the minimum access required, and agree an emergency access route. Send passwords and keys only through the agreed protected method, not public forms or ordinary notifications.
Changes require an agreed scope, risk assessment and approval proportionate to impact. Emergency work follows the agreed procedure and is documented afterwards. Revoke unnecessary access when work or employment ends.
6. Backups and recovery
The agreement specifies who performs backups, their scope, frequency, retention and recovery objectives. Before a material change, verify a usable backup or another proportionate recovery method and document rollback. Test restoration at agreed intervals.
A website enquiry confirmation is not a backup of a customer environment. Website enquiry retention does not determine backup periods or recovery guarantees for the Client’s systems.
7. Communication and incidents
Use the contacts and escalation channels in the agreement. Report incidents promptly with the time, affected service and symptoms, without unnecessarily distributing personal data or secrets. Follow containment instructions, preserve necessary evidence and avoid uncoordinated recovery changes or erasing evidence.
The Parties assess impact and communications within their roles. Statutory notification duties are assessed separately and are not replaced by an ordinary support message.
8. Personal data and records
Limit access to authorised persons and necessary data. When the Contractor processes personal data on the Client’s behalf, the relevant processing agreement governs instructions, safeguards and permitted subprocessors.
Website enquiries and measurement are covered by the separate privacy policy. Customer operational records, contractual evidence and incident records follow the applicable agreement, retention schedule and legal duties.
9. Application of the procedure
Before applying this procedure to a service agreement, the Parties agree the scope, liability terms, contacts and effective date. Existing agreements remain unchanged unless the Parties amend them through the agreed process.
Version 1.1 — editorial update: 17 October 2026.