<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Windows on secderr</title><link>https://secderr.tech/tags/windows/</link><description>Recent content in Windows on secderr</description><image><title>secderr</title><url>https://secderr.tech/images/og-default.png</url><link>https://secderr.tech/images/og-default.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 11 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://secderr.tech/tags/windows/index.xml" rel="self" type="application/rss+xml"/><item><title>Killing Sweet32 on Windows with PowerShell</title><link>https://secderr.tech/posts/disabling-sweet32-cipher-suites-powershell/</link><pubDate>Wed, 07 Oct 2026 00:00:00 +0000</pubDate><guid>https://secderr.tech/posts/disabling-sweet32-cipher-suites-powershell/</guid><description>Sweet32 (CVE-2016-2183) is one of the most common scan findings on Windows. Here&amp;#39;s how to find and kill 3DES suites with built-in PowerShell cmdlets.</description></item><item><title>The NetBIOS Finding That Wasn't About NetBIOS</title><link>https://secderr.tech/posts/netbios-finding-that-wasnt/</link><pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate><guid>https://secderr.tech/posts/netbios-finding-that-wasnt/</guid><description>A null session finding pointed at NetBIOS. NetBIOS was already off. The real gap was a named pipe exception list our hardening never touched.</description></item></channel></rss>