When you configure Microsoft IIS (Internet Information Services) Server on AWS integration to send log data to the USM Anywhere AWS Sensor, you can use the plugin to translate the raw log data into normalized events for analysis.
|Device type||Web server|
Integrating Microsoft IIS Server
Two versions of this plugin are available, depending on the version of the IIS.
- Microsoft IIS (pre 8.0) Plugin
- Microsoft IIS 8.0+ Plugin
To configure Microsoft IIS on AWS to send log data through CloudWatch
Follow the instructions on the AWS web site 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 Amazon CloudWatch pricing information to plan and configure your usage.
Configure the agent to send IIS logs to the group IIS-Logs.
Important: USM Anywhere expects all the log streams in a group to be the same content type (use the same plugin), in this case, Microsoft IIS 8.0+ plugin or Microsoft IIS (pre-8.0) plugin.
In the USM Anywhere web UI, go to Settings > Scheduler and enable CloudWatch - IIS Logs.
This enables USM Anywhere to find the logs automatically without your needing to create a scheduled job.
Important: Only the Microsoft II 8.0+ plugin allows USM Anywhere to match the logs automatically. For this reason, if you need to use the Microsoft II (pre-8.0) plugin, you must schedule a job manually. For instructions, see Collecting Amazon CloudWatch Logs.
- Wait for events to appear in the Events page.
For plugin enablement information, see Manual Plugin Management.
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.
For troubleshooting, refer to the vendor documentation: