From what I've read elsewhere, it sounds like the data itself wasn't actually classified, so there wouldn't be any additional oversight beyond what is given to regular network traffic
I’m guessing you’ve never worked for the Federal Govt. before. The level of Liferism[1], ill equipped technical contractors, clueless management, and just plain old general political fuckery, is stupefyingly gargantuan.
[1] Lifers are employees who just exist, do the absolute bare minimum, and collect a paycheck.
Have low aspirations, and set up camp in a boring job akin to a jail cell, in a place no one wants to be, doing something no one wants to do, and work alongside washed up people who are not inspiring to talk to, and perhaps have never had the chance to even try to become an inspiring role model for others.
Liferism looks like a DMV employee. Postal workers are often lifers, so not all lifer jobs are inherently disappointing, but certainly none are glamourous.
In the 1990's the internet introduced some existential threats to lifers working for the USPS, and since then, the USPS has weathered some rough seas. Putting yourself in the position of a lifer is not precisely enviable, since forces from beyond the protective shelter of the lifer job can still augment economic realities enough to affect such a station in life.
If you find your way into a lifer job, and you grow old while working it, should the day ever arrive that your lifer job disappears in a puff of magic smoke, you might never find comparable employment again.
If your perimeter is poorly architected and you dont have logs from every single ingress/egress point and/or application within, or you arent forcing traffic through a proxy requiring authentication, its easy.
It's definitely not confined to the windows ecosystem. I develop C# on OSX via Jetbrain's Project Rider and run the developed code on anything from linux to docker instances.