SwiftOnSecurity Profile picture
Mar 24, 2024 19 tweets 4 min read Read on X
Rather than go into OrgKit tonight, I want to explain why Windows networks have been historically insecure. 🧵
Computing does not have a long history. Its progression goes industrial IBM solutions with all services included, to piecemeal solutions separating software and hardware, to innumerable OS options and hardware, to standardized hardware and narrowing OS options, to 90’s businesses
As these options narrowed, Windows offered a solution in NT Domains with a compelling, if junior way, to solve the hardest problem in computing: Interoperability and per-user security across server and client. There were others we won’t get into them. It was a huge success.
There is a large history of disparate and converged services in computing. Microsoft eventually combined many academic/corporate solutions into a cohesive offering: Active Directory.
Kerberos for authentication. LDAP for directory. SMB for file services. Group Policy for mgmt etc
The problem here was Microsoft created a monstrously powerful solution, with essentially a blank-slate administrative paradigm you had to design and deploy (they didn’t know what was the right way either yet and didn’t want to prematurely designate), and gave it away for free.
Directory solutions and admin delegation of rights had previously been entire jobs that committees debated and defined and slowly developed tools for.
Active Directory had that, in an almost infinitely adaptable way, for people with no experience or knowledge. It just worked.
Microsoft had tribulations in its management and investment in Active Directory. Some of which I know, most I don’t.
But they had unleashed the greatest networking tool ever for making computers be talking together and be managed. Effortlessly. And, they were mostly all isolated.
Some things, I blame Microsoft. Others I say what they were doing had literally never existed at scale. And without hindsight. Others, were a failure to renew an ownership in results.
Anyway. The years go on. The Internet is omnipresent. And the attacks start against customers.
Microsoft begins to have a Very Bad Time. A combination of code security issues leading to worms, and executable control+privilege level on arbitrary code – leading to users compromising themselves by installing innocuous-seeming malware – becomes crisis. Guess what. They respond
In 2002, Bill Gates releases one of the most consequential pieces of corporate writing in history. The “Trusted Computing Memo.”

This dramatically led to changes making exploiting Microsoft products substantially harder. It led to internal revolution.
But.wired.com/2002/01/bill-g…
What Microsoft could not do was fix the networks their customers had already built. Further, they failed to radically transform the administrative surface of Active Directory and its default state, to make it administratable by commoners.
This is one of their greatest failures.
Active Directory remains without reasonable roles for segregation or responsibility. Like, “desktop administrator” or “server adninistrator” or “network service querying logged-in user.” They just don’t exist. And most customers do not have the specialization and skill to do it.
Neither do OU (folders) exist to correctly delineate these objects into their roles and ability to access. Or organizationally delegate.
So what do Microsoft customers do? They exploit the worst decision in the history of computer. That I feel bad highlighting.

“Domain Admins”
Because Microsoft abdicated its role in strongly defining an administrative theory for Active Directory - which all products today have - their customers have rights to everything assigned to innumerable people. Sane account they access their email can ransom the entire company.
Now; there are firms that nominally try to do it right. Where Helpdesk are not Domain Admins. But innumerable network services with hijackabke credentials are. And the helpdesk people are admins to Domain Admins. So they own the domain admins. AD offers nothing to detect/address.
This is just a sample of 2 issues that fostered our reality. Microsoft is now investing again into AD. With a product leader I’d like to call a friendly acquaintance.
But where was the money before. Where was the leadership that obligated the resources. When they made our world.
Lucky for Microsoft it kinda seems like Twitter broke this thread somewhere so you won’t see it. But yeah. I’m called a Microsoft shill because my criticisms don’t fit in a funny anecdote about the Start Menu.
If anyone knows a similar write up or course that explains the actual motivating issues into WHY our networks are like this @ me a link so I don’t have to write it and then never do it.
(The AD team has been working on great stuff, public, announced, and stuff I’ve heard. This is NOT a criticism of them. I’m trying to describe the history of how we got to today. Which they may disagree with. But I don’t pass stuff by Microsoft. I’m actually independent.)

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with SwiftOnSecurity

SwiftOnSecurity Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @SwiftOnSecurity

Feb 18
The thing about Active Directory, is you can't understand any of it unless you begin from the past before it. You cannot examine it from the future. You will get only nonsensicals.
And that's really where most commentators fail. They don't know why. Because there is a reason.
The reasons Active Directory fails is deeper than technology. It is from inception, to ironically be more open than you conceive. It is the sourcing of philosophy in staff whose only job was one portion. Whose users, absolute experts. Whose salary paid one. This... didn't happen.
Active Directory is truly beautiful. But it's a beauty you can only experience in the world it was envisioned for. Outside, it is a horror of hacks trying to address things you can only ascribe hate. Decades later. But trust me, it is beautiful. I wish you could see it, how I do.
Read 9 tweets
Feb 15
I live on a secluded area of my street with little traffic but I purposefully make it evident my surveillance and you know what every dog walker picks up their poop. Image
👏Always👏be👏engineering👏perception👏

Even on gate I don't lock I have a fake one that makes it appear always padlocked. I have spike strips that are just plastic on areas you could boost over my fence.
I do the same thing in enterprise security. We appear to have three different top-tier antivirus, running on a malware analysis VM, with debug tools running, and more traces like that.

This is your playground they're in and stop denying yourself the freedom to fake it.
Read 9 tweets
Feb 12
One of most interesting artifacts of Windows was in Vista when they laid out their most optimistic dreams of how what they would be built would be used. A real tragedy, writing how they hoped troubleshooting framework would be adopted in proactive remediation. It was just killed. Image
Windows has only had a few true revolutions. 95, NT, 2000 Server (Active Directory), XP, Vista, and 8.
Windows 7, Windows 10, they are the inheritors of surviving the revolution. They are the good times. Unfortunately I don't know what Windows 11 is.
What the common person doesn't understand is that Windows is the only OS on Earth that does what it does. The support matrix for Windows 10 is the most profound and mathematically extreme in human history.
Windows 11 was a hard-cut. A cruel one. One you'd never understand why.
Read 8 tweets
Jan 11
==Training Lesson==
INVESTIGATION NARRATIVE: SSH Kill la Killed 🧵

My job is to solve the Weird Problems as the Final escalation tier. I do this with generalist knowledge and practical experience.

New InfoSec/IT entrants often ask what this looks like in practice. Follow below. Image
NOTE: You can mute this thread if not interested it will be long.

I have a seedbox in Europe to coalesse torrent downloads from other servers at 10gbe uplink to many other similar colocated servers hosting the content. I then collect finished over SSH file copy at my leisure.
In some scenarios you can increase overall transfer speeds by running multiple sessions simultaneously, like a multi-lane highway. This can help saturate your connection, which I was not getting.

I go into WinSCP and turn this on, 6 sounds good. Image
Read 21 tweets
Jan 5
In 2009, I got on a helicopter piloted by my friend. We lifted off with careless abandon, in the online mode of Grand Theft Auto 4, for the first time. We were normally talkative, but we both fell into wordlessness as we flew at night through this impossible city. And I realized.
Every story can be told here. Labor of untold people who toiled to Truman Show you made a city we flew by with only glance. On the streets, raced-by. There are innumerable conceits, things started and never finished. Left over from dreams aborted. But someone made this. For what?
A city never runs out of stories. A city is not reorganized for every allegorical plunder. The artists who strained for years to make this analogy have their effort thrown away on conclusion of an arc written by another or abandoned by player. But they made a city. For what?
Read 6 tweets
Dec 7, 2024
So my outsider impression is all cloud AI services have essentially nuked themselves in endless layers of safety and political conformance, while also desperately trying to save on compute. If you've watched o1 work it has layers of reasoning for "safety" before it answers.
And that cloud AI is essentially in a death spiral of mainstreaming concerns instead of delivering. Yes you've created a corpus of the sins of humanity and you're not remotely brave enough to just be a fucking adult about what your API returns.
The Google AI disaster is just the essential denial of how this technology works. It literally delivers the average signal. The proctologist is going to be an old white guy. That's the average. And you've taken it on yourself to deny this technology you built to say exactly that.
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(