Insider Threat Investigations Using OSINT

An insider threat investigation starts with a specific concern: internal documents have surfaced online, someone is offering access to your network, or a contractor seems to be working for a competitor. We check what open sources show about that concern, under the direction of your HR and legal teams, and report facts they can rely on.

  • Led by HR and legal
  • Open sources only
  • Proportionate, documented scope
  • Innocent explanations tested first
Short answer

An insider threat investigation examines whether someone with authorized access, such as an employee, contractor or supplier, has misused it. OSINT-S supports these cases with open-source work only: finding leaked internal material, offers of your data or access on criminal markets, and undisclosed outside interests. We work for your HR and legal teams, on a documented concern, and never access private accounts or monitor staff covertly.

What OSINT Adds to an Insider Threat Investigation

Internal logs show what an insider did inside your systems. Open sources show what left, where it went and who outside is involved.

CISA defines an insider as any person who has or had authorized access to or knowledge of an organization's resources, and describes four types of insider threat: unintentional, intentional, collusive and third-party (CISA). Each type leaves different traces outside your network.

Insider typeTypical caseWhat open sources can show
UnintentionalA file shared publicly by mistake, a repository pushed with credentialsWhere the material is exposed, since when, and whether it has been copied
IntentionalData taken to a new employer or posted out of grievanceLeaked documents on paste sites, forums or social media; new companies registered by the subject
CollusiveAn insider working with criminals or a competitorOffers of your access or data on criminal markets and channels; recruitment posts that name your sector
Third-partyA contractor or supplier misusing accessCorporate links, undisclosed interests, related companies and public disputes

Triggers That Justify Opening a Case

A specific, documented concern, not a hunch about a person. The concern sets the scope of everything that follows.

  • Internal documents, source code or customer data found on a public site, forum or channel.
  • A post offering remote access, credentials or data from a company that matches yours.
  • Data loss prevention or access logs showing unusual downloads before a resignation.
  • A competitor launching a product or bid that relies on confidential material.
  • A whistleblower or supplier report naming a conflict of interest.

"Someone seems disloyal" is not a trigger. If the concern is moonlighting or dual employment rather than data misuse, see overemployment checks; if your data has leaked but nobody inside is suspected, a data breach investigation is the better start.

How an OSINT Insider Investigation Runs

Referral through HR or counsel, a written scope, collection, testing of innocent explanations, review and a factual report.

  1. ReferralHR, legal or the security lead describes the concern and the evidence behind it, and confirms who is instructing us.
  2. Scope in writingThe questions, the people and companies covered, the sources allowed and the period, all tied to the concern.
  3. Collect and preservePublic and commercially available sources are searched; relevant items are captured with URL, date and hash.
  4. Test innocent explanationsShared names, old postings, public company information and coincidental timing are ruled out before anything is reported.
  5. Senior reviewA senior analyst checks every finding and removes personal data the case does not need.
  6. Report to counselA factual report with sources and confidence, for your HR and legal teams to decide the next step.

Deliverables, Timelines and Lines We Do Not Cross

A factual report for counsel from 10 business days; urgent leak checks sometimes within a business day.

You receive a report that answers the scoped questions, with preserved captures, a source list, confidence levels and the alternative explanations considered. Checking whether a specific document has been posted publicly is a small task we can sometimes complete within a business day; a focused investigation starts from 10 business days and a case covering several people or companies takes up to about a month. Urgent delivery costs 50% more, the price is fixed after written scoping, and the fee goes down if we miss the agreed date. Work is confidential, under NDA if you wish.

We do not follow staff, monitor their private social media, contact their friends or family, use pretexts or fake profiles, or buy data. If evidence points to a crime, the next step is usually police, decided by you and counsel. Insider cases often surface during an incident; see OSINT incident response support. The broader toolkit sits in OSINT cyber investigations, and the full range of OSINT services for HR and legal teams covers screening and due diligence as well.

Start With a Documented Concern

Ask your HR lead or counsel to send the concern, what has been found so far and who is instructing. We reply with a proposed scope and a fixed price.

Insider Threat OSINT FAQ

Our product roadmap appeared on a public forum a week before a key engineer resigned — how would an insider threat investigation work, and what could you find without touching his accounts?

An insider threat investigation would start with your HR and legal teams agreeing a written scope. We would then trace where and when the roadmap was posted, who posted or reshared it, whether other internal material appears with it, and whether the engineer has registered a new company or joined a competitor. All of this comes from public sources. His personal accounts, devices and private messages stay out of scope.

Someone on a criminal forum is offering remote access to a company that sounds exactly like ours — can you confirm whether it is us and whether an employee is involved?

We can often confirm whether the offer matches your organization by comparing the details in the post, such as sector, revenue, technology and access type, with your environment. Whether an insider is involved is harder: offers come from initial access brokers as well as staff. We report what the post and related activity show, and your security team checks logs and accounts internally.

Can we ask you to monitor a suspected employee's personal Instagram and WhatsApp for signs he is leaking information to a competitor?

No. Ongoing monitoring of an employee's private accounts is rarely proportionate and can breach data protection and employment rules, and accessing private messaging is out of the question. We can check whether specific confidential material has appeared publicly and whether the employee has public links to the competitor, within a scope your counsel approves.

We are a UK employer and HR wants to investigate a staff member quietly without telling them — is that allowed, and who has to sign it off?

Covert monitoring is allowed only in exceptional cases. ICO guidance says it may be justified where telling the worker would prejudice the prevention or detection of suspected crime or gross misconduct, must be authorized by senior management, needs a data protection impact assessment and should be targeted and time-limited. Searching public sources about a specific concern is less intrusive, but the same discipline of documented scope applies.

If your report shows an employee did leak our data, can we use it in a disciplinary hearing or hand it to the police?

Yes, that is what it is designed for. Each finding has a preserved capture with URL, date and hash, the source and a confidence level, and the report records the innocent explanations we ruled out. Your HR team should still give the employee a chance to respond, and counsel decides whether to involve the police.

A contractor's company seems to be quietly linked to a competitor that keeps winning our tenders — is that an insider case, and what would you check?

It can be: CISA counts contractors and vendors with access as third-party insiders. We would map the contractor company's ownership, directors and related companies, look for shared addresses, people or filings with the competitor, and check public tender results and disputes. The findings go to your legal and procurement teams, who decide whether a conflict exists.