---
### Appendix B – Raw Data Samples - `whois_example.txt` – WHOIS dump for `example.com`. - `shodan_api_example.json` – Shodan JSON output for `api.example.com`. - `tweets_@example_2024.csv` – Exported tweet list (date, text, retweets).
## 5. Findings ### 5.1 Digital Footprint Overview | Asset Type | Identifier | Owner/Contact (if known) | Public Exposure | Comments | |------------|------------|--------------------------|-----------------|----------| | Domain | `example.com` | Registrant: John Doe (privacy‑protected) | Public website, SSL, subdomains | … | | Sub‑domain | `api.example.com` | Same as above | Exposes REST API (no auth) | Potential data leak | | IP Range | `192.0.2.0/24` | ISP: ExampleNet | Visible on Shodan (open ports 22, 80, 443) | … | | Social Account | `@example` (Twitter) | Owner: Jane Smith | 12k followers, 300 tweets | Recent tweet mentions partnership with X | | GitHub Repo | `example/example‑app` | Owner: example | 5 public repos, 1 contains `.env` file | **Sensitive** – contains API keys | | Document | `annual_report_2023.pdf` (found via Google) | Public | Contains executive emails | **PII** exposure | OSINT Report.zip
---
---
---
---
## 7. Recommendations (Prioritized) 1. **Immediate Actions (0‑7 days)** - Rotate all exposed secrets (API keys, tokens). - Secure admin interfaces (auth, MFA, IP restrictions). - Reset passwords for compromised accounts; enforce 2FA. 2. **Short‑Term (7‑30 days)** - Implement a **DMARC** policy and monitor email spoofing. - Conduct a **code‑review audit** for all public repositories. - Deploy a **web‑application firewall (WAF)** for public services. 3. **Mid‑Term (30‑90 days)** - Harden DNS (DNSSEC, registrar lock‑up). - Establish a continuous **OSINT monitoring** pipeline (e.g., SpiderFoot automation). - Provide security awareness training focused on phishing. 4. **Long‑Term (90 + days)** - Adopt a formal **vulnerability management** program. - Periodic **penetration testing** and **red‑team** exercises. - Review and update **incident response** playbooks.
## 6. Analysis & Impact Assessment | Threat Vector | Likelihood | Impact | Overall Rating | Mitigation Recommendations | |---------------|------------|--------|----------------|----------------------------| | Publicly exposed API keys | High | Data exfiltration, service abuse | Critical | Rotate keys, implement secret management, restrict IP ranges. | | Unauthenticated admin panel | Medium | System takeover, data manipulation | High | Add authentication, IP whitelist, enable MFA. | | Credential leak on Pastebin | High | Account takeover, credential stuffing | Critical | Force password reset, monitor for abuse, adopt password‑less auth. | | Phishing using brand domain | Medium | Reputation damage, credential theft | Medium | Deploy DMARC/DKIM/SPF, employee training, brand monitoring. | | Geo‑tagged interior photos | Low | Physical security reconnaissance | Low | Strip EXIF data from publicly posted images. | --- ### Appendix B – Raw Data Samples - `whois_example
### Appendix C – Reference List 1. **OSINT Framework** – https://osintframework.com/ 2. **MITRE ATT&CK** – https://attack.mitre.org/ 3. **NIST SP 800‑115** – Technical Guide to Information Security Testing and Assessment.
You now have a fully‑structured OSINT report that can be saved as a document and compressed into `OSINT Report.zip` for distribution. Happy hunting—and remember to stay within the bounds of the law and respect privacy! **Immediate Actions (0‑7 days)** - Rotate all exposed