box.all.win

Introduction

This union table collects information from a set of tables that contain system events generated and sent from Windows machines.

Source tables

The information displayed is extracted from the following tables:

Check source tables

box.devo_ea.events_windows
box.devo_ua.events_windows
box.win
box.win_classic
box.win_cloudwatch
box.win_hf
box.win_kinesis
box.win_nxlog
box.win_quest.change_auditor.leef
box.win_snare
box.win_solarwinds
box.win_winlogbeat
cloud.azure.vm.applicationevent
cloud.azure.vm.securityevent
cloud.azure.vm.systemevent

Table structure

This is the set of columns displayed by this union table, which is the result of the collection of columns present in all source tables:

Extra columns

Fields marked as Extra in the table below are not shown by default in data tables and need to be explicitly requested in the query. You can find them marked as Extra when you perform a query so they can be easily identified. Learn more about this in Selecting unrevealed columns.

Field	Type	Extra fields
eventdate	`timestamp`
source_event_date	`timestamp`
source	`str`
keywords	`str`
event_type	`str`
channel	`str`
category	`str`
event_id	`int4`
username	`str`
security_id	`str`
account	`str`
domain	`str`
machine_ip	`ip4`
subject_security_id	`str`
subject_username	`str`
subject_domain	`str`
subject_logon_id	`str`
target_security_id	`str`
target_username	`str`
target_domain	`str`
target_logon_id	`str`
target_object	`str`
target_image	`str`
member_security_id	`str`
member_name	`str`
group_security_id	`str`
group_name	`str`
group_domain	`str`
sam_account_name	`str`
logon_type	`str`
logon_guid	`str`
logon_process	`str`
user_account_control	`str`
object_name	`str`
object_value_name	`str`
object_type	`str`
object_server	`str`
object_handle	`str`
object_resource_attribute	`str`
pid	`str`
process_name	`str`
process_guid	`str`
service	`str`
service_file_name	`str`
service_account	`str`
machine	`str`
workstation	`str`
message	`str`
extended_message	`str`
source_name	`str`
source_image	`str`
source_hostname	`str`
source_ip	`str`
source_port	`str`
destination_hostname	`str`
destination_ip	`str`
destination_port	`str`
status	`str`
sub_status	`str`
accesses	`str`
access_mask	`str`
granted_access	`str`
properties	`str`
recovery_reason	`str`
token_elevation_type	`str`
mandatory_label	`str`
caller_process_name	`str`
caller_process_name	`str`
new_pid	`str`
new_process_name	`str`
parent_pid	`str`
parent_process_name	`str`
parent_process_guid	`str`
parent_command_line	`str`
process_command_line	`str`
file_path	`str`
file_version	`str`
original_file_name	`str`
current_directory	`str`
integrity_level	`str`
hashes	`str`
company	`str`
product	`str`
description	`str`
import_hash	`str`
start_module	`str`
start_function	`str`
computer_name	`str`
device	`str`
pipe_name	`str`
query_name	`str`
query_status	`str`
query_results	`str`
share_name	`str`
share_local_path	`str`
relative_target_name	`str`
class_id	`str`
class_name	`str`
device_id	`str`
device_name	`str`
task_name	`str`
task_content	`str`
ticket_options	`str`
ticket_encryption_type	`str`
signature	`str`
initiated	`str`
key_length	`int8`
reason	`str`
image	`str`
parent_image	`str`
context_info	`str`
engine_version	`str`
host_version	`str`
payload	`str`
layer_rtid	`str`
authentication_package_name	`str`
new_value	`str`
privilege_list	`str`
attribute_value	`str`
attribute_ldap_display_name	`str`
audit_policy_changes	`str`
power_shell_script_block_id	`str`
operation_type	`str`
hostchain	`str`	✓
tag	`str`	✓
rawMessage	`str`	✓

Field transformations

Even though all source tables have several features in common, they have some particularities that make it necessary to undergo a set of transformations to harmonize them for the union table. The most common transformations comprise changes in the data type or the application of rules when several columns in the source table feed a single column in the union table. You can find below the detailed list of transformations in each source table.