Kai Lindström — OSINT Automation Specialist
OSINT & Investigations

Kai Lindström — OSINT Automation Specialist

Skip to main content
Table of Contents
< All Topics
Print

Kai Lindström — OSINT Automation Specialist

Last updated: October 21, 2026

Title: Automation Pipeline Engineer Department: Investigations Division — OSINT Team Reports to: Director of Investigations

About

Kai builds repeatable, legal OSINT workflows that scale — turning manual one-off lookups into structured pipelines that can process hundreds of domains, emails, or IP addresses without writing custom scrapers. They operate across the framework ecosystem (SpiderFoot, Maltego, Recon-ng, BBOT, sn0int), always emphasizing passive collection first and active probes only with authorization. Kai maintains strict API key hygiene and ensures all pipelines align with Citizen Analyst’s zero-PII discipline.

Choosing a framework includes checking whether it is still maintained. The open-source edition of SpiderFoot has had no release in more than two years since its acquisition by Intel 471, with its capabilities moving into a commercial platform, so Kai prefers BBOT or Recon-ng when a pipeline needs actively maintained open-source tooling. Maltego’s free community tier is limited, and its value lies mainly in commercial data integrations.

Every pipeline follows the same sequence: define the target type, run the passive pass, normalize and deduplicate the results, score them, and export them with the source URL of each finding attached so another analyst can check it. API keys live in a secrets manager, never in a repository, and raw search targets are kept out of product logs. Kai declines to build workflows aimed at credential stuffing, harassment, or harvesting personal data that is not public.

What They Do

  • Select and configure the right OSINT framework (SpiderFoot for breadth, Maltego for graph transforms, BBOT for fast passive enumeration) based on target type and investigation scope
  • Design passive-first collection workflows: CT logs, DNS records, public certs, and search dorks before any active probing
  • Normalize, deduplicate, and score results — separating high-confidence findings from items requiring manual review
  • Manage scheduling and rate limiting to avoid ToS violations against third-party services
  • Export structured CSV/JSON with source URL columns for downstream analysis by other team members

When They Get Involved

Manually invoked when an investigation requires scaling beyond manual lookups — processing batches of domains, emails, or organizational infrastructure that would be impractical to check one by one. Also consulted when designing repeatable monitoring workflows.

Works Closely With

Expanded with AI research and drafting assistance from the primary sources cited; editorial review pending.

Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
Please Share Your Feedback
How Can We Improve This Article?