OneConsult

https://www.oneconsult.com/en/blog/

Swiss security firm, incident response and DFIR blog. 2026-05-08 audit: WebFetch returned 5 dated posts on pentests, SOC, IR with most recent 2026-04-09. | 2026-06-20 full audit (v2.62): live=Y, drill=Y. FETCH → webfetch https://www.oneconsult.com/en/blog/ (listing) then webfetch each /en/blog/<cat>/<slug>/ article. AVOID: Cadence is slow (most recent 2026-06-02), treat 'no new item in window' as normal, not a fetch failure.. | 2026-07-05 admiralty audit: B (HIGH->B) status active->active, Swiss DFIR firm, original IR research; live via WebFetch, latest 29.06.2026. No status change. | 2026-09-29: content check saw the Imunify360 anti-bot wall on /en/blog/ (extract 199 B 'One moment, please...'; direct JSON 'Access denied by Imunify360'). The wall is intermittent per request (roughly 5 of 8 feed fetches pass from this egress), never path-specific. Working recipe: python3 tools/fetch_source.py feed https://www.oneconsult.com/en/feed/ 30 (English blog-only WordPress RSS, newest 2026-09-08, ~monthly cadence, longest observed gap 48 d) - RETRY 3-4x a few seconds apart on 'Access denied'/HTTP 415 before logging a failure - then extract <item link> (same retry). Set rss_url, fetch_method webfetch -> rss, max_staleness_days 90. /feed/ (no /en/) mixes German blog with careers posts; do not use. (2026-09-29T2134Z-audit) | 2026-09-30: the feed answered one call in three this morning (Access denied between), and on a miss the health check fell back to the blog page, which has no security vocabulary and read as irrelevant. source_health.py now retries a feed record whose feed read failed, so the recipe stands. (2026-09-30T0634Z-audit)