Active Directory Hardening Series
Part 1 Disabling NTLMv1 https://t.co/9gla1vtQ18
Part 2 Removing SMBv1 https://t.co/KOqpamarcW
Part 3 Enforcing LDAP Signing https://t.co/oW2Ymvu1ZW
Part 4 Enforcing AES for Kerberos https://t.co/iENjEPBOFD
📅 Save the Date: SysAdminDay Leipzig 2026
🗓 31.07.2026
🕒 ab 12:00 (Einlass 11:30)
IT, Community & Austausch – seid dabei!
👉 https://t.co/4d9xkIwf4Z
#SysAdminDay#SADLPZ
You used to get a sticker with a serial for Windows on new hardware, these days it's digital and you have an embedded key stored in EUFI.
To extract your Windows 11 product key on Linux:
sudo strings /sys/firmware/acpi/tables/MSDM | grep -E '[A-Z0-9]{5}(-[A-Z0-9]{5}){4}'
Kali just published a guide on piping pentesting tools through Claude's API and didn't mention data security once. You're sending scan results, target info, and potentially sensitive findings to a third party LLM. "The Most Advanced Penetration Testing Distribution" should probably mention that.
https://t.co/HBLYd09cjz
📢 Major updates for Microsoft partners
"Beginning February 13, 2026, the following benefits are no longer accessed through the Visual Studio Enterprise subscription experience:
- Monthly Azure credits
- On-premises software downloads and product keys (such as Windows, Office, and server products)
- Legacy developer tools that are no longer aligned with modern development workflows
How to access these benefits going forward
Azure credits and software for development and testing continue to be included as part of the benefits package you hold. Going forward, we recommend accessing:
- Azure credits through your existing Azure subscription or partner benefits
- Software and licensing through the appropriate licensing or partner entitlement programs associated with your purchase”
I'm not sure I understand, but it seems Microsoft Partners will only receive:
- Azure credits at the tenant level
- Only keys for production use, meaning Microsoft Partners have lost everything for lab environments.
How does Microsoft expect partners to stay up to date?
And most importantly, making this change after a price increase in 2025 seems... questionable.
🔎 𝗙𝗿𝗼𝗺 𝘁𝗵𝗲 𝗙𝗶𝗲𝗹𝗱 — Real-World Findings from Security Assessments
💥 𝟰𝟮.𝟵% of infrastructures I’ve assessed 𝗿𝘂𝗻𝘀 𝗺𝘂𝗹𝘁𝗶𝗽𝗹𝗲 𝗿𝗼𝗹𝗲𝘀/𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 𝗼𝗻 𝘁𝗵𝗲𝗶𝗿 𝗱𝗼𝗺𝗮𝗶𝗻 𝗰𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗲𝗿𝘀
🚫 𝗧𝗵𝗶𝘀 𝗶𝘀 𝗳𝗮𝗿 𝘁𝗼𝗼 𝗰𝗼𝗺𝗺𝗼𝗻 — especially in smaller environments — but it’s one of the fastest ways to weaken your security posture. Domain Controllers should normally host only two services:
✅ Active Directory Domain Services
✅ DNS
Nothing more.
𝗪𝗵𝘆?
Because every extra service:
▪️ adds ports
▪️ increases the attack surface
▪️ introduces more vulnerabilities
And it turns your DC into a much larger target than it already is (☢️). If you’ve ever had to configure firewall openings for domain controllers, you know the list is already long enough. If not, here’s a reference:
▪️ https://t.co/DM11qW1in7
✅ 𝗕𝗼𝗻𝘂𝘀 𝘁𝗶𝗽: You can restrict many AD-related RPC services from the dynamic port range (yes — network admins will thank you). Microsoft provides guidance here:
▪️ https://t.co/jsVKHW72vJ
▪️ https://t.co/fcvYX1yBwL
𝗔𝗻𝗼𝘁𝗵𝗲𝗿 𝘃𝗲𝗿𝘆 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗿𝗲𝗮𝘀𝗼𝗻 to do so — Tiering Model. Have you ever tried to configure Tiering Model when you are hosting multiple services/roles on just few machines? 𝗧𝗵𝗮𝘁 𝗶𝘀 𝗮 𝗿𝗲𝗮𝗹 𝗽𝗶𝗰𝗸𝗹𝗲...
#ADDS #DomainController #CyberSecurity #Infrastructure #Hardening #BlueTeam #HorizonSecured #FromTheField @BlueTeamDave
Credential Guard was supposed to end credential dumping. It didn't.
@bytewreck just dropped a new blog post detailing techniques for extracting credentials on fully patched Windows 11 & Server 2025 with modern protections enabled.
Read for more ⤵️ https://t.co/mYPHg1mTKj
There appears to be some confusion about the historical and legal foundations of the relationship between the United States, Denmark, and Greenland.
A brief clarification of the relevant facts may therefore be useful.
Greenland was first settled by Norsemen in AD 985, when settlers from present-day Iceland - then part of the Norwegian cultural sphere - established communities in southern Greenland. At the time of their arrival, the areas in which they settled were uninhabited. It is therefore historically inaccurate to describe this settlement as “colonization” in the modern sense of the term.
During the Middle Ages, Greenland followed Norway into the personal union with Denmark in 1380. When Denmark and Norway separated in 1814 under the Treaty of Kiel, Greenland remained under Danish sovereignty.
The Norse settlements disappeared in the early fifteenth century. Danish presence in Greenland was re-established in 1721, initiating a continuous Danish administration that has lasted ever since.
The United States formally and unequivocally recognized Danish sovereignty over Greenland in 1917, in connection with Denmark’s sale of the Danish West Indies to the United States. As part of that agreement, the United States explicitly acknowledged Denmark’s full sovereignty over Greenland. This recognition has never been revoked, qualified, or legally contested.
During the Second World War, Denmark and the United States entered into close and pragmatic cooperation regarding Greenland’s defense. Following the German occupation of Denmark in 1940, the United States established a series of military installations in Greenland - the so-called Bluie bases - with Danish consent. This cooperation laid the foundation for the enduring strategic partnership between Denmark and the United States in the Arctic.
That partnership was formalized in the 1951 Defense Agreement, which grants the United States exceptionally broad rights to operate military installations in Greenland. Few allied countries have ever extended such latitude to a partner power. The agreement reflects a high degree of Danish trust and a shared understanding of Greenland’s strategic importance.
Certain adjustments were introduced with the Igaliku Agreement of 2004, which clarified consultation mechanisms and the role of Greenland’s Home Rule authorities. These modifications, however, did not fundamentally alter the wide operational freedom granted to the United States under the 1951 framework.
In short, there is no historical, legal, or strategic rationale for reverting to nineteenth-century concepts of unilateral territorial revision or for questioning the international legal status of territories belonging to allied states.
Such ideas are incompatible with both international law and the long-standing partnership between Denmark and the United States.
Last quarter I announced a milestone.
30% of our code is now written by AI.
I called it "engineering velocity."
The board loved that phrase.
They didn't ask what the code does.
Neither did we.
It compiles. Usually.
That's the metric.
Someone asked about testing.
I said "AI-assisted quality assurance."
That means the AI writes the tests too.
For the code it wrote.
It finds no issues.
Very efficient.
This week we admitted Windows 11 core features are broken.
Audio doesn't work.
Explorer crashes.
Updates fail to install.
Users asked why.
I said "we're investigating."
Investigating means reading the code.
The code the AI wrote.
That no human understands.
Because understanding isn't scalable.
Our CTO says 95% of code will be AI-generated by 2030.
I believe him.
I have to.
We fired the people who would check.
They were "non-essential headcount."
Essential means writes code.
AI writes code.
Humans are overhead.
Overhead gets optimized.
We optimized 10,000 engineers last year.
This year the bugs arrived.
Unrelated, obviously.
The engineers we kept are debugging AI output.
They don't understand it either.
But they're "cross-functional."
Cross-functional means they do everything.
Everything means nothing well.
A user asked why their audio disappeared after an update.
I said "install updated drivers."
They asked why the update broke the drivers.
I said "report it via Feedback Hub."
They asked what happens to feedback.
I said "it helps us prioritize."
Prioritize means add to backlog.
Backlog means never.
But politely.
Someone on Hacker News called this "a privacy and consent disaster."
I called it "an evolving user experience."
Same thing. Different framing.
We released a fix.
The fix broke something else.
The something else was also written by AI.
The fix was also written by AI.
They're collaborating now.
I call it "autonomous iteration."
The autonomous iteration has created 47 new bugs.
Each bug spawns a fix.
Each fix spawns two bugs.
Exponential growth.
Just like our stock price.
Unrelated, obviously.
Satya told Mark we're at 30%.
Mark said he didn't know Meta's number.
Sundar said Google is also at 30%.
None of us know what the code does.
But we know the percentage.
Percentage is a metric.
Metrics go in earnings calls.
Earnings calls move stock prices.
Stock prices determine bonuses.
Bonuses determine success.
Success means the bugs don't matter.
Users asked when Windows will work again.
I said "we're committed to quality."
Quality means it ships.
Ships means it's your problem now.
Thank you for being part of the Microsoft family.
Family means you can't leave.
We're in your enterprise agreement.
For three more years.
The circle of innovation.
After Months of Development, FINALLY ready to share: Harden System Security🎉
✅ Complete System Hardening
✅ Security Posture Analysis
✅ All-in-One Toolkit
✅ Built-in Intune support for Scalability
✅ Beautiful Modern UI
✅ CLI support
https://t.co/lfd3SaDvvM
#Cyber#Windows
CMTrace.exe requires a SCCM license, so if you`re unlicensed you should use LogExpert instead to analyze @MSIntune logs. Heck, you can even use the free version of @MasterPackager to create a MSI.
https://t.co/i3OtSBqQZ9
I am not sure I would do this in my AD. I would prefer to secure, make them visible and not obscure that can bite me or others 5-10 years later. I have couple of Domains that did similar obscurities and now nobody knows whats where.
Do:
1. Design proper Tiering model
2. Stick to it
Dont:
1. Obscure stuff like this
No disrespect to Linus Torvalds, but this guy is the greatest geek alive 🫡
Created UNIX in 1971 when he was 28 years old.
Created Go in 2009 when he was 66 years old.
He also developed the B programming language (which led to C), created UTF-8 encoding (making international text possible online), and designed essential tools like grep that developers still rely on daily.
He also helped with the development of Multics (that led to UNIX), Plan 9 from Bell Labs and Inferno operating systems.
That's 4 operating systems in total... Most people don't even use these many OS.
Pretty impressive resume, right?
And it's a shame that many people, even the ones in the IT and tech industry, don't know him.
Ken Thompson.... Remember the name 🙏
Again, most of these issues are easily identified using ADeleginator or ADeleg. Highly recommend checking these two tools out.
ADeleginator - https://t.co/FgdvN8lS1D
ADeleg - https://t.co/LCBYlpfzpD