Good Security Starts With Knowing Where You Stand.
Most security gaps are quiet.
An old account keeps access. MFA never gets switched on somewhere important. A vendor covers less than everyone assumes. An employee receives a convincing payment request at exactly the wrong moment.
My security team and I look at the business from the outside in and the inside out, so you can see where the exposure actually is and decide what deserves attention first.
An employee receives a convincing payment request at exactly the wrong moment.
WHERE EXPOSURE HIDES
Security Is Usually More Than One Big Vulnerability.
A company’s security posture is shaped by dozens of smaller decisions across accounts, people, vendors, systems, and processes.
We bring those pieces into one view.
Systems & Access
Security posture assessment across domains, email, cloud accounts, and access controls
Review of externally visible vulnerabilities
MFA coverage and password practices
Administrator access and privilege review
Employee onboarding and offboarding gaps
People & Payments
Email and payment-fraud defences
Wire and invoice-fraud controls
Phishing exposure
Practical employee security awareness
Internal processes around sensitive requests and approvals
Compliance & Readiness
Gap review against relevant client, insurer, or industry requirements
SOC 2 and ISO 27001 readiness considerations
IT provider, MSP, and security-tool review
Basic incident-response planning
Prioritised remediation roadmap
WHO THIS IS FOR
When “We Have IT” Isn’t the Same as “We Know Our Risk.”
You’ve Never Established a Security Baseline.
The business has software, email, cloud accounts, employees, and vendors, but nobody has stepped back and looked at the exposure as a whole.
The diagnostic gives you that baseline.
Clients Are Starting to Ask Harder Questions.
Enterprise customers, partners, and insurers increasingly want to know how you manage access, data, vendors, and security controls.
We identify the gaps before the questionnaire becomes the project.
Something Happened Close Enough to Get Your Attention.
A suspicious login. A fraudulent payment request. A compromised account. An incident at a vendor or another company in your industry.
You don’t need panic.
You need a clear picture of what your own business looks like.
HOW DELIVERY WORKS
See the Risk. Rank the Risk. Address the Risk.
Cybersecurity follows the same diagnostic-first approach behind my consulting work.
STEP_01
1. Establish the Baseline
The Business Diagnostic includes an initial review of the company’s security posture.
We look at the systems, access, controls, vendors, and processes that shape the business’s exposure.
STEP_02
2. Go Deeper Where It Matters
When the baseline identifies areas that warrant deeper assessment, my cybersecurity team conducts the appropriate authorised review using the assessment capabilities we use in our own security business.
All assessment activity is limited to systems the business owns or is authorised to test, with written permission defining the scope.
STEP_03
3. Prioritise the Fixes
You receive a scored report that ranks findings by risk, business impact, and the effort or cost involved in addressing them.
The objective isn’t to produce the longest vulnerability list.
The strongest controls are the ones that still work while invoices move, employees join and leave, vendors need access, and everyone tries to get through a normal workday.
FREQUENTLY ASKED QUESTIONS
Before We Look Under the Hood.
We are a small business. Are we really a target?
Business size alone does not determine cyber risk.
Smaller companies still use email, payment systems, cloud platforms, customer data, employee accounts, and third-party vendors. Many common forms of cybercrime are automated or opportunistic, not aimed only at large enterprises.
The useful question is what exposure your particular business has.
Is this a penetration test?
Not automatically.
The engagement begins with a security-posture diagnostic. If deeper technical testing is appropriate, we define the scope and authorisation before any assessment activity begins.
A penetration test should only be performed against systems the client owns or has explicit authorisation to test.
Will the assessment disrupt our systems?
The initial diagnostic is designed to understand security posture without unnecessarily interfering with normal operations.
If deeper testing is recommended, we agree on the scope, method, authorisation, and potential operational considerations before that work begins.
We already have an IT provider. Why would we need this?
Your IT provider may already be doing valuable work.
The diagnostic helps establish what is currently covered, what responsibilities sit elsewhere, and whether any meaningful gaps remain.
The goal is not to replace a capable provider. It is to make sure assumptions about coverage match reality.
START WITH VISIBILITY
Know What You’re Protecting and Where the Gaps Are.
You don’t need to treat every security concern like an emergency.
You do need a clear view of your systems, access, vendors, people, and existing controls.
We’ll establish the baseline, rank what matters, and give you a practical place to start.