See yourself as a target
Open Source
Intelligence (OSINT)
We find what an attacker can learn about your organization and people before touching a single system: exposed staff details, leaked credentials, forgotten domains, document metadata, vendor ties. You learn which of it would make a phishing email convincing or an intrusion easier, and what you can take down.
Look, never touch
What they know
before they knock.
Collection is passive: we read public sources and never touch your systems or contact your people. Findings are mapped to the MITRE ATT&CK reconnaissance tactic, and personal data is kept to what proves the exposure, then handled under retention terms we agree in writing.
Phase 01 · Scope & limits
Agree what is fair game.
A written scope naming the organization, brands, domains and staff groups in play, and what stays out.
- Executives and high exposure roles named for focused review.
- Personal accounts and family members kept out unless you approve.
- Retention and handling of personal data agreed up front.
Phase 02 · Organization
Learn how you look from outside.
A profile of structure, vendors, locations and processes an attacker could reference by name.
- Org charts rebuilt from public profiles and job postings.
- Vendors, tools and suppliers named in public material.
- Email formats and naming conventions confirmed from public sources.
Phase 03 · Technical footprint
Find the infrastructure you forgot you had.
Domains, hosts and services found in public records, matched against what you think you own.
- Certificate transparency, DNS history, Shodan and Censys.
- Code and secrets exposed in public repositories.
- Metadata pulled from documents on your public sites.
Phase 04 · Exposure
Check what has already leaked.
Which corporate accounts appear in known breach data, and whether those exposures still matter.
- Corporate email addresses checked against known breaches.
- Leaked credentials flagged, never tried against your systems.
- Paste sites and forums searched for mentions of your organization.
Phase 05 · Attack scenarios
Turn the findings into the attacks they enable.
Ranked scenarios showing how each exposure would feed a phishing pretext or an intrusion.
- Pretexts an attacker could build from what we found.
- Takedown and cleanup steps for each exposure you control.
- A readout with the practitioner who did the research.
Agree what is fair game.
A written scope naming the organization, brands, domains and staff groups in play, and what stays out.
- Executives and high exposure roles named for focused review.
- Personal accounts and family members kept out unless you approve.
- Retention and handling of personal data agreed up front.
Learn how you look from outside.
A profile of structure, vendors, locations and processes an attacker could reference by name.
- Org charts rebuilt from public profiles and job postings.
- Vendors, tools and suppliers named in public material.
- Email formats and naming conventions confirmed from public sources.
Find the infrastructure you forgot you had.
Domains, hosts and services found in public records, matched against what you think you own.
- Certificate transparency, DNS history, Shodan and Censys.
- Code and secrets exposed in public repositories.
- Metadata pulled from documents on your public sites.
Check what has already leaked.
Which corporate accounts appear in known breach data, and whether those exposures still matter.
- Corporate email addresses checked against known breaches.
- Leaked credentials flagged, never tried against your systems.
- Paste sites and forums searched for mentions of your organization.
Turn the findings into the attacks they enable.
Ranked scenarios showing how each exposure would feed a phishing pretext or an intrusion.
- Pretexts an attacker could build from what we found.
- Takedown and cleanup steps for each exposure you control.
- A readout with the practitioner who did the research.
Key benefits
Shrink what a stranger can learn.
Exposed documents, stale accounts and leaked secrets can often be removed or rotated. You get the list, with an owner for each item, before an attacker builds a pretext around it.
Leaders are the names attackers impersonate and target. We show what is public about high exposure roles so you can trim it and brief the people who handle their requests.
The findings make later phishing and red team scenarios realistic, because they are built from what is actually public about your organization rather than from a generic template.
What you get
What lands on
your desk.
Three handoffs that turn public information into a cleanup list your team can work through.
The document
The report
What an attacker could learn, organized by people, organization and infrastructure, with source references, the attack each exposure enables, and the cleanup step for each one.
The working file
The exposure tracker
One row per exposure with source, sensitivity, the owner who can remove it and status. Personal details are minimized so the file can circulate inside your team.
The conversation
The readout
A session with the practitioner who did the research. We walk through the scenarios that worry us most and agree which exposures to remove first and which staff to brief.
Client case studies
Real engagements.
Documented outcomes.
In their words
"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
In their words
"ForgePath has become a trusted security partner for YHB. Beyond helping us comply with FTC Safeguards requirements, they provide the governance, oversight, and guidance we rely on to protect our firm and our clients’ data. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
Trusted by industry leaders.
Common concerns
Asked about
your privacy.
Straight answers from the practitioners who do the work. If yours is not here, ask us directly.
No. This work is passive. We read public sources only. If we find a login page or a leaked credential, we record it and stop there. Active testing belongs to a penetration test or a social engineering engagement.
We collect only what demonstrates an exposure, keep personal accounts and family members out of scope unless you approve, and redact personal details in the report. Handling and destruction of the evidence follow terms we agree in writing.
Your organization's names and brands, the domains you know about, and any staff groups you want prioritized. Less is fine. Part of the point is seeing what we find without your help.
It is a natural first step. The domains we find can widen the scope of an external penetration test, and the pretexts we identify can shape a phishing campaign or a red team scenario.
Ready?
Bring us
the problem.
One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.








