-
Notifications
You must be signed in to change notification settings - Fork 0
Configuration File [Alert]
WebsiteFailedLogins will only alert when a threshold has been met or exceeded. The following are methods in which alerts are generated and the desired format of alert data.
Three alert methods are available. While Standard Out is always used, one can use both Smtp and WinEvent, just one, or none.
Smtp will send alerts via SMTP (email). Has ability to ingest a credential file to enable authenticated SMTP. This can be useful when integrating with ticketing systems or even monitoring stand-alone systems. See [Smtp] configuration settings for details.
WinEvent writes an event to the Windows Application event log. This option is useful when integrating with centralized log collection though my require modifying log shipping policies. See [WinEvent] configuration settings for details.
This option is always enabled. An object is returned every time Invoke-WebsiteFailedLogins is launched. Review the following for information on how to work with the returned object.
Method = WinEventMethod = Smtp,WinEventMethod = noneThe message data of an alert can be formatted three different ways to make integration easier. Choose one.
text, each key value pair is printed on a line as key = value.
xml, hashtable is serialized to xml. To deserialize the xml back into a hashtable use [System.Management.Automation.PSSerializer]::Deserialize($obj).
json, hashtable is serialezed to json using ConvertTo-Json. Use ConvertFrom-Json to deserialize.
DataType = textDataType = xmlDataType = json