See your business through an attacker’s eyes.
Our open source threat intelligence exposure report shows what publicly available information could reveal about your business, your people and your technology — and what to do about it.
Open source intelligence (OSINT) means analysing information available from public sources. It gives your security decisions an evidence-based starting point.
Find the door nobody is watching.
A staff portal the business stopped using in 2024 is still online. Nobody owns it, patches it or reviews who signs in. Here is how the exposure report brings it to light.
A forgotten sign-in page is worth a closer look. It may still accept old passwords, and its software may not have been updated in years.
Unused staff portal
portal.example.testReachable from the internet. Staff stopped using it in 2024 and no current support contact could be found. Its software version, remaining accounts and login protections are unknown.
- Route 1: password guessingRepeated guesses or passwords reused from other breaches, if nothing limits failed logins.
- Route 2: unpatched softwareA known weakness in software nobody updates could bypass the login altogether.
Public finance guide
Medium priorityAn obsolete contact and payment-change wording could support impersonation.
Technical document
Medium priorityPublished system names could make a false support request more credible.
General contact page
Fine to keepUseful business contact details that are appropriate to publish.
Understand what your public footprint reveals.
Your internet-facing presence
Identify agreed domains, websites, visible services and connections to suppliers. Understand what is observable from outside your business, including assets that need an owner or further verification.
Information that could support an attack
Review public business profiles, documents and other agreed sources for details that could support impersonation, account targeting or reconnaissance — the research an attacker does before choosing a way in.
What it means for your business
See how each finding could affect your people, operations and information. We explain what is confirmed, what it may mean and where more evidence is needed.
A report your team can use.
We agree what to review before starting. That may be a focused look at a few public services or a broader assessment of your business’s public presence.
Executive assessment
A clear summary of the most significant findings, why they matter and the decisions needed from management. The report explains what we reviewed, when and how, including its limits.
Evidence and findings register
Documented observations with source references, affected assets, confidence and practical implications. Findings are checked and explained so your IT team can verify the issue and assess the recommendation.
Prioritised action plan
Recommended changes, who should act and how to check the result. Urgent steps are separated from improvements to schedule and questions that need further investigation.
Findings walkthrough
A discussion with you and your IT provider or security team to explain the findings, agree priorities and consider whether a threat briefing would help with the next decisions.
Why it helps control costs
Start with evidence before buying another security product. Removing unnecessary public information, clarifying asset ownership or closing an avoidable exposure can be a more useful first investment. The report gives your existing team a defined list of work and a way to confirm progress.
Before you begin
What is included in the scope?
We agree the business entities, domains and public sources before collection. Your quote defines coverage, deliverables and the findings walkthrough. Wider coverage is scoped before additional work starts. Any collection relating to a named individual requires explicit consent and a separately agreed scope.
Do you need access to our systems?
A public exposure review does not require internal access or software installation. Any active security testing requires separate written authorisation and an agreed scope.
Is this a vulnerability assessment or penetration test?
The core report analyses public exposure. It does not attempt to exploit systems or prove a vulnerability is exploitable. If technical validation is needed, we can scope it separately and make that distinction clear in the findings.
Will you fix the findings?
The report is designed for your team or IT provider to act on. Implementation and any follow-up verification are agreed separately, so the scope and cost remain clear.
Start with a clearer picture of your exposure.
Tell us what your business needs to protect, what concerns you and which security tools you already use. We’ll help define a useful starting point and a clear scope.