Clément Notin
@cnotin.bsky.social
🤔 We have answers to your questions on #BadSuccessor, the latest AD vulnerability www.tenable.com/blog/frequen...
🕵️ Tenable Identity Exposure customers can check their exposure with our recently released Indicator of Exposure (IoE): www.tenable.com/indicators/i...
🕵️ Tenable Identity Exposure customers can check their exposure with our recently released Indicator of Exposure (IoE): www.tenable.com/indicators/i...
Frequently Asked Questions About BadSuccessor
Frequently asked questions about “BadSuccessor,” a zero-day privilege escalation vulnerability in Active Directory domains with at least one Windows Server 2025 domain controller.
www.tenable.com
June 2, 2025 at 6:54 PM
🤔 We have answers to your questions on #BadSuccessor, the latest AD vulnerability www.tenable.com/blog/frequen...
🕵️ Tenable Identity Exposure customers can check their exposure with our recently released Indicator of Exposure (IoE): www.tenable.com/indicators/i...
🕵️ Tenable Identity Exposure customers can check their exposure with our recently released Indicator of Exposure (IoE): www.tenable.com/indicators/i...
Microsoft hardened the Entra ID synchronization feature last year:
- restricted permissions on Directory Synchronization Accounts role
- new dedicated sync app
Let’s find out how sync still works 🔍
Some old tricks persist—and new ones have emerged 💥
tenable.com/blog/despite... 🧵
- restricted permissions on Directory Synchronization Accounts role
- new dedicated sync app
Let’s find out how sync still works 🔍
Some old tricks persist—and new ones have emerged 💥
tenable.com/blog/despite... 🧵
Despite Recent Security Hardening, Entra ID Synchronization Feature Remains Open for Abuse
Microsoft synchronization capabilities for managing identities in hybrid environments are not without their risks. In this blog, Tenable Research explores how potential weaknesses in these synchroniza...
tenable.com
April 24, 2025 at 1:39 PM
Microsoft hardened the Entra ID synchronization feature last year:
- restricted permissions on Directory Synchronization Accounts role
- new dedicated sync app
Let’s find out how sync still works 🔍
Some old tricks persist—and new ones have emerged 💥
tenable.com/blog/despite... 🧵
- restricted permissions on Directory Synchronization Accounts role
- new dedicated sync app
Let’s find out how sync still works 🔍
Some old tricks persist—and new ones have emerged 💥
tenable.com/blog/despite... 🧵
🎥 Here's the recording of last week's webinar where I shared how to protect Entra ID from real-world attacks 🏴☠️, beginning with federation backdoors/privesc, using Tenable Identity Exposure
March 24, 2025 at 2:13 PM
🎥 Here's the recording of last week's webinar where I shared how to protect Entra ID from real-world attacks 🏴☠️, beginning with federation backdoors/privesc, using Tenable Identity Exposure
You know how some system AD attributes cannot be edited even when Domain Admin?
"Error 0x20B1 The attribute cannot be modified because it is owned by the system."
This can be bypassed using the schemaUpgradeInProgress modify operation learn.microsoft.com/en-us/opensp... 😉⬇️
"Error 0x20B1 The attribute cannot be modified because it is owned by the system."
This can be bypassed using the schemaUpgradeInProgress modify operation learn.microsoft.com/en-us/opensp... 😉⬇️
[MS-ADTS]: schemaUpgradeInProgress
This operation causes the fschemaUpgradeInProgress field of LDAPConnection instances in dc.LDAPConnections ([MS-DRSR]
learn.microsoft.com
December 23, 2024 at 10:32 AM
You know how some system AD attributes cannot be edited even when Domain Admin?
"Error 0x20B1 The attribute cannot be modified because it is owned by the system."
This can be bypassed using the schemaUpgradeInProgress modify operation learn.microsoft.com/en-us/opensp... 😉⬇️
"Error 0x20B1 The attribute cannot be modified because it is owned by the system."
This can be bypassed using the schemaUpgradeInProgress modify operation learn.microsoft.com/en-us/opensp... 😉⬇️