Colour theme
Book a consultation

What dark web monitoring can tell your business

Assess exposure-monitoring coverage, alert evidence, privacy and response ownership so leaked business information leads to a useful investigation.

A person typing on a laptop in a dimly lit room.

Exposure-monitoring services look for information such as business email addresses in data they can obtain from breaches and other sources. Some suppliers market this as dark web monitoring. The useful question is what an alert lets your business investigate and change.

Treat monitoring as an additional source of evidence. It doesn’t prevent a breach or provide a complete view of where your information has gone.

Ask what the service can observe

The dark web includes services accessed through special networks or software. Leaked information can also appear on ordinary websites, private channels and collections circulated directly between people. A supplier can’t assume access to all of them.

Ask which kinds of sources are covered, what identifiers are monitored and what permission the supplier needs from you. Include former domains and aliases if they matter to your business. Don’t assume monitoring one domain covers personal addresses staff used for work.

Have the supplier explain what happens when a source becomes inaccessible and whether historical data is included. Avoid buying on a promise that every exposure will be found immediately.

Read the alert’s evidence carefully

Look for the claimed source, event date, discovery date, affected identifier and types of information involved. These dates can differ. An old dataset appearing again doesn’t automatically mean there has been a new intrusion.

Have I Been Pwned’s FAQ distinguishes verified and unverified breaches and explains that a password match shows previous exposure without identifying its owner. An email address can also appear in a dataset without the email account itself having been hacked.

Ask how the service labels uncertainty, duplicates and later corrections. A search with no match only means the service’s data doesn’t include it. It says nothing about the state of your systems.

Assign someone to investigate

Agree who receives alerts, who handles them during absences and which findings need escalation. Record the responsibilities in the service agreement or your internal procedure. Paying for a subscription doesn’t mean anyone is watching the alerts around the clock.

Use a safe demonstration alert to test the handoff. Can the recipient identify the affected business account and contact IT without replying to the alert email or following an unfamiliar link?

Don’t ask staff to visit criminal marketplaces or download leaked files to verify a finding. Keep any evidence containing personal information or credentials restricted to the responders who need it.

Respond according to the information exposed

For a suspected credential exposure, have IT assess whether the credential is current or reused and whether the device or account shows other suspicious activity. Change affected credentials through a known service address on a suitable device. Check sessions, recovery settings and connected access where relevant.

The email-recovery guide explains why a password reset may leave other access routes. A suspected vault exposure needs the separate password-manager response review.

If customer, employee or financial information may be involved, involve the business’s incident and privacy leads. Monitoring alerts don’t settle the scope of an incident or its notification requirements. Keep decisions and unresolved questions in the incident record.

Review the service’s own data handling

Ask what you must supply to start monitoring, what the provider stores and who can see the results. Check retention, subcontractors, account access and deletion when the service ends.

Don’t submit a staff member’s personal identifiers or sensitive business records until you’ve agreed why they’re needed and how they’ll be handled. Never provide a live password to an unfamiliar checking site.

Decide whether it adds useful coverage

Compare its cost and response requirements with the gaps in your current controls. Unique passwords, effective MFA, maintained devices and an incident plan remain necessary.

If alerts will sit unread, establish the response process before adding another feed. If you already have one, assess whether the new service supplies evidence you can use to protect specific accounts or investigate a business incident.


Featured Image Credit