Hybrid Identities
Find the Computer Running ADConnect
Find out where AD-Connect is running:
on the ad connect computer:
use the following from an admin-shell:
or the following from an non-admin shell:
Password Hash Sync (PHS)
- sync a hash of password-hash
- expiry date is not synced
- on-prem MSOL_ user: can dcsync AD
- azure:
sync_onprem_installationid
- can reset password of any azure user
- password for both are stored in plaintext on the on-prem sqlserver making that a high-value target
Enumerate
Abuse
on prem to cloud
- request AADGraph token
- with that we can reset any user password
- get cloud anchor
user_<objectid>
Pass-through-Authentication (PTA)
- usernames are synced, but authentication is forwarded to on-prem AD
- for enforcing on-prem password policies
- authentication agent on-prem
- shared secret between Azure AD and on-prem agent
on-prem to cloud
You can also install your own adsync agent and use it to authorize any authentication → skeleton key attack.
Federation
-
using the SAML2 protocol
-
all authentication occurs on-prem
-
can access cloud applications by using their on-prem credentials
-
ImmutableID is stored on-prem in ms-DS-consistencyGuid
-
if IdP is compromised we can create SAML certificate for any user → goldenSAML Attack
on the attacker-vm
back on the server:
Seamless SSO
- supported by PHS and PTA
- computer account
AZUREADSSOACC
in on-prem AD directory