About FlagThis

Side Project & Prototype
This is a prototype and a side project which can go down anytime. This is a testbed for me to play with the latest available in AI to build cool new tools on areas I am deeply passionate about. Security is something I've been focused on for a long time, and I've built a version of this site multiple times in the last few years. This latest iteration so far is the best and built the fastest.
Experimental AI Engine & Analytics
FlagThis is powered by a collection of automated news and feed crawlers, combined with complex analysis using NLP tools and state-of-the-art models like Google Gemma 4. The engine autonomously extracts critical and relevant information, clustering related updates together in a structured layout designed specifically to be most meaningful and actionable for security analysts.
Research
The Research section's long-form pieces are drafted with the help of AI research assistants, built on threat-actor and CVE intelligence FlagThis already tracks, and checked against primary sources before publication. Each post is a living document — see the revision history at the bottom of any post for what's changed since it went up.
Git Repository Analysis
Our repository analysis engine scans package manifests (like package.json, requirements.txt, Cargo.toml, etc.) and cross-references dependencies against the OSV (Open Source Vulnerabilities) database to profile open-source supply chain risk.
Vulnerability Intelligence (CVE Tracker)
Our vulnerability dashboard aggregates records from the official MITRE CVE List (v5). To calculate threat velocity and prioritize risk, we enrich CVEs with CISA KEV (Known Exploited Vulnerabilities), EPSS (Exploit Prediction Scoring System) probabilities, public GitHub Proof of Concept (PoC) directories, and real-time rolling discussion counts tracked from the public Mastodon and Bluesky search streams. CVSS scores, affected vendor/product, and CPE configuration data are sourced from the National Vulnerability Database (NVD) API. This product uses the NVD API but is not endorsed or certified by the NVD.
Writing CVE Filter Rules
The search box on the CVE Monitor page understands a small rule syntax, similar to Gmail or GitHub search. Type plain words for a free-text search, or combine field:value rules — multiple rules are ANDed together automatically:
Rule What it does
vendor:ciscoCVEs affecting Cisco. Use a comma list for "any of" — vendor:cisco,juniper
product:"windows server"Quote multi-word product names
cvss>=9CVSS base score threshold. Operators: >= <= > < =
epss>=0.7EPSS exploit-probability threshold (0–1)
kev:trueActively exploited (CISA KEV) only
exploit:trueHas a known public PoC/exploit
year:2026Published in a given year
after:2026-01-01Published on/after this date (before: also works)
-vendor:oracleA leading - excludes a match instead of requiring it
Example: vendor:cisco,juniper kev:true cvss>=9 -product:ios. Whatever you type also becomes your feed: click "RSS feed for this view" on the CVE Monitor page to subscribe to that exact filter, or add &format=rss to the page URL yourself.
Note: the older plain-text-only search (?search=) still works for any links you already have — it's being phased out in favor of the rule syntax above, not removed outright.
Note: As an experimental system driven by AI, data may occasionally be incomplete or contain hallucinations. Always independently verify critical intelligence.
Get daily intelligence briefs in your inbox

View Preferences

Back to Feed

LINK COPIED TO CLIPBOARD