OSINT Attacks: The Exposure Gap That Phishing Drills Miss

·

It's Cybersecurity Awareness Month but are we overlooking something pretty obvious?

Every October, with Cybersecurity Awareness Month, MFA, strong passwords, and phishing simulation drills take center stage. Each time this training repeats in real-world environments, one frustrating question persists: if attackers already know an employee’s name, job title, home address, and even their manager’s pet’s name, what exactly can training that merely lowers phishing click-through rates actually stop? Public-source attacks drive directly into this gap.

Attackers already know you

OSINT (Open Source Intelligence) attacks are an extended form of social engineering that builds an attack surface using only publicly available information, without any hacking. A name, company, job title, phone number, and address can easily be collected simply by querying a few people-search sites. When current employer information from LinkedIn is layered on, cases are repeatedly reported of new hires receiving CEO gift card scam emails. One operator shared that upon reactivating their own LinkedIn account, roughly half of their users began receiving emails impersonating them. Cases have also been shared of operators approaching employees by directly naming them during phone calls, as well as operators who deleted LinkedIn entirely or reduced it to skeleton profiles unconnected to their current employer.

The blind spot in awareness month curriculum

The importance of MFA, EDR, and phishing awareness training is undeniable. However, the recognition that the human layer has already been effectively compromised at the pre-attack stage is missing. If an attacker has gathered a manager’s pet’s name through data brokers and then calls the help desk, technical controls alone cannot block that point of entry. The “training to suspect” emphasized in awareness month education is effective only against callers without context, but is powerless against callers equipped with context. As AI-based impersonation becomes widespread, this asymmetry continues to widen.

A four-step practical framework

To integrate the OSINT attack surface as a standard assessment item in the consulting process, the following sequence is effective.

1. Make the risk visible through live demonstration — In a client meeting, query people-search sites using the names of executives and security team members to show actual exposed data, and most immediately recognize the risk. “Is it acceptable for our information to be exposed to that extent?” is a typical reaction, and most organizations have never self-assessed their employee exposure levels.

2. Distribute a quarterly self-audit checklist — Have employees self-check their LinkedIn profile visibility, internal directory listings, contact information in email signatures, and personal cell phone exposure. The principle that information identifying a current employer should not be registered on public sites unless one is actively job-seeking should be explicitly stated in internal guidelines.

3. Opt out during new hire onboarding — Before a new hire posts their joining on LinkedIn, guide them to complete opt-out procedures at major data brokers. Review of fake email and phone number issuance services should also be addressed at this stage.

4. Annual risk grading — Explicitly add an “OSINT Attack Surface” section to the consulting report template, and update employee exposure grades as A/B/C. The key is formal incorporation as part of client advisory items, not simple risk flagging.

Tools available for assessment

Public digital footprint mapping can begin with manual queries alone. If automation is needed, public tools such as Maltego CE, SpiderFoot, theHarvester, and Mozilla Monitor can be reviewed for reference. (These are practical recommendation tools not discussed in the original thread and are not official specifications.) The conceptual flow is as follows.

※ Note: The following commands are conceptual simulation examples (Illustrative Example, not official spec).

# Collect emails and subdomains for your domain using theHarvester
theHarvester -d example.com -b linkedin,google,bing -l 200

# Automated scan of your domain with SpiderFoot
spiderfoot -s example.com -t all

Anti-patterns to avoid

It is typical to assess awareness level solely by phishing simulation click rates while omitting OSINT exposure assessment. Operations that treat data broker opt-out as a one-time project without re-monitoring for new leak pathways are cited as common failure patterns. As AI impersonation becomes widespread, organizations that do not specify suspicious-activity reporting hotlines and callback or one-time code authentication procedures in their manuals become targets. The illusion that technical controls alone can close every surface is especially dangerous in the face of the OSINT attack surface.

Shift the focus of Awareness Month from “suspicion” to “exposure control”

Even when phishing simulation pass rates are high, if the OSINT attack surface remains open, the attack entry point exists outside the training category. Raising employee digital exposure to a regular checklist item from the consulting stage is the substantive defense line that awareness month overlooks. The original discussion can be reviewed in the r/sysadmin thread.

What to do right now

  • Query people-search sites with your own name and note the exposed items.
  • On LinkedIn, minimize the public visibility of current employer name, department, title, and email.
  • Check whether your internal email signature includes unnecessary contact information such as cell phone or direct numbers.
  • Run a single email collection against your domain using theHarvester to gauge data broker exposure range.
  • Add a “Complete data broker opt-out before announcing employment” item to the new hire onboarding guide.

Reference source

This article was prepared after reviewing the following source: r/sysadmin — It’s Cybersecurity Awareness Month but are we overlooking something pretty obvious?

Leave a Reply

Your email address will not be published. Required fields are marked *