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.
Where your data lives is a decision, not an accident.
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.
Who is responsible for which control, written down.
Who can reach what, and for how long.
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.
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.
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.
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.
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.
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.