Designed inSecurity is settled before any code is written.
The architecture decides where data is stored, who can reach it and how it leaves the system. We settle those first, and agree the security requirements with you.
Development follows recognised secure-coding practice, including the guidance published by OWASP, the open project that sets out the common weaknesses in web software and how to avoid them.
Where a system holds sensitive or regulated data, independent penetration testing, an outside specialist trying to break in, is scoped into the proposal before go-live. You receive the test report.
Where data is kept
- Hosted in the EUClient data is hosted in the EU by default.
- Credentials in a secure storePasswords and keys are held in a secure store, never in the code.
- Handled on agreed termsConfidential material is shared only once terms are agreed, and data handling follows those terms.
Who can reach it
- Access follows the roleEach person sees only what their role requires, and nothing more.
- Admin tools kept apartAdministrative tools sit behind a separate sign-in that the public internet cannot reach.
- A written record of who can do whatYou receive the role and permission record.
Changes and approvalsNo change reaches the business unreviewed, and nothing that commits it happens without a person.
- Every change is reviewedSeparately from whoever wrote it, by automated checks and a senior reviewer, and it passes automated tests before release. Once it ships, it is confirmed on the live system rather than assumed from a successful build.
- Software stays supportedSystems are kept on supported versions, with no known critical vulnerability left open.
- A named person approves what mattersAnything that moves money, contacts a client or changes an important record is held until a named person approves it. The system proposes; a person decides.
- Every action is recordedWho acted, when, on what information, who approved it and any edits they made.
Backups and rollbackEvery release has a tested way back.
A kill switch
Each system has a switch that stops it at once.
A rehearsed reversal
The way back has been practised, not just written down. You receive the rollback procedure.
Backups restored in testing
Backups are taken automatically and restored in testing, so recovery is proven before it is ever needed. You receive the restore test record.
Moving your dataEvery migration is assisted, from the first record to the last.
- MappedWe plan the move and map each record from the old system to the new one.
- CheckedRecords are checked before they move.
- Moved in rehearsed stagesEach stage is practised before it is done for real.
- Run side by sideBoth systems run in parallel on real data until the results agree.
- Old system switched offOnly once the business runs on the new one unaided. We stay through the cutover.
At handover you receive the runbook (the instructions for running the system), a one-page record of every workflow and the rollback procedure.
At the end of a contractHow you leave is agreed in writing before you start.
Every commission is set out in a written proposal. Among other things it covers confidentiality and data handling, ownership and licensing, and handover and exit.
- Notice and help to moveThe agreement sets the notice period, the help we give with the transfer and who is responsible for completing it.
- What is handed overThe handover identifies the documentation, the data exports you are entitled to, account access, licensing terms and any outstanding actions.
- Another operator can take overIf you move the system to someone else, they take responsibility through an agreed transfer of the runbook, access and service ownership.
What you receiveEach standard comes with a record you keep.
- Security designed inThe agreed security requirements and, where scoped, the independent test report.
- Access by roleThe role and permission record.
- Reviewed changeThe review and test record, and the check made after each release.
- Named approvalThe action record.
- A tested way backThe rollback procedure and the restore test record.
- Assisted migrationThe runbook, the one-page workflow record and the rollback procedure.
How we handle data from this website is set out in the privacy notice.
