What we solve

Start from the sentence you heard this week.

It comes from your customers

“A bank sent us two hundred security questions.”

The questionnaire is your customer’s due diligence on you, and their regulator expects them to do it. Each answer is scored, and the good ones have evidence behind them.

We answer it with you, line by line, and say plainly where the honest answer is not yet, with a date behind it. Then we build what the gaps need, so the next questionnaire is an export rather than a week of work. The date is agreed in the first call.

How quickly is a leaver’s access removed?

The answer that scores lowAccess is removed promptly, in line with our offboarding policy.
The answer with evidenceAccounts are removed from every connected app within minutes of HR setting the leave date. The removal log for the last quarter is attached.Source: HR system · exported removal log
One question, two answersIllustrative

What you have at the end: Answers your sales team can send, the evidence behind them, and a dated plan for the gaps.

“Our biggest prospect wants SOC 2 or ISO 27001 before they sign.”

The customer wants proof that security is taken seriously. The certificate takes months. The proof can start much earlier, with a dated route the customer can follow.

We plan the route to ISO 27001 or a SOC 2 report from what you actually run, build the controls into daily operation, including the engineering ones an auditor checks (branch protection, change management, production access, secrets), and keep your customer informed along the way. The evidence comes from the running system, not from a binder.

What you have at the end: A route with dates, controls in operation, and support through the audit.

“The contract has a DORA clause. Nobody here knows what it commits us to.”

DORA obliges banks, insurers and payment firms to put certain terms into their ICT contracts: security requirements, help with incidents and, where you support a critical or important function, audit rights and exit plans. The clause is their regulator’s duty, passed down to you.

We read the clause with you, translate each duty into what it means for your operation, and build what is missing: the incident process, the registers, the evidence and the exit documentation.

Signed
The clause: support the customer with ICT incidents
Its first test is a real incident
Mapped
An incident process, rehearsed with the people who would run it
Evidence: the rehearsal record
One clause, traced to its evidence

What you have at the end: Every obligation mapped to an owner and a control, and answers ready for your customer’s audit.

“The customer wants an independent pentest report.”

They want an outside view of how far an attacker would get, written so their security team can trust it.

Black box, grey box, white box or red teaming, as deep as your situation needs, by our certified experts and partners, and Lockpoint signs the report. We report what the findings mean for your business and the patterns behind them. Most tests take 10 to 15 business days from start to report, depending on the target; we retest what you fixed. In a call we show you an anonymised report.

What you have at the end: A report you can send to the customer, a retest that confirms the fixes, and, if you want it, help designing the security practices that stop the pattern from coming back.

It comes from inside

“We grew to eighty people. Nobody owns IT.”

Tools were added one at a time by whoever needed them. Accounts, laptops and the office network now depend on one or two people, often engineers who were hired to build the product.

We take over the digital workplace on the tools you already have: identity, devices, office network, helpdesk and monitoring. First we map it, or start from the assessment you already have, then we close the gaps, then we run it, beside your team or instead of one.

A new hire today
HR emails a start date
An engineer stops product work to set up the laptop and each account
Days before the new hire can work
After we take over
HR sets the start date
The laptop configures itself, accounts are provisioned from the HR list
Laptop and accounts ready on the first morning
One new hire, before and after

What you have at the end: One accountable party for the workplace, measures you see every month, and an IT team you did not have to hire.

Other questions we hear

“Security is on us now, and nobody owns it.”

A customer, an investor or the board asks who is responsible. A full-time CISO is often too early.

A named security lead who owns your posture: management reporting, risk decisions, customer and auditor conversations, vendor reviews, and direction for whoever runs IT day to day.

What you have at the end: One person accountable for security, without a full-time hire.

“The cloud bill keeps growing, and nobody can say which half does anything.”

Workloads, accounts and tools were added for good reasons and never removed.

We review your AWS, GCP or Azure estate against CIS Benchmarks, then do the part most providers have no incentive to do: we shrink it. Duplicate tools cancelled, licences matched to use, workloads right-sized.

What you have at the end: A smaller, standard estate that costs less to run and takes minutes to explain to an auditor.

“Customers now ask how we govern our use of AI.”

Your teams already use AI tools, and your customers want to know where their data goes.

We take stock of actual use, set a policy people can follow and review the vendors behind it, aligned with the EU AI Act and with ISO/IEC 42001 where certification is the goal.

What you have at the end: AI in the same registers and policies as the rest of your estate.

Not sure where you stand?

Start with clarity

We list every tool, account, device, vendor and admin right, draw the real architecture and rank what we find by what it would cost you. Read-only: we change nothing while we look.

What you have at the end: a plan you keep, whether or not we do the work. Fixed scope and a fixed price, agreed in the first call.

Next step

Not sure which one it is? That’s what the call is for.

Thirty minutes with an engineer. Bring the questionnaire, the clause or your org chart.