Collect Microsoft PowerShell logs

Supported in:

Google secops SIEM

This document explains how to ingest Microsoft PowerShell logs to Google Security Operations using the Bindplane agent.

Microsoft PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and scripting language. PowerShell logs capture script execution, module activity, and command invocations, providing visibility into PowerShell operations for security monitoring and forensic analysis.

Before you begin

Make sure you have the following prerequisites:

Google SecOps instance
Windows Server 2016 or later
Network connectivity between the Windows host and Google SecOps
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Administrative access to the Windows host to configure PowerShell logging and install the Bindplane agent

Configure PowerShell logging

PowerShell logging must be enabled on Windows hosts before logs can be collected. By default, PowerShell logging is minimal. Enable Script Block Logging to capture detailed PowerShell activity.

Enable Script Block Logging using group policy

Open the Local Group Policy Editorby running gpedit.msc as an administrator.
Go to Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell.
Double-click Turn on PowerShell Script Block Logging.
Select Enabled.
Optionally, check Log script block invocation start / stop eventsto capture start and stop events for each script block. Note that this option generates a high volume of logs.
Click OK.
Open Command Promptas an administrator and run gpupdate /force to apply the policy immediately.

Enable Script Block Logging using the registry

Alternatively, you can enable Script Block Logging by setting the following registry value:

Open the Registry Editorby running regedit as an administrator.
Navigate to HKLM\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging .
If the key does not exist, create it.
Create a new DWORD (32-bit) Valuenamed EnableScriptBlockLogging and set its value to 1 .
Restart PowerShell sessions for the change to take effect.

PowerShell Script Block Logging writes events to the Microsoft-Windows-PowerShell/Operationalevent log channel with Event ID 4104.

Optional: Enable module logging

Module Logging records pipeline execution details for specified modules. To enable Module Logging for all modules, do the following:

In the Local Group Policy Editor, go to Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell.
Double-click Turn on Module Logging.
Select Enabled.
Click Shownext to Module Names.
Enter * to log all modules.
Click OKin the Module Nameswindow.
Click OKin the Module Loggingwindow.
Run gpupdate /force to apply the policy.

Module Logging events are written to the Windows PowerShellevent log with Event ID 4103.

Optional: Enable transcription

Transcription creates a text-based record of all PowerShell session input and output. To enable Transcription, do the following:

In the Local Group Policy Editor, go to Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell.
Double-click Turn on PowerShell Transcription.
Select Enabled.
Optionally, specify a Transcript output directory. If left blank, transcripts are saved to each user's Documents folder.
Check Include invocation headersto include timestamps and metadata.
Click OK.
Run gpupdate /force to apply the policy.

Transcripts are written to text files with names beginning with PowerShell_transcript .

Get Google SecOps ingestion authentication file

Sign in to the Google SecOps console.
Go to SIEM Settings > Collection Agent.
Click Downloadto download the ingestion authentication file.
Save the file securely on the Windows host where Bindplane agent will be installed.

Note: This JSON file contains credentials for authenticating the Bindplane agent to Google SecOps.

Get Google SecOps customer ID

Sign in to the Google SecOps console.
Go to SIEM Settings > Profile.
Copy and save the Customer IDfrom the Organization Detailssection.

Note: The customer ID is required for configuring the Bindplane agent exporter.

Install Bindplane agent

Install the Bindplane agent on your Windows host according to the following instructions.

Windows installation

Open Command Promptor PowerShellas an administrator.

Run the following command:

  msiexec 
  
 / 
 i 
  
 "https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi" 
  
 / 
 quiet

Wait for the installation to complete.
Verify the installation by running:
```
 sc query observiq-otel-collector 
```
The service should show as RUNNING.

Additional installation resources

For additional installation options and troubleshooting, see the Bindplane agent installation guide .

Configure the Bindplane agent to collect PowerShell logs

Locate the Windows configuration file

Locate the Windows configuration file as follows:

 notepad "C:\Program Files\observIQ OpenTelemetry Collector\config.yaml"

Edit the configuration file

Replace the entire contents of config.yaml with the following configuration:

  receivers 
 : 
  
 windowseventlog/powershell 
 : 
  
 channel 
 : 
  
 Microsoft-Windows-PowerShell/Operational 
  
 max_reads 
 : 
  
 100 
  
 poll_interval 
 : 
  
 5s 
  
 raw 
 : 
  
 true 
  
 start_at 
 : 
  
 end 
 processors 
 : 
  
 batch 
 : 
 exporters 
 : 
  
 chronicle/powershell 
 : 
  
 compression 
 : 
  
 gzip 
  
 creds_file_path 
 : 
  
 'C:\Program 
  
 Files\observIQ 
  
 OpenTelemetry 
  
 Collector\ingestion-auth.json' 
  
 customer_id 
 : 
  
 '<CUSTOMER_ID>' 
  
 endpoint 
 : 
  
 malachiteingestion-pa.googleapis.com 
  
 log_type 
 : 
  
 'POWERSHELL' 
  
 raw_log_field 
 : 
  
 body 
  
 override_log_type 
 : 
  
 false 
 service 
 : 
  
 pipelines 
 : 
  
 logs/powershell 
 : 
  
 receivers 
 : 
  
 - 
  
 windowseventlog/powershell 
  
 processors 
 : 
  
 - 
  
 batch 
  
 exporters 
 : 
  
 - 
  
 chronicle/powershell

Configuration parameters

Replace the following placeholders:

Receiver configuration:
- channel : The Windows Event Log channel to collect from. For PowerShell Script Block Logging, use Microsoft-Windows-PowerShell/Operational . For Module Logging, use Windows PowerShell .
- raw : Set to true to send raw Windows Event Log XML to Google SecOps.
- start_at : Set to end to collect only new events after the agent starts. Set to beginning to collect all existing events.
Exporter configuration:
- <CUSTOMER_ID> : Replace with the customer ID from the previous step.
- creds_file_path : Full path to the ingestion authentication file. Copy the downloaded authentication file to this location.
- endpoint : Regional endpoint URL. Use the endpoint for your Google SecOps region:
  - US: malachiteingestion-pa.googleapis.com
  - Europe: europe-malachiteingestion-pa.googleapis.com
  - Asia: asia-southeast1-malachiteingestion-pa.googleapis.com
  - See Regional Endpoints for complete list.
- log_type : Set to POWERSHELL to use the PowerShell parser.

Save the configuration file

After editing, save the file by clicking File > Save.

Restart the Bindplane agent to apply the changes

Windows

Using Command Prompt or PowerShell as administrator:

 net stop observiq-otel-collector && net start observiq-otel-collector

Or using the Services console:
1. Press Win+R , type services.msc , and press Enter.
2. Locate observIQ OpenTelemetry Collector.
3. Right-click and select Restart.
4. Verify the service is running:
```
 sc query observiq-otel-collector 
```
5. Check logs for errors:
```
  type 
  
 "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log" 
 
```

Verify log ingestion

After configuring the Bindplane agent and restarting the service, PowerShell logs should begin flowing to Google SecOps.

Sign in to the Google SecOps console.
Go to Investigate > Search.

Run the following search to verify PowerShell logs are being ingested:

  metadata 
 . 
 log_type 
  
 = 
  
 "POWERSHELL"

Verify that events appear with recent timestamps.

PowerShell Script Block Logging events (Event ID 4104) will appear with details of executed script blocks, including the script content, script block ID, and execution context.

UDM mapping table

Log Field	UDM Mapping	Logic
HostId	principal.resource.product_object_id	Unique identifier for the product object associated with the principal resource
System.Version	metadata.product_version	Version of the product that generated the event
System.EventId, EventID, winlog.event_id	metadata.product_event_type	Type of event as defined by the product
Computer, System.Computer, computer, winlog.computer_name	principal.hostname	Hostname of the principal entity
Computer, System.Computer, computer, winlog.computer_name	principal.asset.hostname	Hostname of the asset associated with the principal
System.EventRecordID, RecordNumber, winlog.record_id	metadata.product_log_id	Unique identifier for the log entry within the product's logging system
System.Opcode, opcode, winlog.opcode	metadata.description	Description of the event or additional context
ProviderGuid, winlog.provider_guid	metadata.product_deployment_id	Unique identifier for the deployment of the product
System.ProcessID, ProcessID, ExecutionProcessID, execution.process_id, winlog.process.pid	principal.process.pid	Process ID of the principal process
SourceModuleName	principal.resource.name	Name of the resource associated with the principal
SourceModuleType	principal.resource.resource_subtype	Subtype of the resource associated with the principal
security.user_id, UserID, winlog.user.identifier	principal.user.windows_sid	Windows Security Identifier (SID) for the principal user
	metadata.event_type	Type of event (e.g., USER_LOGIN, NETWORK_CONNECTION)
SourceName, winlog.provider_name	metadata.product_name	Name of the product that produced the event
AccountName, Username, UserName, winlog.user.name	principal.user.userid	User ID of the principal user
Domain, winlog.user.domain	principal.administrative_domain	Administrative domain of the principal
Path, target_file, ScriptName, script_name, ContextInfo_Script Name, file_path	target.process.file.full_path	Full path to the file associated with the target process
HostName, powershell.Host Name, ContextInfo_Host Name	target.hostname	Hostname of the target entity
HostName, powershell.Host Name, ContextInfo_Host Name	target.asset.hostname	Hostname of the asset associated with the target
Host ID, HostID, ContextInfo_Host ID	target.asset.asset_id	Unique identifier for the target asset
Nombre_de_comando, ContextInfo_Command Name, CommandName	target.application	Name of the application associated with the target
HostApplication, ContextInfo_Host Application	target.process.command_line	Command line used to launch the target process
ScriptBlockText	target.process.command_line	Command line used to launch the target process
MessageSourceAddress	principal.ip	IP address of the principal
MessageSourceAddress	principal.asset.ip	IP address of the asset associated with the principal
Nombre_de_host	principal.application	Name of the application associated with the principal
Version_de_host	principal.platform_version	Version of the platform associated with the principal
Id_de_host	principal.resource.id	Unique identifier for the principal resource
Application_host	principal.process.file.full_path	Full path to the file associated with the principal process
HostApplication	principal.process.command_line	Command line used to launch the principal process
Usuario, admin_domain	principal.user.userid	User ID of the principal user
Usuario, admin_domain	principal.administrative_domain	Administrative domain of the principal
CommandLine	principal.process.command_line	Command line used to launch the principal process
Machine, machine_id	principal.asset.asset_id	Unique identifier for the principal asset
Machine, platform_software	principal.asset.platform_software.platform	Platform type of the asset (e.g., WINDOWS, LINUX)
Machine, platform_software	principal.asset.platform_software.platform_version	Version of the platform software on the asset
MessageSourceAddress	intermediary.ip	IP address of the intermediary entity
MessageSourceAddress, Hostname	intermediary.hostname	Hostname of the intermediary entity
MessageSourceAddress, Hostname	intermediary.asset.hostname	Hostname of the asset associated with the intermediary
MessageSourceAddress	intermediary.port	Port number used by the intermediary
HostApplication	target.process.command_line	Command line used to launch the target process
HostId	target.asset.asset_id	Unique identifier for the target asset
SequenceNumber, ContextInfo_Sequence Number, Sequence Number	security_result.detection_fields	Key-value pairs of additional detection information
ProviderName	principal.resource.attribute.labels	Labels or attributes associated with the principal resource
NewEngineState	additional.fields	Additional custom fields not covered by standard UDM schema
PreviousEngineState	additional.fields	Additional custom fields not covered by standard UDM schema
ScriptName	additional.fields	Additional custom fields not covered by standard UDM schema
ManagementGroupName	additional.fields	Additional custom fields not covered by standard UDM schema
Source	additional.fields	Additional custom fields not covered by standard UDM schema
RenderedDescription	security_result.description	Description of the security result or action taken
TenantId	additional.fields	Additional custom fields not covered by standard UDM schema
UserName	principal.user.userid	User ID of the principal user
ActivityID	security_result.detection_fields	Key-value pairs of additional detection information
ExecutionThreadID, execution.thread_id, winlog.process.thread.id	security_result.detection_fields	Key-value pairs of additional detection information
Output	security_result.detection_fields	Key-value pairs of additional detection information
Data	security_result.detection_fields	Key-value pairs of additional detection information
Data_1	additional.fields	Additional custom fields not covered by standard UDM schema
data_1	security_result.detection_fields	Key-value pairs of additional detection information
Data_2	security_result.detection_fields	Key-value pairs of additional detection information
winlog.activity_id	security_result.detection_fields	Key-value pairs of additional detection information
winlog.api	additional.fields	Additional custom fields not covered by standard UDM schema
winlog.channel	principal.resource.attribute.labels	Labels or attributes associated with the principal resource
Offset	additional.fields	Additional custom fields not covered by standard UDM schema
SeverityValue	security_result.detection_fields	Key-value pairs of additional detection information
intermediary	intermediary	Details about intermediary entities involved in the event
security_result	security_result	Overall security result including actions, severities, and detections
	metadata.vendor_name	Name of the vendor that produced the event
SourceName	metadata.product_name	Name of the product that produced the event

Need more help? Get answers from Community members and Google SecOps professionals.