Skip to content

Network & remote access

Network profiles (NetworkList)

NetworkList cheat sheet: network profiles, SSIDs, gateway MAC addresses, first and last connection times (local time), WLAN profile files and WLAN events.

Location
SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
Proves
Which networks (SSID, domain, gateway MAC) the host joined, first and last connection
Timestamps
DateCreated and DateLastConnected as 16-byte SYSTEMTIME in local time; profile key LastWrite as FILETIME, UTC; WLAN events UTC
Retention
Profiles persist until the network is forgotten or deleted; registry traces can outlive a forgotten Wi-Fi profile
Access
Administrator; SOFTWARE hive locked live: reg query works live, otherwise raw NTFS (KAPE) or VSS
Type
Registry
Windows
Vista / 78 / 8.11011
KAPE target
RegistryHivesSystemEventLogs
Velociraptor
Windows.Triage.Targets:RegistryHivesSystemEventLogs

What it is

Windows' Network Location Awareness service identifies each network the machine connects to and stores a profile for it in the SOFTWARE hive: name (SSID for Wi-Fi, domain or "Network" for wired), category (public, private, domain), gateway MAC address and connection dates. WLAN profiles are also stored as XML files. Together they place a laptop on a given network at a given time: home, hotel, café, a competitor's guest Wi-Fi, a mobile hotspot.

Location

ArtifactLocation
ProfilesSOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles\{profile GUID}
Signatures (link to gateway, DNS suffix)SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\Managed\<id> and \Unmanaged\<id>
Intranet cacheSOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Nla\Cache\Intranet
WLAN profilesC:\ProgramData\Microsoft\Wlansvc\Profiles\Interfaces\{interface GUID}\{profile GUID}.xml
WLAN eventsMicrosoft-Windows-WLAN-AutoConfig/Operational (for example 8001 connected, 8003 disconnected)

Present on Windows Vista and later.

What it proves

  • The host connected to a network with this name, and the first and last time it did.
  • Wi-Fi networks are identified by SSID; DefaultGatewayMac identifies the physical router, which can be geolocated through Wi-Fi databases or matched to a known site.
  • The profile GUID is the L2ProfileId referenced by SRUM, which gives bytes sent and received per app on that network.
  • It does not record every connection; use WLAN events and SRUM for the details in between.

Key fields

ValueWhereMeaning
ProfileName, DescriptionProfilesNetwork name (SSID or domain)
CategoryProfiles0 public, 1 private, 2 domain
NameTypeProfilesType of network (for example 0x47 wireless, 0x06 wired, 0x17 mobile broadband)
DateCreatedProfilesFirst connection
DateLastConnectedProfilesLast connection
ProfileGuidSignaturesLinks back to the profile
DefaultGatewayMacSignaturesMAC address of the gateway
DnsSuffix, FirstNetworkSignaturesDNS suffix, SSID

Timestamps

TimestampSet whenFormatPitfalls
DateCreatedFirst connection to the network16-byte SYSTEMTIME, local timeConvert with the time zone in effect at that date (UTC vs local time)
DateLastConnectedMost recent connectionSYSTEMTIME, local timeTravellers change time zones; check TimeZoneInformation and context
Profile key LastWriteProfile updatedFILETIME, UTCOften close to the last connection
WLAN event SystemTimeConnect / disconnectUTCLog may roll over

Retention and clearing

  • Profiles persist until the user "forgets" the network or an administrator deletes them; forgetting a Wi-Fi network removes the WLAN XML profile but registry traces can remain.
  • Deleted profile keys can be recovered from hive slack and shadow-copy SOFTWARE hives.

Collection

  • KAPE targets: RegistryHivesSystem (SOFTWARE hive) and EventLogs (WLAN-AutoConfig). No standard target collects the Wlansvc\Profiles XML files: copy them explicitly.
  • Velociraptor (Windows.Triage.Targets): RegistryHivesSystem, EventLogs; collect ProgramData\Microsoft\Wlansvc\Profiles separately, for example with Windows.Search.FileFinder.
  • Built-in:
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles" /s
netsh wlan show profiles
wevtutil qe Microsoft-Windows-WLAN-AutoConfig/Operational /q:"*[System[(EventID=8001)]]" /f:text /c:20

Parsing tools

  • Registry Explorer / RECmd (Eric Zimmerman): decodes SYSTEMTIME values and joins profiles to signatures.
  • RegRipper: networklist plugin.
  • WifiHistoryView (NirSoft): Wi-Fi connection history from the WLAN event log.

Investigation tips

  • Map L2ProfileId in SRUM to ProfileName to show that a large upload happened while the laptop was on a personal hotspot, not the corporate network.
  • Hotel, airport and coffee-shop SSIDs help confirm travel and the time zone to apply to local-time artifacts.
  • A new profile created shortly before an incident (a phone hotspot, an unknown SSID) can explain how data left without crossing the corporate proxy.
  • Use DefaultGatewayMac to distinguish two networks with the same generic SSID.

Related artifacts

Glossary terms

Guides

All artifacts on one page: cheat sheet