Industries/ Finance/ Secure cloud foundations
Cloud hosting that answers the security questionnaire before it arrives
We set up your cloud so customer and account data are separated, encrypted and reachable only by the roles that need them, with every access recorded where nobody can quietly edit it. When a bank partner, funder or enterprise client sends its due diligence questions, the evidence already exists.

- Used by
- Your technical lead, operations, compliance and auditors
- Takes the place of
- Shared admin logins, ad hoc servers and evidence gathered by hand
- Connects to
- Your identity provider, payment provider, apps and log storage
- Built with
- Our security & compliance service
Where it hurts today
A normal week, before it exists
Many financial firms' cloud setups grew around a product launch. The first developer created an account, gave themselves full rights, and later added a contractor, an integration and a reporting tool with the same rights, because narrowing them looked like an afternoon of work. Test copies of the customer database sit beside the live one. Nobody is careless, but nobody could say today exactly who can read the account data.
Then the questionnaire arrives. A bank partner, a funding line or an enterprise client wants long answers about encryption, access reviews, backups, logging and incident response before it will sign. A founder or operations lead spends weeks writing careful prose, some of it describing controls that are intended rather than in place, and the answers drift from one questionnaire to the next.
Card payments add their own weight. If card details pass through your servers on the way to the payment provider, much of your infrastructure is drawn into PCI DSS scope, and every annual assessment becomes a project. And when someone leaves, removing their access means remembering every system they touched, which is exactly the step that gets missed when the team is busy.
What it does
Secure cloud foundations, feature by feature
The controls financial firms are asked about most, set up as code so they stay in place after the first tidy-up.
- 01
Customer data separated from everything else
Live customer and account data sit in their own environment, apart from development and testing, which use synthetic or anonymised data. Each service reaches only the data it needs, so a problem in the marketing site or a reporting tool cannot reach the account records.
- 02
Access by role, granted for a time
Staff and suppliers sign in through your identity provider with multi-factor authentication. Day-to-day roles are narrow. Production access is requested for a reason, approved by a named person and expires on its own, and a documented emergency account covers the night something genuinely breaks.
- 03
Encryption and keys kept properly
Data is encrypted in storage and in transit, with keys held in a managed key service rather than configuration files. Passwords, API keys and tokens live in a vault with rotation and a record of who accessed them, and old repositories are scanned for keys that were never removed.
- 04
Logs nobody can quietly edit
Administrative actions, data access and changes to the setup are written to separate log storage that cannot be altered for a period you agree with your compliance lead. When someone asks who looked at an account record, the answer comes from the log.
- 05
Card data kept out of your systems
Card details travel from the customer's browser straight to your payment provider, and your systems keep only a token. What remains in PCI DSS scope is small, documented and separated, which makes the annual assessment a smaller piece of work for your team and your assessor.
- 06
Backups that survive an attack
Backups are held in a separate account with separate credentials, locked so they cannot be altered or deleted for a defined period, and restored on a schedule. Each restore test is recorded, so you can show a funder or an auditor that recovery has been tried, not just planned.
A day with it
How the day runs instead
A normal week for a growing fintech once the foundations are in place.
- Monday, 9amOperations lead
A new starter joins customer operations. Her work account is created in the identity provider, and the operations role gives her the case screens she needs and nothing else. She sets up multi-factor sign-in on her first morning.
- Tuesday, 2pmDeveloper
A developer needs to look at a production database to investigate a failed payment. He requests access with the ticket reference, the engineering lead approves it, and it expires at the end of the day. Every query he runs is logged.
- WednesdayEngineering lead
A change to the infrastructure would have made a storage bucket public. The automated policy check refuses it before it is applied, and the pipeline tells the developer which rule it broke and why.
- ThursdayChief operating officer
A prospective bank partner sends its due diligence questionnaire. The chief operating officer answers most of it from the evidence pack: access review records, encryption settings, the last restore test and the incident plan, each dated and current.
- Quarter endCompliance lead
The quarterly access review arrives as a list of every person and supplier with access, grouped by role. The compliance lead and team managers confirm or remove each one. A contractor who finished last month is removed, and the review is filed as evidence.
What it connects to
Works with what you already run
The foundations sit underneath your applications and connect to the services that hold identity, payments and logs.
Cloud provider
Accounts on a major cloud, for example AWS, Microsoft Azure or Google Cloud, set up in your firm's name, in the regions your obligations allow, with policies that stop resources being created anywhere else.
Identity provider
Staff and supplier sign-in runs through the provider your firm already uses, for example Microsoft Entra ID or Google Workspace, so joiners, movers and leavers are handled in one place.
Payment provider
Card capture uses your payment provider's hosted fields or checkout, for example Stripe or Adyen where they suit your products, so card numbers do not pass through your servers.
Your applications and log storage
Your portal, onboarding journey and internal tools run on the foundations, and their security events flow into the same protected log storage, so one search shows what happened across all of them.
The first version
Start small, then grow it
A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.
In the first version
- A read-only review of your current setup, with findings ranked by real risk
- Single sign-on and multi-factor authentication for every staff and supplier account
- Separate live and test environments, with synthetic or anonymised test data
- Secrets moved into a vault, and any exposed keys rotated
- Protected logs and backups in a separate account, with a first restore test
Once it is in use
- Time-limited production access with approval and automatic expiry
- Hardening written as code and checked automatically on every change
- Independent penetration testing at an agreed interval, with findings fixed and retested
- A maintained evidence pack for due diligence questionnaires and audits
Buyer's guide
Before you commission one
Four decisions worth making before you commission cloud foundations.
- 01
Managed platform, or your own cloud
Early on, a managed platform or a banking-as-a-service partner may carry much of the infrastructure and its evidence for you, and that can be the right call. Your own cloud accounts make sense once partners ask for controls you must show directly, or your data and residency needs outgrow the platform. Either way, the accounts should be in your firm's name.
- 02
What to gather first
The last security questionnaire a partner sent, any contract clauses on security and data location, a list of every system and supplier that touches customer data, and who has admin access to each today. Note which frameworks you are measured against: PCI DSS, SOC 2, ISO/IEC 27001 or a regulator's own rules.
- 03
Who should own it
A named senior person, often the chief operating officer or technical lead, owns security decisions and the risk register. Compliance owns the mapping to your obligations. Day-to-day operation can sit with us or with your own team, but accepting a risk is always the firm's decision, made by name and recorded.
- 04
How you will know it is working
Watch how quickly a due diligence questionnaire can be answered from current evidence, whether access reviews happen on time, how long a leaver keeps any access, how many changes the policy checks block and why, and whether the last restore test succeeded. Findings from independent tests should shrink between rounds.
Terms worth knowing
The words you will meet
- PCI DSS v4.0.1
- The card industry's security standard. Requirements that had been best practice became mandatory on 31 March 2025, including controls over the scripts running on payment pages. The simplest way to shrink what is assessed is to keep card numbers out of your systems entirely, using your payment provider's hosted fields so you store only tokens.
- SOC 2 Type II
- A report from an independent auditor on how a firm's controls operated over a period, built on the AICPA's Trust Services Criteria, with security always in scope. Bank partners and enterprise clients often ask for one. The audit covers your organisation, so we build the technical controls and the evidence it tests.
- DORA and operational resilience
- In the EU, the Digital Operational Resilience Act has applied to financial entities since 17 January 2025, including a register of ICT third-party providers. In the UK, the operational resilience rules for important business services ended their transition on 31 March 2025. In Australia, APRA's CPS 230 has applied since 1 July 2025.
Handled with care
The details that matter here
In financial services, security is judged by the evidence you can produce on the day someone asks. These are the details we handle with your team.
Compliance stays yours
PCI DSS, SOC 2, data protection law and your regulator's rules apply to your firm as a whole, including policies and people. We engineer the technical controls with your compliance lead, document each decision and produce the evidence. The assessment and the sign-off stay with your auditors and advisers.
Independent testing
We do not mark our own homework. We help you scope a penetration test with independent specialists, fix what they find in order of real risk, and arrange the retest, so the report your partners read comes from someone with no stake in the result.
Where data is held
Before anything is built we agree which regions customer data, backups and logs may sit in, and which suppliers process them. Rules differ by market: Saudi Arabia's Personal Data Protection Law sets conditions on transfers out of the Kingdom, and in the UAE the DIFC and ADGM free zones run their own data protection regimes.
Incidents rehearsed, not just written
We write an incident plan with your team that names who decides and who tells customers, regulators and partners. In the US, the amended Regulation S-P requires covered firms to run an incident response programme, and the FTC Safeguards Rule requires notice to the FTC within 30 days for breaches affecting 500 or more consumers. Then we rehearse it.
Questions
What buyers ask first
Can you get us through a SOC 2 or PCI DSS assessment?
No supplier can do that for you, and we would be wary of one who offered. Those assessments look at your whole firm, including policies and people as well as infrastructure. What we do is build and run the technical controls they test, keep the evidence current, and work alongside your compliance lead and assessor, so the audit becomes a matter of collecting what already exists rather than reconstructing it.
Do small financial firms need this level of cloud security?
The controls scale down well. A small advice firm and a growing lender face the same common risks: a leaked password, a leaver who keeps access, a backup nobody has tested. The first pass on identity, secrets and backups is modest work and deals with the problems that come up most often. Heavier controls can wait until a partner, a funder or your own growth asks for them.
Who holds the keys if we stop working with you?
You do. The cloud accounts, the identity provider and the vault are in your firm's name from the first day, and our access runs through the same time-limited, logged roles as everyone else's. If we stop working together, removing us is one step in your identity provider, and the documentation tells your next team how everything is set up.
What happens if we are breached anyway?
It remains possible, and nobody honest will tell you otherwise. What preparation changes is how it unfolds: alerts reach a named person, the protected logs show what was reached, narrow access limits how far it spread, and locked backups make recovery a procedure. The incident plan sets out who decides and who tells customers, partners and, where required, your regulator.
Do we need ISO 27001 as well as SOC 2?
It depends who is asking. SOC 2 is an American attestation report, while ISO/IEC 27001 is an international certification standard, and partners in different markets ask for different ones. They test overlapping controls, so one set of engineering can produce evidence for either. If you hold an older certificate, note that the transition from the 2013 version ended on 31 October 2025.
Send us the questionnaire you dread answering
Share the last due diligence questionnaire a partner sent you. We reply within 48 hours and will show you which answers your current setup can evidence today and which it cannot.
More for finance
What else we build for finance and banking
Client portals
A secure login where clients see valuations, statements, documents and application status, upload what you have asked for, and sign or approve without a printer. Permissions are checked on the server for every request, and every view is logged.
Guided onboarding journeys
Application and onboarding flows designed around how customers think: one question at a time, errors explained where they happen, progress saved between visits, and identity and suitability checks handed to your chosen providers at the right step.
Automated management reporting
Ledger, CRM and operational data joined on agreed definitions, so the board pack and investor updates build themselves from the same numbers every month, with unusual movements flagged for a person to explain before anything is sent.
Policy and procedure search
An assistant that answers questions from your own policies, procedures, product terms and committee minutes, citing the document and the version it relied on, so staff stop guessing and reviewers can check the source for themselves.
Document reading and triage
Bank statements, payslips, claim forms, valuations and signed agreements read on arrival, key details extracted and checked against the client record, and anything ambiguous or above a set threshold routed to a person rather than processed automatically.