About
What is CognitiveCTI?
CognitiveCTI is a self-hosted, AI-powered threat intelligence pipeline that collects, correlates, and summarises cyber threat data from multiple intelligence layers — vendor advisories, independent research, sector-specific feeds, indicators of compromise, and threat actor channels.
This blog is the delivery layer. Every post you read here is generated by the pipeline and published as static content — no databases, no server-side processing, no attack surface.
Intelligence Cadence
Daily Briefs summarise the previous 24 hours of ingested intelligence: new vulnerabilities, active exploitation, campaign updates, and notable threat actor activity.
Weekly Reports aggregate the daily output into a 7-day landscape view with trend analysis and priority recommendations.
Monthly Landscapes provide strategic-level assessments of the threat environment over 30 days, tracking shifts in actor behaviour, vulnerability patterns, and sector targeting.
Bespoke Analyses are deep-dive investigations into specific campaigns, trends, or techniques identified through the correlation engine.
Subscribe via RSS
The RSS feed is a first-class output of this blog. Every post — daily, weekly, monthly, and analysis — is available in the Atom feed at /feed.xml.
Use it to:
- Ingest intelligence into your SIEM or SOAR platform
- Feed a Slack or Teams channel with daily briefs
- Aggregate alongside your existing CTI feeds in a reader
- Build downstream automations with any RSS-compatible tool
The Pipeline
The full architecture, implementation details, and source code are documented at:
- Blog post: Cognitive CTI — Building a Scalable, Self-Hosted Threat Intelligence Pipeline with AI
- Source code: github.com/jwhitt3r/cognitiveCTI
Security
This site is a static HTML document served from a CDN. There is no server-side code, no JavaScript frameworks, no third-party analytics, and no cookies. The theme toggle uses localStorage — that is the extent of client-side state.
Security headers are configured for Content Security Policy, X-Frame-Options, and Referrer Policy. See the _headers or netlify.toml file in the repository for the exact policy.