Leaked Information Analysis
Whether information said to be out is real, and yours
We answer on evidence whether your information has really got out and, if so, what needs doing now.
On the dark web and elsewhere outside your company, we look for information about you, such as staff accounts or customer data, and trace it back to where it first appeared.
Is the information said to be out there real, and is it really ours?
Where and when it first appeared, our judgement on whether it is yours and why, and what needs doing urgently, such as which accounts to change straight away.
Expert reviewed
When it fits
- You have had a tip about a leak
If you have been told your customers' data is being traded, we start by checking whether it is true and whether it concerns you.
- Your name is coming up outside
You have heard your company's name came up on the dark web, but not what was posted or where.
- You are concerned about staff accounts
You want to know whether staff logins and passwords appear in leaked lists, and whether any of those accounts are still in use.
- An old leak is going round again
Data from an incident years ago is being posted as if it were new, and you need to know whether it is a fresh leak or old material reposted.
The SAFE SQUARE approach
Back to the first appearance
The same data is often posted again and again, so we find where and when it first appeared, to tell the real source.
What is still a risk today
With your staff we work out which accounts on a leaked list are still in use, and which records really are your customers'.
Ready to use in your explanations
Sources, timing and the evidence of relevance are set out in the shape of an explanation, so you can use them as they stand in reports to management and answers to customers.
What we look at
What turns up, and where, is different every time; below are things we often look at.
Information exposed
- Staff logins and passwords
- Customer data
- Internal documents and business files
- Access keys and credentials for systems
Where it appears
- Dark web forums and sale listings
- Paste and file-sharing sites where leaked data is posted
- Messaging channels and online communities
- Posts that mention your company
What we establish
- Where and when it first appeared
- Whether it is an old leak posted again
- Whether it is really yours, and the evidence
- Whether it includes accounts still in use
How it runs
Set the targets
We settle the company and brands to look at and the information to check, and start from any tip you have received.
Find and trace
We look for related posts and data in external sources, including the dark web, and trace the same data back to where and when it first appeared.
Check relevance
With your staff we check whether it is really yours, and whether it includes accounts still in use.
Report
We explain the source and timing, the evidence of relevance, and what to check and act on first.
A tip you have received is followed as an in-depth investigation; to keep watching for your name and accounts, it runs as monitoring. Which form it takes is decided with you. See the three ways to run it
What you receive
Source and timing
Where and when the information first appeared, and whether it has been posted again, with the evidence.
Whether it is yours, and why
Whether it is really your information, and whether it includes accounts still in use, with the evidence.
What could not be confirmed, and why
What the available information could not settle, why, and how it can be followed up.
What to check and act on first
Based on the likely impact, what to do first, such as which accounts need their passwords changed.
This analysis focuses on whether information is already out, and where it came from. How information could leak is looked at in Privacy Risk Analysis.
A ‘customer data for sale’ post on the dark web, and a list of staff logins
One sale post naming your company; one list of 120 staff logins
| What we checked | Finding | Evidence |
|---|---|---|
| Where the sale post came from | Reposted | The same data first appeared on another site years ago, and was posted again with only the company name changed. |
| The customer data in the post | Not yours | Its fields and samples match another company's leaked data, and your staff found that it does not match your customer records. |
| 120 staff logins | 3 in use | Checked with your staff: 117 belong to leavers or have had their passwords changed already, and 3 are still in use. |
| Where the list came from | Still to confirm | It looks as if it came from an outside service staff signed up to with their work email, but which service has not been confirmed (assumption). |
- What to do first
- Change the passwords on the 3 accounts still in use straight away and turn on multi-factor authentication. Use the evidence that the sale post is another company's reposted data in your report to management and your answers to customers.