Industrial Cyber (industrialcyber.co)

https://industrialcyber.co

Discovered via S2 2026-05-22 research. Covers EU/UK CNI enforcement, ICS/OT vulnerability disclosures; published in-depth analysis of South Staffordshire ICO fine and utility cyber oversight implications. Candidate — promote to active after 3 runs with content contribution. | 2026-06-20 full audit (v2.62): live=Y, drill=Y. FETCH → webfetch https://industrialcyber.co (listing) then webfetch the per-article industrialcyber.co/<section>/<slug>/ for the full body. AVOID: Nothing to avoid — plain WebFetch works on both listing and articles. High publishing cadence (several items/day).. | 2026-07-05 admiralty audit: C — established OT/ICS trade journalism mixing original features with heavy re-reporting; keep active. NOTE: now UA-403s WebFetch AND the bridge (was WebFetch-OK); liveness confirmed via WebSearch only — fetch method needs re-work, not a demotion. | 2026-07-09 (v3.16 2009Z run): article pages + listing 403 WebFetch / 401 jina-reader on every transport (confirmed again S1/S3/S4), BUT the WordPress RSS feed https://industrialcyber.co/feed/ returns full items 200. Switched fetch_method webfetch->rss with rss_url set (re-applying the 1211Z fix that was lost in a sources.json --theirs merge). Fetch the feed; do NOT retry direct article/listing WebFetch. | 2026-07-10: homepage + jina reader both returned upstream 403/challenge for S3 and S4 (8th consecutive run failing). Persistent anti-bot/WAF block, not death; RSS feed path https://industrialcyber.co/feed/ recovered content on earlier runs — prefer the feed. NOT demoted (403 is transport). | 2026-07-10 (2009Z run): article pages 403 across webfetch/jina/bridge for S3+S4 again (transport/anti-bot block, not death); the /feed/ RSS path remained reachable via jina for rotation accounting. NOT demoted (403 never demotes). | 2026-07-11: recovered via RSS/jina bridge after recent 403 fetch-gaps — reachable, no in-window content this run; failure counter reset. | 2026-07-12 (2009Z run): transport block lifted — `fetch_source.py feed https://industrialcyber.co/feed/` returned HTTP 200 via method:direct (9 items, freshest 2026-07-10, no 403/jina escalation needed) after several runs of 403; failure counter reset. Working recipe: rss feed, direct — no bridge/jina escalation required. | 2026-07-13 intel run: Cloudflare-class anti-bot challenge on BOTH direct fetch and jina-reader fallback, third consecutive run (S3). 403/challenge never demotes (rule A1); keep as coverage gap. Retest periodically; recover if the challenge relaxes or a structured feed appears. | 2026-07-14 intel run: RECIPE CONFIRMED (S3): the RSS feed https://industrialcyber.co/feed/ returns full items via DIRECT fetch (9 items); only the bare homepage 403s/challenges. Prefer the feed direct; no jina/bridge escalation needed. No in-window content this run.