Cybersecurity audits and advice
If your email or billing system went offline tomorrow, what could you still do? Starting with that question keeps the review focused on the services your business depends on.
Design example
One lost phone. Which accounts depend on it?
In this example, the billing system sends recovery emails to the business inbox. Following that dependency helps decide which risk to address first.
- EmailSecond factor unavailable
- BillingRecovery depends on email
When to get in touch
- Accounts and internet-facing services have accumulated across projects.
- Security tools are in place, but their coverage is hard to assess.
- Several fixes compete for the same people and budget.
Scope of work
- A review of access, configurations and working practices within the agreed scope.
- Findings supported by evidence and tied to potential business impact.
- A prioritised action plan covering dependencies and checks for each fix.
Illustrative audit report excerpt
Recovering access to the business inbox
- Finding
- In this fictional example, sign-in relies on a single phone. The person responsible for billing does not know where the recovery codes are kept.
- Business impact
- If the phone is lost, they could also lose access to recovery emails from the billing system.
- Proposed action
- Assign responsibility for account recovery, keep a backup sign-in method in a protected location and document who can retrieve it.
- Acceptance check
- Using a test account, the responsible person retrieves the backup method and restores access without the usual phone. They record the date and outcome.
Our approach to the work
We start with a disruption that would matter to you. If your email went down, for instance, we’d also look at how you would recover the accounts tied to that inbox. We then prioritise fixes by their impact on your work and what it would take to carry them out.
What you gain
You can explain why one fix takes priority, assign it to the right person and check whether it addresses the original risk.