Asked to conduct OSINT? Learn how CTI teams build repeatable investigation workflows, manage attribution, and protect operational security from day one.
Cyber Threat Intelligence has traditionally operated within structured boundaries: parsing indicators of compromise (IoCs), tracking CVEs, mapping known malware families, and enriching SIEM alerts from automated feeds. But automated feeds are reactive by design. An IP flagged this morning was hostile yesterday, and a cataloged hash only documents an attack that was already executed. In most cases, feeds cannot tell you what an adversary is planning right now.
Meanwhile, modern adversaries are conducting operations in plain sight. Threat actors collaborate in real-time on Telegram, advertise exfiltrated databases on clear web forums, and stage payloads on public code repositories. Because structured telemetry often misses these early signals, CTI teams are now being asked to take on open-source intelligence (OSINT) workflows.
However, navigating these decentralized, hostile spaces demands dedicated tradecraft. Without isolated infrastructure and managed operational security, conducting OSINT outside the perimeter risks burning the investigation and inviting adversary retaliation back into the enterprise.
Here is how CTI teams can transition from passive feed consumption to active open-source hunting safely and from scratch.
Step 1: Establish Your Infrastructure
Before collecting and analyzing open-source intelligence, teams must have purpose-built controls in place to manage online attribution. Interacting directly with adversary-controlled infrastructure, or even passively scraping underground boards, exposes the investigator’s digital fingerprint.
To protect operational security, investigators often rely on the following tools:
- VPN/Tor (Virtual Private Network): While useful for basic masking or routing traffic across exit nodes, they only obscure the transport layer. They do nothing to defend against browser fingerprinting techniques that identify unique hardware configurations despite an obfuscated IP.
- VMs (Virtual Machines): VMs isolate untrusted payloads from the host OS, but rebuilding, patching, and resetting snapshots for every investigative session creates massive operational drag. A misconfigured network adapter or accidentally copied clipboard data can still trigger an attribution leak.
- Managed Attribution Network: Dedicated infrastructure that masks or customizes an analyst’s complete digital signature, including IP address, geographic location, and device telemetry. While they control the outward-facing footprint, standalone network configurations alone do not protect endpoints from malicious web payloads or browser exploits unless paired with full session isolation.
Digital investigators often heavily rely on VPN, TOR, and virtual machines. However, setting them up (and resetting them) properly can be a highly technical and time-consuming task. To facilitate OSINT workflows, organizations rely on cloud-based managed attribution (MA) platforms to conduct professional investigations due to the numerous benefits, such as in-region access, isolated environments, and auditable controls. By executing sessions within a disposable cloud container entirely separated from corporate endpoints, investigators gain:
- True browser isolation: Code executes in the cloud; only encrypted pixels stream to the user’s screen. Drive-by downloads, zero-days, and exploit kits cannot touch the analyst’s machine or corporate network.
- Custom egress and digital fingerprints: Analysts can align their apparent IP address, time zone, system locale, and device headers with the target’s operating environment—allowing access to geo-restricted resources without raising alarms.
- Auditable governance and evidence chains: Secure capture tools preserve metadata, hashes, and timestamps for downstream legal or incident response teams, while centralized audit logs maintain internal compliance.
Step 2: Anchor Investigations to Requirements (IRs and PIRs)
Without structured intelligence requirements, OSINT turns into open-ended web browsing that wastes analyst hours and yields low-value noise. Therefore, it is critical that CTI teams identify the type of information they are trying to obtain and why it matters to the organization. Clear intelligence requirements allow analysts to address a specific intelligence gap instead of collecting everything that might be relevant.
To define their intelligence needs, organizations commonly use two types of intelligence requirements:
Priority Intelligence Requirements (PIRs)
A PIR identifies an important question that an organization needs to know the answer to understand a security threat or make a particular security decision. It is usually defined or approved by senior leadership and is periodically reviewed to make certain that it stays in line with the organization’s evolving security risks and business priorities.
Intelligence Requirements (IRs)
An IR breaks down the broader question into specific questions that CTI analysts can investigate and answer. For OSINT investigators, these questions should be answerable (at least in part) using open sources. They should also be narrow enough to guide a specific investigation and specific enough that analysts can tell when the requirements have been satisfied.
How PIRs and IRs Work in Practice
In practice, a single PIR may generate several IRs. For example, a PIR asking whether the organization is exposed to a ransomware group may be broken down into different IRs such as identifying recent victims, the tools commonly used in attacks, and the potential initial access channels.
The next step would be to translate these requirements into OSINT collection requirements. Analysts need to identify sources that help answer these questions. For example, in order to investigate whether a particular threat actor is selling access to financial institutions’ systems, it would require monitoring darknet marketplaces, Telegram channels and data leak repositories for content mentioning financial organizations. Analysts could then gather details like the mentioned organization, access type, publication date/time and any supporting evidence. These findings can be correlated with threat intelligence feeds and other internal security information to determine if that activity presents a credible risk.
Step 3: Run a Repeatable OSINT Lifecycle
To make findings defensible and repeatable, OSINT workflows must mirror the intelligence lifecycle:
| Phase | Core Objective | CTI & OSINT Application |
| 1. Access | Reach target sources without attribution risk | Blend into target environments with configurable egress nodes, geolocation, and device/browser fingerprints. Access surface, deep, and dark web (Tor) forums or gated communities via managed identities and SMS profiles without exposing corporate infrastructure. |
| 2. Capture | Secure primary evidence at the source | Safely harvest live content, underlying source code, network details, and rich media without running malicious scripts locally. Artifacts and flattened pages are organized, hashed, and timestamped in secure cloud storage for verifiable evidence chains. |
| 3. Analyze | Transform raw data into actionable intelligence | Process multilingual dumps, transcribe/translate media, inspect suspicious underlying code, and map complex relationships across accounts, domains, and entities. A persistent knowledge base correlates findings directly to active investigation requirements. |
| 4. Report | Package and disseminate finished intelligence | Structure cases with built-in case management, visual research timelines, and exhibit markups. Produce finished intelligence briefs and alerts within an isolated environment to deliver clear, validated findings to SOC and IR teams. |
| Extend & Connect (Integration) | Bridge investigations to enterprise security systems | Use APIs and pre-built integrations to push validated indicators, case notes, and deliverables directly into downstream SIEMs, TIPs, SOAR playbooks, or ticketing systems for immediate remediation. |
Step 4: Apply OSINT Across Core CTI Use Cases
OSINT investigations can be used to support various activities within the CTI world. Real-world OSINT extends internal telemetry into three primary investigative domains:
Validating Data Leaks and Extortion Campaigns
When an extortion group or ransomware affiliate claims to hold corporate data, CTI teams must verify validity without triggering an incident response false alarm. The following open-source services can facilitate with this investigation:
- TGState
- Lyzem
- Ahmia, Torch, DuckDuckGo Onion Service
- haveibeenpwned
- Firefox Monitor
- Dehashed
- Pastebin
- Library of Leaks
Analysts should treat information obtained from open-sources as untrusted and consider the security risk associated with accessing resources controlled by threat actors. This is exactly why leveraging the correct infrastructure before conducting investigations is critical.
Breach samples may contain malware, and accessing data leak repositories may track unwanted visitors. Accessing threat actors’ malicious websites, such as phishing and ransomware websites, means direct interactions with adversary-controlled infrastructure. Analysts should access such resources from isolated, attributed environments instead of using regular web browsers with VPN access, which does not provide adequate security and privacy against emerging tracking techniques and advanced cyberthreats.
Monitoring Threat Actor Activities
CTI teams can use OSINT tools and techniques to monitor and track threat actor chatter, advertised services, attack claims, and changes in their tactics, tools, and procedures (TTPs). This allows analysts to identify targeted attacks against their organization and understand how a particular threat actor operates.
However, effective monitoring requires more than conducting periodic searches; analysts may need to access or monitor the same Telegram channels and forums where threat actors recruit and advertise their stolen information, in addition to monitoring darknet marketplaces to get early notification about breached data advertised for sale.
Proactive Exposure and Attack Surface Mapping
The third OSINT use case is identifying public information about an organization that an attacker could potentially exploit. This includes exposed employee access credentials, leaked documents, impersonation websites, fraudulent social media accounts and any sensitive information published on public platforms. Digital exposure is cumulative. A stale credential dump, an orphaned token in a public repo, and a spoofed login portal seem isolated on their own—together, they hand an adversary a complete intrusion path that no single finding would ever reveal.
Teams can cross-reference breach repositories like Have I Been Pwned for exposed corporate accounts and deploy tools like VirusTotal and urlscan.io to dissect suspicious domains and network telemetry. (Just ensure submissions don’t inadvertently leak sensitive corporate data to public search archives.) Similarly, analysts must proactively monitor public code hubs like GitHub for leaked API tokens, hardcoded credentials, and infrastructure configs that reveal pathways into the network.
Step 5: Close the Loop with Internal Telemetry
The final step is cross-correlating external findings with internal telemetry. If an OSINT investigation reveals a threat actor peddling network access to organizations in your vertical, analysts must pivot back inside the enterprise. That means querying SIEM, EDR, VPN, and identity logs for indicators of compromised credentials or unusual egress.
Embedding OSINT into these existing workflows bridges the gap between external open-source collections, commercial feeds, and internal telemetry. Most importantly, it prevents investigations from becoming dead-end research projects by ensuring intelligence directly powers real-time security operations.
The Only Silo Your Security Team Actually Needs
Being asked to take on open-source intelligence can feel like a daunting mandate, especially when teams are already stretched thin. But OSINT does not have to be chaotic or dangerous. When anchored to specific priority intelligence requirements and supported by purpose-built isolated environments, it turns raw, messy web chatter into decisive security outcomes.
The objective is not to collect everything on the internet. It is to give your analysts the safety, tradecraft, and infrastructure they need to investigate what matters most to your business without putting the enterprise at risk. Request a demo and see how Silo Workspace empowers CTI and OSINT workflows while eliminating the risk out of online investigations.