🖥️
Windows DFIR
  • Introduction
  • Windows Artifacts
    • Windows Quick Tips
      • Windows Command Line
      • Workstation File/Folder Locations
      • Server File/Folder Locations
    • Account Usage
      • Authentications SAM Artifacts
        • Last Login
        • Last Failed Login
        • Last Password Change
      • Authentications (Windows Event Log)
        • Logon ID
      • Group Membership
        • Event ID: 4798
        • Event ID: 4799
      • RDP
        • Source System Artifacts - Quick Reference
        • Destination System Artifacts - Quick Reference
      • SSH
      • Rouge Local Accounts
      • CrowdStrike Searches
        • Event Name - UserLogon
        • Event Name - UserLogonFailed
        • Event Name - UserLogonFailed2
        • Event Name - SsoApplicationAccess
    • Browser Usage
      • History & Downloads
        • Viewing History Files - DB Browser
        • Transition Types
      • Auto-Complete Data
      • Bookmarks
      • Browser Preferences
      • Cache
      • Cookies
      • Extensions
      • Super Cookies (HTML5 Web Storage)
      • Media History
      • Private Browsing
      • Session Restore
      • Stored Credentials
      • Suggested/Frequent Sites
      • DB Browser Queries
        • Firefox
        • Chrome
        • Media History
      • PowerShell Scripts
        • Browser Extension Finder
        • Browser History Finder
    • Processes
      • at.exe
      • explorer.exe
      • lsass.exe
      • lsaiso.exe
      • PuTTy.exe
        • X11 Forwarding
      • runtimebroker.exe
      • services.exe
      • smss.exe
      • System
      • svchost.exe
        • Services
      • winlogon.exe
      • wininit.exe
    • Cloud Storage
    • Deleted File or File Knowledge
      • WordWheelQuery (Win 7+)
      • ACMRU (Win XP)
      • Internet Explorer file:///
      • Last Visited MRU
      • Thumbs.db (Win XP)
      • Thumbcache
      • Recycle Bin
      • User Typed Paths
      • Windows Search Database
    • File Download
      • Zone.Identifer
      • Open/Save Most Recently Used (MRU)
      • Email
      • Drive By Downloads
        • Malvertising
      • Web Browsing
        • Cache Files
      • CrowdStrike Searches
        • MoTW
    • Folder/File Opening/Creation
      • Recent Files
      • Office Recent Files
      • Shell Bags
      • .lnk Files
      • Jump Lists
        • AppIDs
      • Prefetch
      • Index.dat file://
      • PowerShell Scripts
        • .lnk Files
    • Persistence
      • Registry
        • NTUSER.DAT & HKU\SID
        • Run and Run Once
        • Shell Folders and UserInit Key
        • Services
        • Logon Scripts
        • Office Add-ins
        • Winlogon Shell
        • Image File Execution Options (IFEO)
        • AppInit_DLLs
        • Scheduled Tasks
      • Scheduled Tasks
        • Scheduled Task Destination System Artifacts
        • Scheduled Task Source System Artifacts
      • Startup
      • Tool: AutoRuns
      • Accounts
      • WMI Event Consumers
        • WMI: Source System Artifacts
        • WMI: Destination System Artifacts
        • WMI: PowerShell Analysis
      • PowerShell Scripts
        • Startup Programs
      • CrowdStrike Searches
        • Files Written to Startup Folder
        • Files Written to Startup Folder from the Internet
        • Local Account Creation/Deletion
        • Azure Account Creation/Deletion
        • Scheduled Tasks
    • Physical Location
      • Time zone
      • Wireless SSID
      • Network History (Vista/Win7–11)
      • Cookies
      • Browser Search Terms
    • Program Execution
      • Prefetch
        • Decoding Prefetch Files with Eric Zimmerman's PECmd Tool
      • BAM/DAM
      • CapabilityAccessManager
      • UserAssist
      • Last Visited MRU
      • RunMRU
      • MUI Cache
      • ShimCache
      • Amcache
      • Jump Lists
    • Shadow Copies
      • VSC Permissions
      • Event ID 8193: Volume Shadow Copy Service Error
    • USB Usage
      • Key Identification
      • Drive Letter and Volume Name
      • Connection Timestamps
      • User
      • Volume Name
      • Plug & Play Event Log
    • Windows Services
      • DoSvc (Delivery Optimization)
    • System Information
    • Event IDs
      • Authentication / Account
        • 4624 - Authentication Success
          • Logon Types
        • 4625 - Authentication Failure
          • SubStatus Codes
        • 4634 - Account Logoff
        • 4648 - Explicit Credentials Success
        • 4672 - Special Privileges
        • 4720 - Account Creation
        • 4722 - Account Enabled
        • 4732 - Addition to Local Group
        • 4738 - Account Changed
        • 4776 - Kerberos Authentication Attempt
          • Substatus Codes
        • 4771 - Kerberos Failure
        • 4768
      • File System
        • 1006
        • 4688 - Process Created
        • 4663
        • 4656
        • 6416
        • 20001
        • 20003
  • Windows DFIR & MITTR
    • Initial Access
      • Content Injection
      • Drive-by Compromise
        • Watering Hole Attack
        • Microsoft Files (Payload Execution)
        • Exploit Delivery
        • Viewing Browser History Files
      • Phishing
    • Execution
    • Persistence
    • Privilege Escalation
    • Defense Evasion
    • Credential Access
      • Logon ID
    • Discovery
    • Lateral Movement
    • Collection
    • Command and Control
    • Exfiltration
    • Impact
  • SOC Related
    • Cached Credentials
    • Domain Controller Password Spraying
Powered by GitBook
On this page
  • How to Find the Time Zone on a Windows Host
  • 1. Via the Registry
  • 2. Via Command Line
  • 3. Via PowerShell
  • 4. Via Control Panel
  • Why Time Zone Information Matters in Analysis

Was this helpful?

  1. Windows Artifacts
  2. Physical Location

Time zone

Understanding and accurately interpreting the system time zone on a Windows host is pivotal for forensic analysts, system administrators, and security professionals. The system time zone determines how time stamps are represented in logs, files, and other system artifacts. Discrepancies in time zone settings across different systems can complicate the correlation of events in a multi-device environment, making it crucial to establish the correct time context when conducting analysis.

How to Find the Time Zone on a Windows Host

1. Via the Registry

The Windows Registry holds the current system time zone information within the SYSTEM hive. The specific path is:

SYSTEM\CurrentControlSet\Control\TimeZoneInformation

You can access this information using the Registry Editor (regedit.exe) or via command line tools like reg query. For example:

reg query "HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation"

This command will display various values, including:

  • TimeZoneKeyName: The name of the current time zone.

  • DynamicDaylightTimeDisabled: Indicates whether daylight saving is considered.

  • Other values related to specific daylight saving time adjustments.

2. Via Command Line

You can also determine the system's time zone by executing the following command in Command Prompt or PowerShell:

tzutil /g

This command uses the Time Zone Utility (tzutil.exe) to get (/g) the current time zone ID.

3. Via PowerShell

PowerShell offers a more detailed view through the Get-TimeZone cmdlet, available in Windows 10 and newer versions:

Get-TimeZone

This will return the Id, DisplayName, StandardName, DaylightName, and whether the system is currently on daylight saving time.

4. Via Control Panel

For a GUI approach, navigating to Control Panel > Clock and Region > Date and Time and then to the Time Zone tab will display the current system time zone setting.

Why Time Zone Information Matters in Analysis

  • Event Correlation: When analyzing logs from multiple sources (e.g., network devices, servers, and workstations), time zone differences can lead to misinterpretation of the sequence of events. Accurate time zone information ensures that events are correctly correlated across all devices.

  • Forensic Accuracy: The interpretation of file timestamps, log entries, and other time-sensitive data is contingent upon understanding the system's time zone settings. This is especially critical in forensic investigations where the timing of events can indicate malicious activity or user actions.

  • Legal and Compliance Implications: In legal scenarios, the precise timing of events can be critical. Misalignment in time zone settings might lead to incorrect conclusions, affecting the outcome of legal proceedings or compliance audits.

  • Security Monitoring: For real-time security monitoring, knowing the time zone is essential for alerting and response activities. It ensures that security personnel can respond to incidents in a timely manner based on the local time of the affected systems.

PreviousPhysical LocationNextWireless SSID

Last updated 1 year ago

Was this helpful?