<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://amritesh-sec.github.io/threat-intelligence/feed.xml" rel="self" type="application/atom+xml" /><link href="https://amritesh-sec.github.io/threat-intelligence/" rel="alternate" type="text/html" hreflang="en" /><updated>2026-08-24T08:16:16+01:00</updated><id>https://amritesh-sec.github.io/threat-intelligence/feed.xml</id><title type="html">Threat Intelligence | Amritesh</title><subtitle>Threat intelligence research covering OSINT methodologies, digital risk, cyber crime, threat actor analysis, and major data breach investigations by Amritesh. United States, United Kingdom, and European Union focus.</subtitle><author><name>Amritesh</name></author><entry><title type="html">Ransomware in 2026: Threat Actor Ecosystems, Business Impact, and Defensive Strategy</title><link href="https://amritesh-sec.github.io/threat-intelligence/2026/06/ransomware-2026-threat-landscape/" rel="alternate" type="text/html" title="Ransomware in 2026: Threat Actor Ecosystems, Business Impact, and Defensive Strategy" /><published>2026-06-01T00:00:00+01:00</published><updated>2026-06-01T00:00:00+01:00</updated><id>https://amritesh-sec.github.io/threat-intelligence/2026/06/ransomware-2026-threat-landscape</id><content type="html" xml:base="https://amritesh-sec.github.io/threat-intelligence/2026/06/ransomware-2026-threat-landscape/"><![CDATA[<p>Ransomware is no longer a technology problem. It is a business model — one generating billions of dollars annually, operated by organised criminal enterprises with HR functions, customer service desks, and affiliate programmes. Understanding it requires the same analytical rigour applied to any sophisticated business threat.</p>

<p>This report analyses the 2026 ransomware landscape using primary sources from CISA, the FBI, NCSC UK, and Europol — translating threat actor behaviour into actionable intelligence for security teams and business leadership.</p>

<hr />

<h2 id="the-ransomware-business-model--how-it-actually-works">The Ransomware Business Model — How It Actually Works</h2>

<p>Modern ransomware operates primarily through a <strong>Ransomware-as-a-Service (RaaS)</strong> model. The structure mirrors legitimate software distribution:</p>

<p><strong>Core Developer Group</strong> — builds and maintains the ransomware payload, encryption mechanisms, and payment infrastructure. Takes a percentage of every ransom payment.</p>

<p><strong>Affiliate Programme</strong> — criminal actors license the ransomware, conduct their own intrusions, deploy the payload, and negotiate ransoms. Affiliates typically retain 70–80% of the ransom.</p>

<p><strong>Initial Access Brokers (IABs)</strong> — a specialised criminal layer that compromises networks and sells access to affiliates. A compromised Fortune 500 network with domain admin credentials can sell for $50,000–$100,000 on underground markets.</p>

<p>This division of labour means a ransomware attack may involve five or more distinct criminal actors, each specialising in one phase of the operation. Attribution is consequently complex — the group named in headlines is typically the RaaS operator, not the affiliate who conducted the actual intrusion.</p>

<hr />

<h2 id="key-threat-actor-groups--2026">Key Threat Actor Groups — 2026</h2>

<h3 id="lockbit-30-and-successors">LockBit 3.0 and Successors</h3>

<p>LockBit was the dominant RaaS operation through 2024, disrupted by Operation Cronos in February 2024 — a joint operation by the FBI, NCSC UK, Europol, and twelve other agencies. However, law enforcement disruption of RaaS operations historically results in rebrand rather than elimination.</p>

<p>Key characteristics of LockBit-lineage operations:</p>
<ul>
  <li>Double extortion standard — data exfiltration before encryption</li>
  <li>Affiliate programme with aggressive recruitment</li>
  <li>Bug bounty programme for identifying flaws in their own malware</li>
</ul>

<p><strong>Reference:</strong> <a href="https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-075a">FBI/CISA Joint Advisory AA23-075A</a></p>

<h3 id="alphvblackcat">ALPHV/BlackCat</h3>

<p>Notable for being written in Rust — technically sophisticated, cross-platform, and difficult to detect. ALPHV conducted the Change Healthcare attack in early 2024, causing significant disruption to US healthcare billing infrastructure and highlighting the systemic risk posed by single points of failure in critical sectors.</p>

<p><strong>Reference:</strong> <a href="https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-353a">CISA Advisory AA23-353A</a></p>

<h3 id="cl0p">Cl0p</h3>

<p>Distinguished by exploiting zero-day vulnerabilities in managed file transfer software at scale — the MOVEit campaign in 2023 compromised hundreds of organisations simultaneously. This “mass exploitation” model contrasts with targeted RaaS operations and requires different defensive strategies.</p>

<hr />

<h2 id="evolving-tactics--what-has-changed-in-2026">Evolving Tactics — What Has Changed in 2026</h2>

<h3 id="intermittent-encryption">Intermittent Encryption</h3>

<p>Modern ransomware encrypts only portions of files rather than entire files — dramatically increasing encryption speed while still rendering data unusable. This reduces the time window for detection and response.</p>

<h3 id="exfiltration-before-encryption--triple-extortion">Exfiltration Before Encryption — Triple Extortion</h3>

<p>The standard model is now:</p>
<ol>
  <li><strong>Exfiltrate data</strong> — steal before encrypting</li>
  <li><strong>Encrypt systems</strong> — operational disruption</li>
  <li><strong>Threaten public disclosure</strong> — reputational damage</li>
  <li><strong>Threaten regulatory notification</strong> — compliance pressure (GDPR, HIPAA fines)</li>
</ol>

<p>Some operations have added a fourth threat: DDoS attacks against victims who refuse to pay.</p>

<h3 id="targeting-backup-infrastructure">Targeting Backup Infrastructure</h3>

<p>Ransomware operators now specifically target backup systems — identifying and destroying backups before deploying ransomware, eliminating the primary recovery mechanism. This makes offline, immutable backups non-negotiable.</p>

<h3 id="living-off-the-land-lotl">Living off the Land (LotL)</h3>

<p>Affiliates increasingly use legitimate system administration tools — PowerShell, WMI, PsExec, Cobalt Strike — to conduct intrusion and lateral movement, making detection significantly harder than signature-based approaches allow.</p>

<hr />

<h2 id="business-impact-analysis--2026">Business Impact Analysis — 2026</h2>

<p>The financial impact of ransomware extends beyond the ransom itself:</p>

<table>
  <thead>
    <tr>
      <th>Impact Category</th>
      <th>Description</th>
      <th>Estimated Cost Range</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Ransom payment</td>
      <td>Direct payment (if made)</td>
      <td>$500K–$5M+ (enterprise)</td>
    </tr>
    <tr>
      <td>Business interruption</td>
      <td>Lost revenue during downtime</td>
      <td>Often exceeds ransom</td>
    </tr>
    <tr>
      <td>Recovery costs</td>
      <td>IR firm, forensics, rebuild</td>
      <td>$1M–$10M+</td>
    </tr>
    <tr>
      <td>Regulatory fines</td>
      <td>GDPR, HIPAA, SEC</td>
      <td>Up to 4% global turnover</td>
    </tr>
    <tr>
      <td>Legal liability</td>
      <td>Customer/partner litigation</td>
      <td>Variable, potentially significant</td>
    </tr>
    <tr>
      <td>Reputational damage</td>
      <td>Customer churn, stock impact</td>
      <td>Long-tail, difficult to quantify</td>
    </tr>
  </tbody>
</table>

<blockquote>
  <p>The average total cost of a ransomware incident — including all categories above — significantly exceeds the ransom payment itself. Organisations that focus solely on ransom negotiation without accounting for full recovery costs systematically underestimate ransomware risk.</p>
</blockquote>

<hr />

<h2 id="sectors-under-greatest-pressure--united-states--united-kingdom">Sectors Under Greatest Pressure — United States &amp; United Kingdom</h2>

<p><strong>Healthcare</strong> — Electronic health records, operational technology dependencies, and regulatory sensitivity make healthcare a high-value target. US healthcare has faced persistent attacks from multiple groups following the Change Healthcare incident’s demonstrated impact.</p>

<p><strong>Financial Services</strong> — High-value data, regulatory notification requirements, and reputational sensitivity. UK financial services firms face dual regulatory pressure from the PRA/FCA and ICO.</p>

<p><strong>Legal</strong> — Law firms hold client data across multiple industries. A single successful attack can expose data from dozens of client companies.</p>

<p><strong>Manufacturing and Critical Infrastructure</strong> — OT/IT convergence creates new attack surfaces. US CISA Critical Infrastructure Security advisories frequently highlight manufacturing targeting.</p>

<hr />

<h2 id="defensive-framework--prioritised-by-effectiveness">Defensive Framework — Prioritised by Effectiveness</h2>

<p>The following controls are prioritised based on their documented effectiveness in preventing ransomware intrusion and limiting blast radius:</p>

<h3 id="tier-1--prevent-initial-access">Tier 1 — Prevent Initial Access</h3>

<p><strong>Multi-Factor Authentication (MFA)</strong> — The single most effective control. The majority of ransomware incidents begin with compromised credentials. MFA defeats credential-based access even when credentials are stolen. Implement on all external-facing systems without exception.</p>

<p><strong>Patch Management</strong> — Maintain a patch cycle that addresses critical and high severity vulnerabilities within 72 hours of publication. Cl0p’s success demonstrates that slow patching of known vulnerabilities remains highly exploitable.</p>

<p><strong>Email Security</strong> — Phishing remains a primary initial access vector. Implement DMARC, DKIM, SPF, and anti-phishing controls. Conduct regular phishing simulations.</p>

<h3 id="tier-2--detect-and-contain">Tier 2 — Detect and Contain</h3>

<p><strong>Endpoint Detection and Response (EDR)</strong> — Signature-based antivirus is insufficient. EDR with behavioural detection identifies LotL techniques that signature scanning misses.</p>

<p><strong>Network Segmentation</strong> — Limit lateral movement. Flat networks allow ransomware to propagate from a single compromised endpoint to full domain compromise. Implement least-privilege network access.</p>

<p><strong>Log Aggregation and SIEM</strong> — Centralised logging enables detection of lateral movement patterns, unusual authentication activity, and large-scale data exfiltration.</p>

<h3 id="tier-3--recover-without-paying">Tier 3 — Recover Without Paying</h3>

<p><strong>Immutable, Offline Backups</strong> — The 3-2-1-1-0 rule: three copies, two media types, one offsite, one offline/immutable, zero errors on restore testing. Test restores regularly — untested backups frequently fail at the moment of greatest need.</p>

<p><strong>Incident Response Plan</strong> — A documented, tested IR plan reduces recovery time and cost significantly. Include ransomware-specific playbooks with decision trees for payment considerations.</p>

<hr />

<h2 id="official-resources">Official Resources</h2>

<ul>
  <li><a href="https://www.cisa.gov/stopransomware">CISA Stop Ransomware</a> — comprehensive US guidance</li>
  <li><a href="https://www.ncsc.gov.uk/ransomware/home">NCSC UK Ransomware Guidance</a> — UK-specific response guidance</li>
  <li><a href="https://www.fbi.gov/how-we-can-help-you/safety-resources/scams-and-safety/common-scams-and-crimes/ransomware">FBI Ransomware Resources</a> — reporting and resources</li>
  <li><a href="https://www.europol.europa.eu/publications-events/main-reports/iocta-report">Europol IOCTA Report</a> — EU organised cyber crime analysis</li>
  <li><a href="https://attack.mitre.org/campaigns/">MITRE ATT&amp;CK Ransomware</a> — threat actor campaign tracking</li>
</ul>

<hr />

<h2 id="conclusion">Conclusion</h2>

<p>Ransomware in 2026 is a mature criminal industry, not a collection of opportunistic attacks. Defending against it requires understanding the business model — who the actors are, how they operate, and what controls systematically disrupt their operations.</p>

<p>The organisations that suffer most are those that treat ransomware as a technology problem rather than a business risk requiring board-level attention, adequate resourcing, and tested response capability.</p>

<p>The next report in this series covers <strong>Initial Access Brokers</strong> — the criminal layer that makes modern ransomware operations possible, and how organisations can detect and disrupt IAB activity before ransomware is deployed.</p>

<hr />

<p><em>Intelligence corrections, additional sources, or sector-specific questions? <a href="https://amritesh-sec.github.io/contact/">Get in touch</a>.</em></p>]]></content><author><name>Amritesh</name></author><category term="threat-intelligence" /><category term="ransomware" /><category term="threat-actors" /><category term="CISA" /><category term="cyber-crime" /><category term="incident-response" /><summary type="html"><![CDATA[A comprehensive analysis of the 2026 ransomware threat landscape — key threat actor groups, evolving tactics, business impact analysis, and a prioritised defensive framework for US and UK organisations.]]></summary></entry><entry><title type="html">OSINT Techniques: A Practical Guide from Beginner to Advanced</title><link href="https://amritesh-sec.github.io/threat-intelligence/2026/04/osint-techniques-beginner-to-advanced/" rel="alternate" type="text/html" title="OSINT Techniques: A Practical Guide from Beginner to Advanced" /><published>2026-04-05T00:00:00+01:00</published><updated>2026-04-05T00:00:00+01:00</updated><id>https://amritesh-sec.github.io/threat-intelligence/2026/04/osint-techniques-beginner-to-advanced</id><content type="html" xml:base="https://amritesh-sec.github.io/threat-intelligence/2026/04/osint-techniques-beginner-to-advanced/"><![CDATA[<p>Open source intelligence — OSINT — is one of the most powerful and widely misunderstood disciplines in cybersecurity. It requires no hacking tools, no exploits, and no illegal access. Everything happens in plain sight. The question is whether you know where to look.</p>

<p>This guide covers OSINT from first principles to advanced methodology — the way security professionals actually use it, not the oversimplified version you find in most tutorials.</p>

<hr />

<h2 id="what-osint-actually-is">What OSINT Actually Is</h2>

<p>OSINT is the collection and analysis of information from <strong>publicly available sources</strong> to produce actionable intelligence. The term originated in military and intelligence communities — the CIA, GCHQ, and NATO all have dedicated OSINT units — and has since become a core discipline in cybersecurity, investigative journalism, law enforcement, and corporate due diligence.</p>

<p>The key word is <em>publicly available</em>. OSINT does not involve accessing private systems, intercepting communications, or any form of unauthorised access. Everything covered in this guide operates entirely within legal boundaries when used responsibly.</p>

<blockquote>
  <p><strong>Ethical Boundary:</strong> OSINT techniques must only be used on yourself, your organisation, or targets you have explicit written authorisation to research. Unauthorised collection and profiling of private individuals may violate GDPR (UK/EU), CCPA (California), CFAA (US), and Computer Misuse Act 1990 (UK).</p>
</blockquote>

<hr />

<h2 id="the-osint-framework">The OSINT Framework</h2>

<p>Before touching any tool, understand the methodology. OSINT professionals follow a structured process:</p>

<h3 id="phase-1--define-your-intelligence-requirement">Phase 1 — Define Your Intelligence Requirement</h3>

<p>What exactly do you need to know? Define your target and your objective before starting. Undirected collection produces noise, not intelligence.</p>

<p>Examples of clear intelligence requirements:</p>
<ul>
  <li><em>What is the external attack surface of [organisation]?</em></li>
  <li><em>What personal information about [individual] is publicly accessible?</em></li>
  <li><em>What technologies does [company] use in their infrastructure?</em></li>
</ul>

<h3 id="phase-2--passive-reconnaissance">Phase 2 — Passive Reconnaissance</h3>

<p>Collect information without directly interacting with the target. No packets sent, no footprint left.</p>

<h3 id="phase-3--active-reconnaissance">Phase 3 — Active Reconnaissance</h3>

<p>Interact with public-facing infrastructure to gather additional data. This leaves traces and requires explicit authorisation.</p>

<h3 id="phase-4--analysis--correlation">Phase 4 — Analysis &amp; Correlation</h3>

<p>Raw data is not intelligence. Analysis — finding connections, confirming accuracy, assessing reliability — is where OSINT becomes valuable.</p>

<h3 id="phase-5--reporting">Phase 5 — Reporting</h3>

<p>Document findings clearly with source attribution, confidence levels, and recommendations.</p>

<hr />

<h2 id="beginner-level--starting-points">Beginner Level — Starting Points</h2>

<h3 id="google-dorking">Google Dorking</h3>

<p>Google’s advanced search operators are among the most underutilised OSINT tools available. Used correctly, they surface information that basic searches never return.</p>

<p>Essential operators:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>site:target.com              — limits results to a specific domain
filetype:pdf site:target.com — finds specific file types
inurl:admin site:target.com  — finds URLs containing specific strings
intitle:"index of"           — finds exposed directory listings
"@target.com" filetype:xls   — finds spreadsheets containing email addresses
</code></pre></div></div>

<p><strong>Real example:</strong> <code class="language-plaintext highlighter-rouge">site:target.com filetype:pdf "confidential"</code> frequently surfaces internal documents accidentally published to public web servers.</p>

<p>Official reference: <a href="https://support.google.com/websearch/answer/2466433">Google Search Operators Documentation</a></p>

<h3 id="whois-lookup">WHOIS Lookup</h3>

<p>Every registered domain has a WHOIS record containing registration data. Even with privacy protection enabled, historical records often contain real contact details.</p>

<p>Tools:</p>
<ul>
  <li><a href="https://who.is">who.is</a> — clean UI, historical records</li>
  <li><a href="https://domaintools.com">domaintools.com</a> — professional-grade, tracks changes over time</li>
  <li><code class="language-plaintext highlighter-rouge">whois target.com</code> — command line, fastest for bulk queries</li>
</ul>

<p>What you can find: registrant name, email, organisation, registration date, name servers, registrar.</p>

<h3 id="certificate-transparency-logs">Certificate Transparency Logs</h3>

<p>Every TLS certificate issued is logged publicly. This reveals <strong>subdomains</strong> — often including staging environments, internal tools, and forgotten infrastructure.</p>

<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c"># Using crt.sh — free, no account required</span>
curl <span class="s2">"https://crt.sh/?q=%.target.com&amp;output=json"</span> | jq <span class="s1">'.[].name_value'</span> | <span class="nb">sort</span> <span class="nt">-u</span>
</code></pre></div></div>

<p>Or simply visit: <code class="language-plaintext highlighter-rouge">https://crt.sh/?q=%.target.com</code></p>

<p>This consistently surfaces subdomains that DNS brute-forcing misses entirely.</p>

<hr />

<h2 id="intermediate-level--infrastructure-intelligence">Intermediate Level — Infrastructure Intelligence</h2>

<h3 id="shodan">Shodan</h3>

<p>Shodan is a search engine for internet-connected devices. It continuously scans the entire internet and indexes banners, service versions, open ports, and SSL certificates.</p>

<p>What security professionals use it for:</p>
<ul>
  <li>Finding exposed databases (MongoDB, Elasticsearch, Redis)</li>
  <li>Identifying outdated software versions in production</li>
  <li>Mapping an organisation’s full external attack surface</li>
  <li>Finding industrial control systems (ICS/SCADA) exposed to the internet</li>
</ul>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code># Shodan search examples
org:"Target Company Ltd"          — all assets belonging to an organisation
ssl:"target.com"                  — assets with target.com in SSL certificate
port:3389 country:GB              — exposed RDP servers in the UK
product:"Apache httpd" version:2.2 — vulnerable Apache versions
</code></pre></div></div>

<p>Official resource: <a href="https://help.shodan.io">Shodan Documentation</a></p>

<blockquote>
  <p>According to <a href="https://cisa.gov">CISA’s 2025 advisory on internet-exposed assets</a>, exposed management interfaces remain one of the top vectors for initial access in ransomware attacks.</p>
</blockquote>

<h3 id="theharvester">theHarvester</h3>

<p>A purpose-built OSINT tool for gathering emails, subdomains, and employee names from public sources.</p>

<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c"># Installation</span>
pip <span class="nb">install </span>theHarvester

<span class="c"># Basic usage</span>
theHarvester <span class="nt">-d</span> target.com <span class="nt">-b</span> google,bing,linkedin,shodan <span class="nt">-l</span> 500
</code></pre></div></div>

<p>Sources it queries: Google, Bing, LinkedIn, Hunter.io, Shodan, and more. Produces a consolidated list of email addresses, names, and infrastructure details.</p>

<h3 id="maltego">Maltego</h3>

<p>Maltego is the professional standard for OSINT data correlation. It visualises relationships between entities — people, organisations, domains, IP addresses, social accounts — through an interactive graph.</p>

<p>Community edition is free. Professional licence is used by law enforcement agencies, corporate investigators, and penetration testers worldwide.</p>

<p>Key transforms for security research:</p>
<ul>
  <li>Domain → DNS records → IP addresses → hosting provider</li>
  <li>Email address → breached credentials → associated accounts</li>
  <li>Organisation → employees → LinkedIn profiles → personal emails</li>
</ul>

<hr />

<h2 id="advanced-level--social-media-intelligence-socmint">Advanced Level — Social Media Intelligence (SOCMINT)</h2>

<h3 id="metadata-extraction-from-images">Metadata Extraction from Images</h3>

<p>Every image taken on a smartphone contains EXIF metadata — which can include GPS coordinates, device model, software version, and timestamp.</p>

<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c"># Using ExifTool — the standard for metadata extraction</span>
exiftool image.jpg

<span class="c"># Extract GPS coordinates specifically</span>
exiftool <span class="nt">-gpslatitude</span> <span class="nt">-gpslongitude</span> image.jpg
</code></pre></div></div>

<p>This is how journalists and investigators have geolocated conflict zone images, verified the location of leaked documents, and identified the devices used to capture specific photographs.</p>

<p><strong>Defensive note:</strong> Strip EXIF data before publishing any images using tools like ExifTool or online services like <a href="https://www.exifpurge.com">exifpurge.com</a>.</p>

<h3 id="reverse-image-search--beyond-google">Reverse Image Search — Beyond Google</h3>

<p>Google reverse image search is the starting point, but advanced OSINT uses multiple engines simultaneously:</p>

<table>
  <thead>
    <tr>
      <th>Tool</th>
      <th>Strength</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><a href="https://tineye.com">TinEye</a></td>
      <td>Tracks image across time — finds first appearance</td>
    </tr>
    <tr>
      <td><a href="https://yandex.com/images">Yandex Images</a></td>
      <td>Superior facial recognition for SOCMINT</td>
    </tr>
    <tr>
      <td><a href="https://bing.com/visualsearch">Bing Visual Search</a></td>
      <td>Strong for product and location identification</td>
    </tr>
    <tr>
      <td><a href="https://pimeyes.com">PimEyes</a></td>
      <td>Face search engine — powerful but use ethically</td>
    </tr>
  </tbody>
</table>

<h3 id="breach-data-intelligence">Breach Data Intelligence</h3>

<p>Have I Been Pwned (HIBP) is the authoritative public resource for checking whether an email address appears in known data breaches.</p>

<ul>
  <li><a href="https://haveibeenpwned.com">haveibeenpwned.com</a> — individual lookups</li>
  <li><a href="https://haveibeenpwned.com/API/v3">HIBP API</a> — programmatic bulk checking for organisations</li>
</ul>

<p>For security professionals conducting authorised assessments, breach data reveals credential reuse patterns — one of the most dangerous vulnerabilities in any organisation.</p>

<blockquote>
  <p><strong>Reference:</strong> Troy Hunt’s HIBP database currently contains over 14 billion breached records. <a href="https://www.ncsc.gov.uk/collection/passwords/updating-your-approach">NCSC UK recommends HIBP</a> as part of password security policy.</p>
</blockquote>

<hr />

<h2 id="osint-tool-reference--complete-list">OSINT Tool Reference — Complete List</h2>

<table>
  <thead>
    <tr>
      <th>Category</th>
      <th>Tool</th>
      <th>Free</th>
      <th>Notes</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Search</td>
      <td>Google Dorking</td>
      <td>✅</td>
      <td>Master this first</td>
    </tr>
    <tr>
      <td>DNS</td>
      <td>ViewDNS.info</td>
      <td>✅</td>
      <td>Historical DNS records</td>
    </tr>
    <tr>
      <td>Certificates</td>
      <td>crt.sh</td>
      <td>✅</td>
      <td>Subdomain enumeration</td>
    </tr>
    <tr>
      <td>Infrastructure</td>
      <td>Shodan</td>
      <td>Partial</td>
      <td>Essential for professionals</td>
    </tr>
    <tr>
      <td>Email OSINT</td>
      <td>theHarvester</td>
      <td>✅</td>
      <td>Open source</td>
    </tr>
    <tr>
      <td>Social</td>
      <td>Maltego CE</td>
      <td>✅</td>
      <td>Community edition</td>
    </tr>
    <tr>
      <td>Image</td>
      <td>ExifTool</td>
      <td>✅</td>
      <td>Metadata extraction</td>
    </tr>
    <tr>
      <td>Breaches</td>
      <td>HaveIBeenPwned</td>
      <td>✅</td>
      <td>Industry standard</td>
    </tr>
    <tr>
      <td>Geolocation</td>
      <td>GeoGuessr Pro</td>
      <td>Partial</td>
      <td>Image geolocation training</td>
    </tr>
    <tr>
      <td>Dark Web</td>
      <td>OnionScan</td>
      <td>✅</td>
      <td>Research use only</td>
    </tr>
  </tbody>
</table>

<hr />

<h2 id="defending-against-osint">Defending Against OSINT</h2>

<p>Understanding OSINT is only half the picture. The other half is protecting your organisation from being the target.</p>

<p><strong>For organisations:</strong></p>
<ol>
  <li>Conduct regular attack surface reviews using the tools above</li>
  <li>Audit what employee information is publicly visible on LinkedIn</li>
  <li>Implement strict email format policies to reduce harvesting</li>
  <li>Remove sensitive metadata from all published documents and images</li>
  <li>Monitor certificate transparency logs for unexpected subdomains</li>
  <li>Use <a href="https://alerts.google.com">Google Alerts</a> for your organisation name and key personnel</li>
</ol>

<p><strong>For individuals:</strong></p>
<ol>
  <li>Audit your own digital footprint quarterly</li>
  <li>Enable privacy protection on domain registrations</li>
  <li>Strip metadata from images before publishing</li>
  <li>Review and restrict social media visibility settings</li>
  <li>Check yourself on HIBP regularly</li>
</ol>

<hr />

<h2 id="official-resources--references">Official Resources &amp; References</h2>

<ul>
  <li><a href="https://osintframework.com">OSINT Framework</a> — comprehensive tool directory</li>
  <li><a href="https://www.ncsc.gov.uk/information/protective-dns">NCSC UK — Protective DNS</a></li>
  <li><a href="https://cisa.gov/cyber-hygiene-services">CISA — Reduce Internet-Facing Attack Surface</a></li>
  <li><a href="https://enisa.europa.eu/publications/enisa-threat-landscape-2025">ENISA Threat Landscape 2025</a></li>
  <li><a href="https://www.bsi.bund.de/EN/Topics/ITGrundschutz/itgrundschutz_node.html">BSI Germany — IT Grundschutz</a></li>
  <li><a href="https://haveibeenpwned.com/API/v3">Have I Been Pwned API Documentation</a></li>
</ul>

<hr />

<h2 id="conclusion">Conclusion</h2>

<p>OSINT is not a collection of hacking tricks. It is a disciplined intelligence methodology that, when applied rigorously and ethically, gives security professionals a complete picture of what an attacker can learn about a target before launching an attack.</p>

<p>Master the basics — Google dorking, WHOIS, certificate transparency — before moving to advanced tools. The most impactful OSINT finds consistently come from the simplest techniques applied thoughtfully.</p>

<p>The next article in this series covers <strong>Social Engineering Attack Patterns</strong> — how attackers use OSINT intelligence to build targeted phishing and pretexting campaigns.</p>

<hr />

<p><em>Have corrections, additions, or want to share your own OSINT research? <a href="https://amritesh-sec.github.io/contact/">Get in touch</a>.</em></p>]]></content><author><name>Amritesh</name></author><category term="osint" /><category term="OSINT" /><category term="reconnaissance" /><category term="Shodan" /><category term="Maltego" /><category term="SOCMINT" /><category term="passive-recon" /><summary type="html"><![CDATA[A comprehensive, practical guide to open source intelligence — covering passive reconnaissance, social media intelligence, tools, and real-world methodology used by security professionals.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://amritesh-sec.github.io/threat-intelligence/assets/images/posts/osint-guide-cover.png" /><media:content medium="image" url="https://amritesh-sec.github.io/threat-intelligence/assets/images/posts/osint-guide-cover.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry></feed>