USM Anywhere™

AWS Windows

When you configure the AWS Windows integration to send log data to USM Anywhere, you can use the AWS Windows plugin to translate the raw log data into normalized events for analysis.

Device Details
Device vendor Amazon
Device type Management platform
Connection type CloudWatch
Vendor link None

AWS Windows Integration

For more information about AWS log collection, see AWS Log Discovery and Collection in USM Anywhere.

  1. Follow the instructions on the AWS website to install the CloudWatch Agent on your host.

    Note: If you choose to enable CloudWatch Logs in your Amazon Web Services (AWS) environment, you should make sure that you are not collecting more data than you need because this service incurs AWS costs based upon usage. See the CloudWatch pricing information to plan and configure your usage.

  2. Configure the agent to send Windows logs to the group Windows-System-Logs.
  3. In USM Anywhere, go to Settings > Scheduler and enable the CloudWatch - Windows System Logs default job.

    This enables USM Anywhere to find the logs automatically.

    Enable the default Windows-System-Logs job in the Scheduler

  4. Wait for events to appear in the Events page.

Plugin Enablement

For plugin enablement information, see Adding AlienApps to an Asset.

Available Plugin Fields

The following plugin fields are important attributes extracted from the syslog message. The USM Anywhere reports use these fields, and you can also reference them when creating custom reports. In addition to reporting, the USM Anywhere correlation rules make use of these fields.

  • authentication_mode
  • authentication_type
  • destination_address
  • destination_hostname
  • destination_port
  • event_category
  • event_subcategory
  • event_description
  • event_name
  • event_severity
  • file_hash
  • file_hash_algorithm
  • file_name
  • file_create_time
  • file_old_create_time
  • rep_device_rule_id
  • source_address
  • source_hostname
  • source_ntdomain
  • source_port
  • source_process
  • source_process_commandline
  • source_process_id
  • source_process_parent
  • source_process_parent_commandline
  • source_process_parent_process_id
  • source_userid
  • source_username


For troubleshooting, refer to the vendor documentation: