Fileless malware commonly leverages PowerShell to execute in memory without dropping files to disk. Detailed PowerShell activity — including script block contents and module execution — is recorded in the Microsoft-Windows-PowerShell/Operational log, but this level of logging (script block logging and module logging) is disabled by default and must be explicitly enabled through Group Policy or registry configuration. Once enabled, the SIEM can ingest these events (such as Event ID 4104) to detect fileless malware execution. The other listed logs are enabled by default and track unrelated system activities: DPAPI operational logs track data protection API cryptographic operations, UserPnp/DeviceInstall logs track plug-and-play device installation, and TerminalServices-LocalSessionManager logs track remote desktop session connects/disconnects — none of which pertain to capturing fileless malware execution.
Community Discussion