Recent Event Logs

1. Navigate to the Logs page.
   1. From the Edgio Console, select the desired team space.
   2. From the Security section, click Logs.
   By default, the dashboard displays recent log events for threats (i.e., access rule, custom rule, and managed rule violations).
2. Optional. Click on the Bot, Rates, or Rate Enforcement tab to view recent log events for bot traffic or rate limiting.

Threat Log Data #

• <Rule Message>: Identifies the rule that was violated.
• <Elapsed Time>: Indicates the amount of time that has passed since the request was screened.
• <Time>: Indicates the time (UTC) at which the request was screened.

Threat Log Fields #

• Timestamp: Indicates the point-in-time at which the rule violation occurred. This timestamp is reported using a 24 hour time format (UTC/GMT).
  Format:
  <YYYY>-<MM>-<DD> <hh>:<mm>:<ss>.<milliseconds>
  Example:
  2023-07-08 15:00:22.123
• Managed Rules Name: Indicates the name of the managed rule set that was violated. If a managed rule was not violated, then this field will be empty.
• Rule Message: Provides a description of the rule that the request violated. The syntax for this field varies according to the type of rule that was violated.
  • Managed Rule Set - Anomaly Score: This field indicates the request’s anomaly score and the last rule that it violated. Please refer to the Sub Event(s) section, which contains a sub event for each rule violated by a request, to find out why the request was flagged or blocked. Each sub event indicates the rule that was violated and the data used to identify the violation.
    Inbound Anomaly Score Exceeded (Total Score: <#>): Last Matched Message: <Rule Message>
  • Syntax (All Other Rule Sets):
    <Rule Message>
• Event ID: Indicates the system-defined ID assigned to this event (i.e., rule violation).
• Security Application Name: Indicates the name of the Security Application Manager configuration that was assigned the rule set that was triggered.
• Profile Type: Indicates whether the request was screened as a result of a production or audit rule.
• Country Name: Identifies the country from which the request originated by its name.
• Action Type: Indicates the type of action that was taken in response to the rule violation. Valid values are:
  • BLOCK_REQUEST: Indicates that the request that violated a rule was blocked.
  • ALERT: Indicates that an alert was generated in response to the rule violation.
  • REDIRECT_302: Indicates that the request that violated a rule was redirected to the URL associated with the instance defined by the Instance Name field.
  • CUSTOM_RESPONSE: Indicates that a custom response was returned to the client that submitted a request that violated a rule.
• Client IP: Identifies the IP address of the client from which the request originated.
• URL: Indicates the URL of the request that triggered the rule violation.
• Referer: Indicates the request’s referrer as defined by the Referer request header.
• User Agent: Indicates the user agent that submitted the request that triggered the rule violation. This information is derived from the User-Agent request header.

Sub Events #

• Matched On: Indicates a variable that identifies where the violation was found.
• Matched Value: Indicates the value of the variable defined by the Matched On field.

• Rule ID: Indicates the ID for the rule that the request violated.
• Rule Message: Provides a description of the rule that the request violated.
• Operator Name: Indicates how the system interpreted the comparison between the Operator Parameter and the Matched Value fields. Common operators are:
  • BEGINSWITH: Begins with. Identifies a match due to a request element that started with the specified match value.
  • CONTAINS: Contains. Identifies a match due to a request element that contained the specified match value.
  • ENDSWITH: Ends with. Identifies a match due to a request element that ended with the specified match value.
  • STREQ: Exact match. Identifies a match due to a request element that was an exact match to the specified match value.
  • RX: Regex. Identifies a match due to a request element that satisfied the regular expression defined in the match value.
  • EQ: Value match. Identifies a match due to a request element that occurred the exact number of times defined in your custom rule.
  • IPMATCH: IP Address. Identifies a match due to the request’s IP address either being contained within an IP block or that was an exact match to an IP address defined in your custom rule.
• Operator Parameter: Indicates the source or the value that was compared against the Matched Value field.
• Rule Tags: Indicates the tags associated with the rule that the request violated. These tags may be used to determine whether a rule, access control, or global setting was violated.
  Naming convention:
  <Rule Set>/<Category>/<Subcategory>
  <Category> identifies whether the request violated a rule, an access control, or the delivery profile.
  Example values:
  • Policy: The following sample values identify a policy:
    OWASP_CRS/PROTOCOL_VIOLATION/INVALID_HREQ OWASP_CRS/WEB_ATTACK/SQL_INJECTION
  • Blacklist: The following sample values identify a blacklist criterion:
    BLACKLIST/IP BLACKLIST/COUNTRY BLACKLIST/REFERRER BLACKLIST/URL
  • Setting: The following sample values identify a setting:
    OWASP_CRS/POLICY/SIZE_LIMIT
• Total Anomaly Score: Indicates the anomaly score assigned to the request. This score is determined by the number of rules that were violated and their severity.

Bot Log Data #

• <Rule>: Identifies the rate rule that was violated by its name.
• <Elapsed Time>: Indicates the amount of time that has passed since the request was screened.
• <Time>: Indicates the time (UTC) at which the request was screened.

Bot Log Fields #

• Bot Rules Name: Indicates the name of the bot rule set that triggered the browser challenge.
• Browser Challenge Status: Indicates the reason why a browser challenge was served. Valid values are:
  • CHAL_STATUS_NONE: Indicates that a browser challenge was not issued.
  • CHAL_STATUS_IP_MISMATCH: Indicates that a browser challenge was served due to an invalid token. This status is typically reported when a token is shared or the user’s IP address is modified after the initial token was generated.
  • CHAL_STATUS_NO_TOKEN: Indicates that a browser challenge was served for a new session.
  • CHAL_STATUS_TOKEN_CORRUPTED: Indicates that a browser challenge was served due to an invalid token. This status is typically reported when a user agent submits a request that includes a token that our service cannot decrypt.
  • CHAL_STATUS_TOKEN_EXPIRED: Indicates that a browser challenge was served due to an expired token. This status is typically reported when a user agent (e.g., web browser) submits a request after the expiration of the previously solved browser challenge.
    You may configure the duration for which our CDN will serve content to a client that solves a browser challenge without requiring an additional browser challenge through the Security Application’s Valid for (in minutes) option.
  • CHAL_STATUS_UA_MISMATCH: Indicates that a browser challenge was served due to an invalid token. This status is typically reported when a token is shared with another user agent (e.g., web browser) within the same machine.
  • CHAL_STATUS_WRONG_ANSWER: Indicates that a browser challenge was served because the user was unable to solve the previous browser challenge. This status may also be reported when the user agent (e.g., web browser) submits a tampered token.
• Client IP: Identifies the IP address (IPv4) of the client from which the request originated.
• Country Name: Identifies the country from which the request originated.
• Matched On: Indicates a variable that identifies where the violation was found.
• Matched Value: Indicates the value of the variable defined by the Matched On field.
  Standard security practices dictate that measures should be taken to prevent sensitive data (e.g., credit card information or passwords) from being passed as clear text from the client to your origin server. Another incentive for encrypting sensitive data is that it will be logged by our system when an alert is triggered as a result of this data. If sensitive data cannot be encrypted or obfuscated, then it is strongly recommended to contact our technical customer support to disable logging for the Matched Value field.
• Referer: Indicates the request’s referrer as defined by the Referer request header. A referrer identifies the address of the resource that linked to the requested content.
• Request Method: Indicates the request’s HTTP method.
  Format:
  HTTP_METHOD_<NAME>
  Example:
  HTTP_METHOD_GET
• Rule ID: Indicates the ID of the rule that triggered the browser challenge.
• Rule Message: Indicates the message of the rule that triggered the browser challenge.
• Security Application Name: Indicates the name of the Security Application configuration that was assigned the bot rule set that was triggered.
• Timestamp: Indicates the date and time (UTC) at which the browser challenge was issued.
  This field is only available from within the Event Log view. Requests may not be filtered by this field. Filter by time through the Time Range option that appears on the left-hand side of the dashboard.
  Local time is displayed on the right-hand side of the event log entry header that appears directly above this field.
• Token Validity Duration: Indicates the number of minutes for which our CDN will serve content to a client that solves a browser challenge without requiring an additional browser challenge.
• URL: Indicates the URL for which a browser challenge was issued.
• User Agent: Indicates the user agent (e.g., web browser) that submitted the request that resulted in a browser challenge. A request’s user agent is defined in the User-Agent request header.

Rate Limit Log Data #

• <Rule>: Identifies the rate rule that was violated by its name.
• <Elapsed Time>: Indicates the amount of time that has passed since the request was screened.
• <Time>: Indicates the time (UTC) at which the request was screened.
• <Action Type>: Represents the type of action that was applied to the rate limited request. This action is determined by the rate rule that it violated.

Rate Limit Log Fields #

• Client IP: Identifies the IP address (IPv4) of the client from which the request originated.
• Country Name: Identifies the country from which the request originated.
• Action Type: Indicates the action (e.g., CUSTOM-RESPONSE) that was applied to the rate limited request.
• Referer: Indicates the request’s referrer as defined by the Referer request header. A referrer identifies the address of the resource that linked to the requested content.
• Request Method: Indicates the request’s HTTP method.
  Format:
  HTTP_METHOD_<NAME>
  Example:
  HTTP_METHOD_GET
• Rule Name: Indicates the name of the rule that was applied to the rate limited request.
• Timestamp: Indicates the date and time (UTC) at which the request was rate limited.
  This field is only available from within the Event Log view. Requests may not be filtered by this field. Filter by time through the Time Range option that appears on the left-hand side of the dashboard.
  Local time is displayed on the right-hand side of the event log entry header that appears directly above this field.
• URL: Indicates the URL of the request that was rate limited.
• User Agent: Indicates the user agent that submitted the request that was rate limited. A request’s user agent is defined in the User-Agent request header.

Rate Limit Enforcement Log Data #

• <Rule>: Identifies the rate rule that was violated by its name.
• <Elapsed Time>: Indicates the amount of time that has passed since the request was screened.
• <Time>: Indicates the time (UTC) at which the request was screened.
• <Action Type>: Represents the type of action that was applied to the rate limited request. This action is determined by the rate rule that it violated.

Rate Limit Enforcement Log Fields #

• Action Name: Indicates the name of the action that was applied to rate limited requests as a result of this enforcement event.
• Action Type: Indicates the type of action (e.g., custom-response) that was applied to rate limited requests as a result of this enforcement event.
• Rule Name: Indicates the name of the rule whose threshold was exceeded.
• Timestamp: Indicates the date and time (UTC) at which rate limiting enforcement was initiated.
  This field is only available from within the Event Log view. Requests may not be filtered by this field. Filter by time through the Time Range option that appears on the left-hand side of the dashboard.