This document will hold information for both protocols: MS-LSAD & MS-LSAT. MS-LSAT is issued alongside MS-LSAD and leverages the same interface UUID.
- Local Security Authority (Domain Policy) Remote Protocol (MS-LSAD)
- Local Security Authority (Translation Methods) Remote Protocol (MS-LSAT)
12345778-1234-ABCD-EF00-0123456789AB
lsarpc.dll
(loads into)lsass.exe
- ncacn_ip_tcp
- ncacn_np:
\PIPE\lsass
alias\pipe\lsarpc
-
Network:
- Network traffic over:
\pipe\lsarpc
or\pipe\lsass
- Destination port:
445
- Methods:
LsarOpenPolicy*
LsarLookupSid*
LsarQueryInformationPolicy*
LsarSetInformationPolicy*
LsarEnumerateTrustedDomains
LsarEnumeratePrivileges
LsarEnumeratePrivilegesAccount
LsarEnumerateAccounts
LsarEnumerateAccountRights
LsarEnumerateAccountsWithUserRight
LsarQueryDomainInformationPolicy*
- Network traffic over:
-
Host:
- Event ID 5145:
- Share Name:
\\*\IPC$
- Relative Target Name:
lsarpc
- Access Mask:
0x12019f
(Rights could be potentially less depending on the method called. Test was done via net.exe) - Object Type:
File
- Look at Source Address when investigating
- User account will not be a machine account ($)
- Share Name:
- Event ID 5145:
-
Potentially see a high volume of 5145's due to the number of enumeration requests
- RPC Filter Example:
rpc
filter
add rule layer=um actiontype=permit
add condition field=if_uuid matchtype=equal data=12345778-1234-ABCD-EF00-0123456789AB
add condition field=remote_user_token matchtype=equal data=D:(A;;CC;;;BA)
add filter
add rule layer=um actiontype=block
add condition field=if_uuid matchtype=equal data=12345778-1234-ABCD-EF00-0123456789AB
add filter
quit
- Filter forces the interface
12345778-1234-ABCD-EF00-0123456789AB
to only accept calls coming from a local admin on the host (BA in the SDDL string).
- Can be seen with enumeration activity.
- By default domain users can query this information via: dsacls.exe "cn=users,dc=marvel,dc=local"
- Created a RPC filter to only allow BA's (local admins) to perform this action, but note during testing it seemed that legitimate connections over these protocols were occurring. Unsure of the repercussions limiting the access to this protocol will cause. Could create a group that has BAs and Machine accounts, then apply that group SID to the filter.