DFIRHub

Windows event log ยท System56 TermDD

Remember you will need to decode the binary (the documentation above explains it) to actually figure out WHAT it was trying to do.

  • System
  • 1 field
  • System.evtx
  • TermDD

Notes

  • Remember you will need to decode the binary (the documentation above explains it) to actually figure out WHAT it was trying to do.
  • However, these are basically "frozen" RDP connections.

Fields EvtxECmd extracts

1 column in the EvtxECmd CSV

  • PayloadData1Data: %Data%
    • %Data% = /Event/EventData/Data

Sample event

Event XML from the map file

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="TermDD"/>
    <EventID Qualifiers="49162">56</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-06-01T12:13:20.176180300Z"/>
    <EventRecordID>163487</EventRecordID>
    <Channel>System</Channel>
    <Computer></Computer>
    <Security/>
  </System>
  <EventData>
    <Data>\Device\Termdd</Data>
    <Data>IP ADDRESS</Data>
    <Binary>STATUS CODE IN BINARY</Binary>
  </EventData>
</Event>

References

1 link

Source: evtx/Maps/System_TermDD_56.map(opens in new tab) by Tony Knutson and contributors(opens in new tab), MIT License(opens in new tab)