OSINT Index

Purpose

This index is the root entry point for the OSINT branch of the cybersecurity atlas.

Use it to: - collect and evaluate publicly available information - separate source discovery from active recon - build evidence-backed target, company, asset, and people context - support attack-surface mapping, scope validation, privacy thinking, and reporting

Use Reference Registry — OSINT as the source of truth for references in this branch. Return to Cybersecurity Index for root navigation across branches.

Before this branch: - Foundations (Phase 0).

Recommended learning order

Phase 1 — Core model

1. osint
2. osint-triage
3. osint-reporting

Phase 2 — Search and public web

4. search-engine-operators
5. google-dorking

Phase 3 — People, accounts, and public identity

6. social-media-osint
7. email-and-phone-osint
8. image-and-location-osint

Phase 4 — Organization and exposure context

9. company-osint
10. breach-and-leak-intelligence

Core OSINT Cluster

Foundations

• osint
• osint-triage
• osint-reporting

Search and public web

• search-engine-operators
• google-dorking

People and identity context

• social-media-osint
• email-and-phone-osint
• image-and-location-osint

Company and exposure context

• company-osint
• breach-and-leak-intelligence

Cross-links to other branches

Offensive / recon

• Passive Recon
• Company Mapping
• Scope Validation
• Recon to Testing Handoff

Attack surface mapping

• External Attack Surface
• Endpoint Discovery
• Third-Party Exposure

Web and API security

• Open Redirect
• OAuth Security
• API Inventory Management

Suggested future notes

• historical-internet-artifacts
• public-document-metadata
• github-osint
• username-enumeration
• map-and-satellite-osint
• domain-registration-osint
• osint-opsec
• source-reliability-grading

Possible future playbooks

• build-osint-case-file
• triage-public-leak-exposure
• map-company-public-footprint
• verify-image-location

Branch maintenance notes

• Keep OSINT notes focused on public-source collection, reliability, ethics, evidence handling, and reporting.
• Keep active probing in index and vulnerability testing in Web/API/Security Playbooks.
• Treat people-focused OSINT with extra care: minimize collection, avoid harassment, and prefer defensive or authorized contexts.
• Use unresolved wikilinks for future atomic notes so Obsidian can track the branch expansion.

References

• Foundational: OSINT Framework — https://osintframework.com/
• Foundational: Bellingcat Online Investigation Toolkit — https://bellingcat.gitbook.io/toolkit
• Foundational: Google Search Help: refine searches — https://support.google.com/websearch/answer/2466433/refine-web-searches