XQL query for hunting MS-DFSNM

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

XQL query for hunting MS-DFSNM

L4 Transporter

Hello dear community, 


has anyone of you a XQL Query for this type of attack?








L3 Networker

Hi @RFeyertag!


Thank you for submitting the coverage request regarding DFSCoerce.


At this time, our security engineers are working diligently to provide protection and coverage against the DFSCoerce NTLM Relay Attack for the Cortex XDR agent and Cortex XDR server. If you would like to receive direct notifications when advances in this coverage have been deployed or want a more immediate option for inquiries on future attack coverage, we highly recommend contacting our TAC team at https://support.paloaltonetworks.com/. We can update you on the availability of Cortex XDR coverage in the LiveCommunity when it is available, however, that would be best effort and may involve some delay.

L3 Networker

Hi @RFeyertag


With the release of Content Update 590-96665, a new XQL query has been provided for the DFSCoerce attack:


dataset  = xdr_data 

| alter day = extract_time(_time, "DAY"), dfs_relay_server = json_extract_scalar(action_rpc_func_str_call_fields,"$.ServerName"), 

 dfs_root_share = json_extract_scalar(action_rpc_func_str_call_fields,"$.RootShare")

| filter event_type = 22 and action_rpc_interface_uuid = "{4FC742E0-4A10-11CF-8273-00AA004AE673}" and action_rpc_func_name  = "NetrDfsRemoveStdRoot" and action_rpc_func_opnum in (12, 13)

| fields actor_remote_ip, agent_hostname, agent_id, action_rpc_func_opnum, action_rpc_func_str_call_fields, action_rpc_func_name, actor_type, day, dfs_relay_server, dfs_root_share

| comp count_distinct(day) as day_count_dfrpc_src_dst_func by actor_type, action_rpc_func_name, action_rpc_func_opnum, agent_hostname, agent_id, actor_remote_ip, dfs_relay_server, dfs_root_share

| filter day_count_dfrpc_src_dst_func < 7


Since the RPC functionality can be normal... this may require further tuning for your environment.


The client can see the remote actor under actor_remote_ip , the affected server under agent_id or agent_hostname , and the possible relay server extracted under dfs_relay_server in addition to other fields there that might help triage.


This is not guaranteed to be the attack, but will most likely show an unusual usage of DFS which can indicate a possible attack.

  • 2 replies
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!