What Caused the Microsoft Developer Account Lockout?

 The Microsoft developer account lockout incident described in the article highlights how several major open-source security tools—including VeraCrypt, WireGuard, and Windscribe—were suddenly cut off from distributing updates to Windows users. According to the report, developers found their accounts suspended without warning, preventing them from signing drivers or releasing patches. Because Windows requires signed drivers for installation, this effectively froze updates for tens of millions of users, leaving them potentially exposed to unpatched vulnerabilities. ([Aardwolf Security][1])

The root cause appears tied to Microsoft’s Windows Hardware Program and its mandatory identity verification requirements. Developers were expected to submit government-issued identification within a set timeframe, but several affected maintainers they never received proper notification—or even completed verification without regaining access. 

Sniff Smarter, Not Harder: Why Wireshark Preferences Are Your Secret Weapon

Before you even think about hitting that capture button in Wireshark, spending time in Edit → Preferences is one of the smartest moves you can make. Out of the box, Wireshark is powerful—but it’s also generic. Every network is different, every investigation has a purpose, and default settings rarely align perfectly with your environment. By configuring preferences first, you’re essentially tuning Wireshark to your network, which means cleaner captures, better visibility, and less time wasted digging through irrelevant data.

One of the biggest advantages of tweaking preferences early is improved capture and file management. Wireshark relies heavily on heuristics and default port assumptions to identify traffic. 

How to Solve the Four Most Common Problems with PoE++ Devices (Julio Petrovitch)

In 2018, the IEEE 802.3bt (PoE++) standard for Power Over Ethernet was approved. It offered more power, allowing devices like high-powered security cameras to be run on PoE. Which is great – until the installer uses the wrong cable to connect a camera and can’t figure out why it won’t power on.

Having multiple standards makes troubleshooting PoE issues more complicated. For example, many field technicians or network engineers don’t realize that upgrading to new pan-tilt-zoom cameras or to Wi-Fi 7 access points with multiple radios will require a PoE upgrade as well. As offices and warehouses deploy more smart devices that need PoE++, testing becomes more important. This article will explain the PoE++ standard, best practices in PoE deployment and testing, and how to solve several common problems.

What is the PoE++ Standard?

ATM Jackpot for Hackers: Inside the $3.6M Bitcoin Depot Breach

The recent breach of Bitcoin Depot highlights yet another reminder that in the world of cryptocurrency, the weakest link often isn’t the blockchain—it’s everything around it. According to the report, attackers infiltrated the company’s internal IT systems on March 23, 2026, and managed to steal over 50 Bitcoin, valued at roughly $3.6 million. U.S. Securities and Exchange Commission filings revealed the hackers gained access to sensitive credentials tied to digital asset settlement accounts, allowing them to transfer funds before the breach was contained. (BleepingComputer)

Switch Reporting Mystery Solved

For those of you who have read my past articles, I have said countless times that you should "Know your tools". Over the years, I find a lot of examples of this simple statement.  Funny thing is how many times people just shrug their shoulders and say "oh well"...  

A few weeks ago, while troubleshooting, I noticed something odd. There were multiple mac/ip entries for individual switch ports.