Technical and Organisational Measures

How TechProvidence protects client information and manages access while delivering remote infrastructure engineering and operations services. These measures support the security obligations in our engagement agreements and GDPR Article 32.

What these measures cover and where they apply.

Employees only, under confidentiality commitments.

Least privilege, MFA and complete access removal.

Terminal server, VPN and managed, patched computers.

Two-year connection logs and a clear escalation path.

Daily encrypted backups on separate storage.

Client data stays in client systems; a clean exit.

Measures reviewed as threats evolve.

How this page relates to your contract.

Where each Article 32 area is covered.

01

Purpose and scope

These Technical and Organisational Measures (TOMs, also written technical and organizational measures) describe how TechProvidence protects client information and manages access while delivering remote infrastructure engineering and operations services.

They cover employees, company-managed computers, remote-access systems, credential management, logging, security maintenance, backup and recovery, and incident handling. Measures covering TechProvidence’s internal systems support secure service delivery.

Security, backup and recovery responsibilities within client environments, and the service scope for each client, are defined in the applicable engagement agreement. For hosting-side controls, see our GDPR server hosting checklist.

02

Personnel and confidentiality

Client work is carried out by TechProvidence employees. TechProvidence does not engage freelancers, contractors or external delivery providers to perform this work or access client systems.

Confidentiality commitments form part of employment arrangements. Employees receive security and client data handling guidance during onboarding.

Each team leader is responsible for ensuring their team follows the applicable security measures and for approving changes to those measures.

03

Access and credential management

Employee access permissions are limited to those required for their assigned work.

Individual user accounts are used where permitted by the client. Multi-factor authentication is used wherever the client’s systems support and permit it.

Credentials are managed through the client’s password manager where provided, or through TechProvidence’s internally hosted password manager. Access to client credentials is restricted to employees assigned to that client.

When an employee leaves or their assignment ends:

04

Secure remote access and system protection

Employees access client environments through a terminal server using company-managed computers, from office or remote locations. VPN access is the preferred connection method for client systems.

Company-managed access computers have antivirus protection, receive security updates, and automatically lock after inactivity, requiring authentication to unlock.

Security patching for the VPN and terminal server follows a monthly schedule. When a critical vulnerability affecting these systems is identified, patching is prioritised and scheduled outside the monthly cycle.

Routine maintenance is performed within the agreed scope and schedule. Major or disruptive changes require client approval. Emergency actions follow the authority agreed for the engagement, with prompt notification and documentation.

05

Logging and incident handling

VPN and terminal-server connection logs identify who connected and when. These logs are retained for at least two years, with viewing and deletion restricted to designated administrators. Read more about audit logging for compliance.

Logs are reviewed when an alert or incident occurs to identify connections present at the relevant time.

Employees report suspected incidents to their team leader, who investigates and informs management and the affected client on confirmation. For potentially serious cases, the team leader may escalate internally and notify the client when credible evidence suggests their systems or data may be affected, clearly stating that the investigation is ongoing.

06

Backup and recovery

Internal systems supporting client access and credential management are backed up daily. Backups are encrypted and stored on a separate server or storage system from the systems they protect.

Restores are tested as part of major infrastructure changes, such as machine replacement.

Backup and recovery responsibilities for client infrastructure, including covered systems, backup frequency, retention, storage and recovery targets, are defined in the applicable engagement agreement.

07

Data handling and engagement exit

TechProvidence’s working practice is to keep client data within the client’s systems and avoid downloading it to TechProvidence systems. Issue work and ticket replies are handled within the client’s ticketing system.

Handover scope, timing, and any applicable retention or deletion arrangements are agreed for each engagement. At engagement end:

Clients are encouraged to rotate credentials to invalidate previously used credentials and to independently confirm access closure.

08

Review and assurance

Security practices are reviewed when publicly reported threats, vulnerabilities or other security developments indicate that changes may be needed.

Changes affecting client environments remain subject to the approval requirements and responsibilities agreed for the engagement. For how we approach controls more broadly, see SOC 2 technical controls and our cybersecurity risk management service.

09

Relationship to agreements

This document supports the security obligations in the engagement agreement and any data processing agreement (GDPR Article 28(3)(c) and Article 32). Where they differ, the signed agreement prevails.

Need Our Security Answers for Your Vendor Review?

Talk to us about the security requirements for your engagement.