NCSC UK

https://www.ncsc.gov.uk/section/keep-up-to-date/reports-advisories

UK National Cyber Security Centre. /section/keep-up-to-date/threat-reports is a landing page with no actual reports listed. Substantive content lives at /section/keep-up-to-date/reports-advisories (joint advisories, CISA-co-signed) and /section/keep-up-to-date/malware-analysis-reports (technical malware analyses). Drill into individual reports for citation; never cite the landing page itself. NB: the RSS feed at /api/1/services/v1/report-rss-feed.xml has been observed to lag the HTML by months — prefer WebFetch on the HTML index. | 2026-06-20 full audit (v2.62): live=Y, drill=Y. FETCH → bridge: python3 tools/fetch_source.py url https://www.ncsc.gov.uk/section/keep-up-to-date/reports-advisories (parse real article slugs from the index, then `url <article_url>`; article body is JS-rendered so read <title> + <meta description> + dates rather than <p> text). WebFetch the HTML index also works for discovery.. AVOID: RSS at /api/1/services/v1/report-rss-feed.xml lags ~13 months (newest item May 2025) — do NOT use it for recency. CRITICAL: WebFetch's AI summariser MANGLES the article slugs (it returned /news/alert-ncsc-issues-advice-following-global-targeting-fortinet... which 404s; the real slug is /news/advice-following-global-targeting-of-fortinet-firewalls-and-vpn-gateways). Always take the slug from the bridge index, not from WebFetch's reconstructed URL. Never cite the landing page itself.. | 2026-07-05 admiralty audit: A (HIGH->A) status active->active — UK national cyber authority, original threat reporting + advisories; bridge index live/drillable (take slugs from bridge, not WebFetch). Justified A: primary national authority. No change. | 2026-07-11 audit: WORKING RECIPE FOUND — the combined feed https://www.ncsc.gov.uk/api/1/services/v1/all-rss-feed.xml (reports + guidance + blog) is FRESH (items dated within days, verified 2026-07-11), unlike report-rss-feed.xml which lags months. Fetch via `python3 tools/fetch_source.py feed https://www.ncsc.gov.uk/api/1/services/v1/all-rss-feed.xml 20` for discovery, then drill into item links for citation. This replaces the consent-banner-blocked HTML listing as the discovery path; the HTML listing kept returning a cookie-consent shell to WebFetch AND jina (recurring 'recipe gap' in July run records despite green last_successful_fetch — reachability is not readability). | 2026-07-13: reported RSS/feed path unresolved (report-feed.rss and all-feeds.xml 404'd); fetch_method=bridge still reaches the advisories listing — feed URL needs re-verification, kept active (feed drift, not death). | 2026-07-26 weekly quality audit: the 2026-07-13 note calling the feed path unresolved is STALE: the combined feed https://www.ncsc.gov.uk/api/1/services/v1/all-rss-feed.xml (already on the record as rss_url) resolved cleanly this run. Lead with the feed for discovery; the HTML listing is a JS/consent shell with no drillable rows.