Security and operations

Requirements agreed at the start and built into delivery.

Security and operational requirements form part of every engagement. This page describes our standing practices; the specific controls for your solution are agreed with you and documented for your governance teams.

Hosting and data residency

Where your data lives is a decision, not an accident.

EU cloud regions we deploy toA dot-matrix map of Europe. Nottingham, our base, is connected to three EU cloud regions: Dublin (AWS, Microsoft Azure), Frankfurt (AWS, Microsoft Azure, Google Cloud) and Paris (AWS, Microsoft Azure, Google Cloud). Data residency is documented per service.Nottingham · our baseEU regions we deploy toDublinAWS · AzureFrankfurtAWS · Azure · Google CloudParisAWS · Azure · Google CloudData at rest and in processing staysin the regions you specify. Residencyis documented per service.On requestAmsterdam · Stockholm · Milan
Deployments in the EU regions of AWS, Microsoft Azure and Google Cloud, with residency documented per service.
  • EU and UK regions

    Client solutions are deployed in the regions you specify on AWS, Microsoft Azure or Google Cloud, including EU regions. Data residency is documented per service, with exceptions listed.

  • Your tenant, your accounts

    Wherever possible we build inside your own cloud accounts and identity tenant, so ownership, billing and audit trails remain with your organisation.

  • Encryption by default

    Data is encrypted in transit and at rest using the platform's managed services. Keys are held in your key-management service where the platform supports it.

  • Backups and recovery

    Backup schedules, retention and recovery objectives are agreed per system and tested, not assumed.

Shared responsibility

Who is responsible for which control, written down.

Shared responsibility: your organisation, ItSolver and the cloud providerThree columns list controls. Your organisation: policies and approvals, identity provider, data classification, business continuity. ItSolver: architecture and infrastructure as code, access reviews and single sign-on, security testing, runbooks and incidents, monthly reporting. Cloud provider: physical security, hypervisor and network, regional resilience, compliance attestations. Lines between the columns show where responsibilities hand over.Your organisationPolicies and approvalsIdentity providerData classificationBusiness continuityItSolverArchitecture and IaCAccess reviews · SSOSecurity testingRunbooks · incidentsMonthly reportingCloud providerPhysical securityHypervisor · networkRegional resilienceCompliance attestationsWritten down per engagement, including where a control sits with another supplier
Controls are split between your organisation, ItSolver and the cloud provider. Each engagement records who owns which control, including where responsibility sits with another supplier.
Access control and identity

Who can reach what, and for how long.

Access control: identity provider, multi-factor authentication, role, environmentAn engineer's access passes through your identity provider with single sign-on, an enforced multi-factor gate and a least-privilege role before reaching the environment in your tenant. Beneath it, a session bar shows access granted for the task and removed when the work ends.Identity providerYour SSOMulti-factorEnforcedRoleLeast privilegeEnvironmentYour tenantGranted for the taskRemoved when the work ends
An engineer's access passes your identity provider, the multi-factor gate and a least-privilege role before it reaches the environment, and is removed when the work ends.
  • Least privilege

    Engineers receive the minimum access needed for the task, granted through roles rather than shared credentials, and removed when the work ends.

  • Single sign-on and multi-factor authentication

    Access to client environments and to our own systems uses SSO with enforced multi-factor authentication.

  • Access reviews

    Who can reach which environment is reviewed at agreed intervals and on every change of team composition.

  • Secrets management

    Credentials live in the platform's secret manager, never in source code, tickets or chat. Rotation is part of the runbook.

Testing, procedures and incidents

Assurance you can inspect.

  • Security testing in delivery

    Dependency and static analysis run in the pipeline; infrastructure changes are reviewed before deployment. Independent penetration testing is arranged before go-live where your policy requires it.

  • Documented procedures

    Runbooks, change management, incident classification and escalation paths are written down, versioned and reviewed with you.

  • Incident handling

    Incidents are classified by priority with agreed response targets. You are informed of security incidents affecting your data without undue delay, with a written report after resolution.

  • Business continuity

    Named backups for every role on an engagement, documentation that does not depend on individuals, and clear exit terms so knowledge stays with you.

When something goes wrong

A written procedure, followed every time.

Incidents are handled to a procedure agreed with you at the start of the engagement, from the first alert to the written report, so nothing depends on who happens to be on call.

Incident handling: detect, classify, respond, inform, resolve, report, improveAn incident is detected by monitoring or reported by you, classified by priority against agreed response targets, worked on by an engineer, communicated without undue delay, resolved and verified, and closed with a written report. Lessons feed back into the improvement backlog and into monitoring.Lessons into the backlog and the monitoringDetectAlert or callClassifyP1 to P4RespondEngineer on itInformWithout delayResolveFix and verifyReportIn writing
An incident, from detection to the written report, with the lesson carried back into the backlog and the monitoring.
Incident handling: detect, classify, respond, inform, resolve, report, improveAn incident is detected by monitoring or reported by you, classified by priority against agreed response targets, worked on by an engineer, communicated without undue delay, resolved and verified, and closed with a written report. Lessons feed back into the improvement backlog and into monitoring.DetectAlert or callClassifyP1 to P4RespondEngineer on itInformWithout delayResolveFix and verifyReportIn writingLessons back into the backlog
An incident, from detection to the written report, with the lesson carried back into the backlog and the monitoring.
  • Priorities agreed before the first incident

    Each engagement defines what a P1 to P4 incident is for your organisation, the response target for each and who is called. Nothing is decided in the moment.

  • You are informed, not left waiting

    Security incidents affecting your data are reported to you without undue delay, with updates at agreed intervals until the incident is closed.

  • Every incident ends in writing

    A written report records the cause, the fix and what changes. Lessons go into the improvement backlog and, where useful, into monitoring.

Documentation on request

What we can provide during procurement.

Non-disclosure agreement

We sign mutual NDAs before receiving system documentation, data samples or architecture material.

Data processing agreement

A DPA covering UK GDPR and EU GDPR obligations for any engagement in which we process personal data on your behalf.

Security questionnaire responses

Written answers to your supplier assessment, with the evidence available for each control.

Certifications

We do not currently hold formal security certifications. We align our practices with recognised frameworks and provide evidence for specific controls on request.

Contact support@itsolver.co.uk or call +44 115 678 5537 to request any of the above.

Start a conversation

Discuss your security requirements with an engineer.

Describe your environment and the outcome you need. An engineer, not a sales team, reads every request and replies within one business day.

+44 115 678 5537support@itsolver.co.ukMonday to Friday, 09:00 to 17:30 UK time (10:00 to 18:30 CET)
Four disciplines, one accountable teamFour lines labelled consulting and architecture, engineering, cloud and operations, and service delivery converge into a single line labelled one accountable team.One accountable teamStrategy → delivery → operations
Contact

Start a conversation

Tell us about your environment and what you want to change. An engineer replies within one business day.