Microsoft Security Response Center (MSRC)

https://www.microsoft.com/en-us/msrc/blog

Microsoft Security Response Center blog (added 2026-05-08). MSRC handles vuln coordination & Patch Tuesday context, distinct from MSTIC's actor-tracking. The landing redirects to www.microsoft.com/en-us/msrc/blog and renders as a navigation shell on WebFetch, drill into individual /blog/YYYY/MM/<slug>/ posts. Candidate; promote to active after 3 runs with content contribution. | 2026-06-20 full audit (v2.62): live=Y, drill=Y. FETCH → WebSearch `site:msrc.microsoft.com/blog 2026` (or known post URL) then webfetch the per-post https://www.microsoft.com/en-us/msrc/blog/YYYY/MM/<slug>; individual posts render substantively even though the listing is an SPA shell.. AVOID: Don't WebFetch the /blog landing, it 301s to www.microsoft.com/en-us/msrc/blog and renders as an SPA navigation shell. Bridge url on the listing also returns only the SPA shell. There is NO working RSS (/blog/feed/ returns the HTML shell, not XML). Do not confuse with the `msft-secblog recent` bridge feed, that is the separate Microsoft Security Blog, not MSRC.. | 2026-07-05 admiralty audit: A, Microsoft PSIRT, first-party authority over its own product vulnerabilities/disclosure. Reliability HIGH->A, status stays active. A justified: definitive first-party PSIRT channel. Fetch per-post URLs (listing is an SPA shell, no working RSS). | 2026-10-13 (S1): the old msrc.microsoft.com/blog URL now 301-redirects to www.microsoft.com/en-us/msrc/blog; url updated in place; no in-window post.