Self-Hosted SpiderFoot OSINT Reconnaissance
Overview
A self-hosted deployment of SpiderFoot, an open-source OSINT (open-source intelligence) automation tool used for footprinting and reconnaissance, packaged as a container behind a reverse proxy.
Why It Exists
OSINT footprinting, gathering and correlating publicly available data about a domain, host, or entity, benefits from a persistent, self-hosted instance. This deployment makes SpiderFoot available internally with stable storage and a clean hostname.
What We Built
A Docker Compose deployment of the treemo/spiderfoot image with a persisted SQLite database volume (spiderfoot.db), resource limits (CPU shares/quota/cpuset and memory caps), and integration with an nginx-proxy network exposing it under a virtual host. Work here is deployment, persistence, and resource-constrained operation of the upstream OSS tool rather than building the scanner itself.
Technologies & Approach
SpiderFoot for the OSINT engine and its many data-source modules; Docker Compose for reproducible deployment with explicit CPU/memory limits; nginx-proxy for virtual-host routing. Framed honestly as self-hosting/operating an open-source tool.
Outcome / Impact
A running, resource-bounded OSINT reconnaissance platform, demonstrating the ability to deploy, persist, and operate security tooling within a managed reverse-proxy environment. Archived.
Capabilities Demonstrated
- Deploying and operating OSINT/reconnaissance tooling (SpiderFoot)
- Containerized self-hosting with resource limits and persistence
- Reverse-proxy/virtual-host integration (nginx-proxy)