Dimensions
Access the dimensions by clicking the Dimensions tab in the left column.
Attack type
The Attack Type dimension provides request data by attack type, namely the dimension groups listed in the left menu (for example, WAF, DoS, and Custom Rule). The display provides the total number of requests by attack type, a graph with the average number of requests per second at given moments within the displayed time period, and a table breaking down the data by the individual attack types, providing the attack type, the number of requests for each, and a graphical display of request distribution within the selected time period.
Protection
The Protection dimension identifies request data by the specific protection applied to your traffic. Each Protection is associated with a Protection Area which groups related protections into broader security categories and uses updated terms for some existing Attack Types. For example, Web Application Firewall is a Protection Area that includes Protections such as SQL injection, cross-site scripting and command injection.
Use Protection and Protection Area when analyzing traffic to focus on what your security controls protected you from. The existing Attack Type dimension remains available for compatibility with existing alerts and configurations.
The following table shows examples of Protections and their corresponding Protection Areas:
| Protection Area | Protection |
|---|---|
| Web Application Firewall | SQL Injection |
| Web Application Firewall | Cross Site Scripting |
| Web Application Firewall | Command Injection |
| Web Application Firewall | Local File Inclusion |
| Web Application Firewall | Remote File Inclusion |
| Web Application Firewall | Web Attack Tool |
| Web Application Firewall | Web Platform Attack |
| Web Application Firewall | Web Protocol Attack |
| Web Application Firewall | Web Policy Violation |
| Web Application Firewall | Uncategorized Web Attacks |
| Web Application Firewall | Penalty Box |
| Web Application Firewall | URL Evasion |
| Web Application Firewall | MCP Protection |
| IP/Geo Firewall | Unwanted IPs and Geos |
| DoS Protection | Rate Limiting |
| DoS Protection | Quota Management |
| DoS Protection | URL Protection |
| DoS Protection | Slow Post protection |
| DoS Protection | Behavioral DDoS |
| Custom Rules | Monitored and mitigated unwanted traffic |
| API Request Constraints | API Protections |
| Client Reputation | Known bad actors |
| Bot & Agent Control | Active Protection |
| Bot & Agent Control | Custom bots |
| Bot & Agent Control | Transparent Protection |
| Bot & Agent Control | Bot Attacks on Transactional Endpoints |
| Bot & Agent Control | Account Protection |
| Bot & Agent Control | Content Protection |
| Bot & Agent Control | Custom bots |
| Bot & Agent Control | Verified bots |
| Bot & Agent Control | Impersonation |
| Malware Protection | - |
| Client-Side Protection & Compliance | - |
| AAP Hybrid | - |
| AI Application Firewall | - |
| API Security | API Security |
Common
The Common dimension group provides data in a number of dimensions common to all incoming requests.
When you select a dimension, you can see the total number of requests, a graph with the average number of requests per second at given moments within the displayed time period, a table with additional details on the dimension, and a graphical display of request distribution within the selected time period.
- IP address. The dimension provides request data by IP address.
In addition, you can have the table display either the Connecting IP Address (the IP address that connected to Akamai's edge servers) or the End User IP Address (which will differ from the connecting IP address if the edge server acted on an IP address taken from the x-forwarded-for header).
Country, company, and domain are calculated at run time, so while it's possible these values could be different subsequent to the event's triggering, occurrences like this are rare.
-
IP subnet. The dimension provides request data by IP subnet. These are calculated by
truncating the IP address to a /24 netmask for IPv4 and a /64 netmask for IPv6.
In addition, you can have the table display either the Connecting IP Subnet or the End User IP Subnet. -
AS number. The dimension provides request data by AS (autonomous system) number, which
identifies the originating network.
In addition, you can have the table display either the Connecting AS Number or the End User AS Number. AS numbers are calculated by a reverse look up on the connecting IP addresses or the end users' IP addresses at the time the requests were received by Akamai's edge servers. -
Country/Area. The dimension provides request data by geography.
In addition, you can have the table display either the Connecting Country/Area or the End User Country/Area. Country/area is calculated by a reverse look up on the connecting IP address or the end user IP address at the time the request was received by Akamai's edge servers. -
Hostname. The dimension provides request data by hostname.
-
Path. The dimension provides request data by path.
The Path filter is a free-text field and does not automatically split query strings. Query parameters (anything after
?) are stored separately. Do not include the?or any query parameters in the Path filter, or your search will return zero results. Use the Query dimension for those values.
- Query. The dimension provides request data by query string.
In the Statistics view, if a query string is longer than 1000 characters, the system trims it to the first 1000 characters and adds a "[TRUNCATED]" suffix. You can still see the full query value in the Sample Log view.
- Referer. The dimension provides request data by the referer header.
In the Statistics view, referer is displayed without the query string to allow for better aggregation. The full referer field is available in the Samples view.
-
URL. The dimension provides request data by URL.
-
User-Agent. The dimension provides request data by User-Agent header.
-
SDK version. The dimension lets you filter on a version of Bot Manager Premier Mobile
Protection Module that you use to protect native mobile apps.
The returned value may be empty if the request came from a web client or the request was stopped by an edge detection, for example with a reason code 3902001. For more information about the code, see Behavioral detection
- Native mobile app version. For Bot Manager Premier only. The dimension lets you filter on a version you entered when defining your native mobile apps. It can be, for example, the Earliest app version with SDK integrated or Earliest app version using Proof-of-Work feature.
The returned value may be empty if you have no User agent version prefix defined for your native mobile application.
-
Action. The dimension provides request data by action type such as alert and deny.
-
API ID. The dimension provides request data by your API IDs.
The API ID dimension is only available if API protections are enabled.
-
API resource purpose name. The API resource purpose name dimension for bot management shows request data by individual API resource purpose names you defined when registering an API. This value is the name you gave to any transactional endpoints you defined in order manage their bot traffic using behavior anomaly detections.
-
API resource purpose type. The API resource purpose type dimension for bot management lets you see request data by the types you assigned to API resource purposes. Type is the task a resource serves, like login. You define and name an individual API resource purpose when you register an API. Then you can manage its bot traffic using behavior anomaly detections.
-
Origin response. View request data grouped by the response to the requests forwarded to the protected endpoints on your origin server:
-
Fail - the request was rejected.
-
Success - the request was fulfilled.
-
Unknown - the request doesn't meet the defined criteria to be a failure or success.
-
-
API key. The API Key dimension provides request data by your API keys.
The API key dimension is only available if API protections are enabled.
- Policy. The dimension provides request data by your firewall policies.
Policy name is the current name assigned to the policy ID. Should the name change during the displayed analysis period, the new name used.
- Status code. The dimension provides request data by status code.
IP/geo firewall
The IP/Geo Firewall dimension group provides network list data for incoming requests.
When you select a dimension, you can see the total number of requests, a graph with the average number of requests per second at given moments within the displayed time period, a table with additional details on the dimension, and a graphical display of request distribution within the selected time period.
- Network list. The Network List dimension provides request data by network list.
The network list's name is obtained from the security configuration at run time. So, if it was changed during the course of analysis, only the new name will appear in this report.
DoS protection
The DoS Protection dimension group provides data in two DoS (denial of service) dimensions, DoS category and rule, for incoming requests.
When you select a dimension, you can see the total number of requests, a graph with the average number of requests per second at given moments within the displayed time period, a table with additional details on the dimension, and a graphical display of request distribution within the selected time period.
-
DoS category. The DoS Category dimension provides request data by DoS category (rate, slow POST, or DoS anomaly).
-
Rule. The Rule dimension provides request data by individual rules.
The rule name is the current name assigned to the rule ID. Should the name change during the analysis period, the new name is the one displayed.
Custom rules
The Custom Rules dimension group provides data in three custom rule dimensions—rule, selector, and match—for incoming requests.
When you select a dimension, you can see the total number of requests, a graph with the average number of requests per second at given moments within the displayed time period, a table with additional details on the dimension, and a graphical display of request distribution within the selected time period.
- Rule. The Rule dimension provides request data by individual custom rules.
The rule name is the current name assigned to the rule ID. Should the name change during the analysis period, the new name is the one displayed.
-
Selector. The Selector dimension provides request data by selector, the HTTP property on which the rule triggered.
-
Match. The Match dimension provides request data by match, the HTTP property value within the request that triggered the rule.
-
Message. The Message dimension provides request data by message.
-
Tag. The Tag dimension provides request data by tag.
Web application firewall
The Web Application Firewall dimension group provides data in five web application firewall (WAF) dimensions—WAF category, rule combination, rule, selector, and match—for incoming requests.
When you select a dimension, you can see the total number of requests, a graph with the average number of requests per second at given moments within the displayed time period, a table with additional details on the dimension, and a graphical display of request distribution within the selected time period.
-
Attack Group. The Attack Group dimension provides request data by attack group (SQL injection, total inbound, and command injection, for example).
Refer to the About rules topic for more information on attack groups. -
Rule combination. The Rule Combination dimension provides request data by different combinations of rules.
-
Rule. The Rule dimension provides request data by individual rules.
The rule name is the current name assigned to the rule ID. Should the name change during the analysis period, the new name is the one displayed.
-
Selector. The Selector dimension provides request data by selector, the HTTP property on which the rule triggered.
-
Match. The Match dimension provides request data by match, the HTTP property value within the request that triggered the rule.
Client reputation (Client Reputation only)
The Client Reputation dimension group provides data in three Client Reputation dimensions—reputation profile, reputation category, and reputation score—for incoming requests.
When you select a dimension, you can see the total number of requests, a graph with the average number of requests per second at given moments within the displayed time period, a table with additional details on the dimension, and a graphical display of request distribution within the selected time period.
- Reputation profile. The Reputation Profile dimension provides request data by Client Reputation profiles.
Multiple reputation profiles can trigger on a single request.
Policy name is the current name assigned to the policy ID. Should the name change during the displayed analysis period, the new name is used.
For more information regarding Client Reputation profiles, go to Control for client reputation.
-
Reputation category. The Reputation Category dimension provides request data by Client Reputation category.
-
Reputation score. The Reputation Score dimension provides request data by Client Reputation score.
For information on reputation score is, see Control for client reputation.
Bot & Agent Control - General
The Bot & Agent Control - General group provides request data in several dimensions related to automated traffic and bot behavior.
When you select a dimension, you can see the total number of requests, a graph with the average number of requests per second at given moments within the displayed time period, a table with additional details on the dimension, and a graphical display of request distribution within the selected period.
-
Bot type. View requests grouped by bot type:
- Akamai are bots that Akamai has identified and defined for you. You see these bots listed in Bot & Agent Control under verified bots, and can set action by category. For example, you may want to allow all web search engines, but not enterprise data aggregators.
- Customer are bots that you defined (under Custom bots) in order to allow or block requests.
- Unknown are bots that have no declared identity, but that doesn't mean Bot & Agent Control knows nothing about them. Though the source is unknown, Bot & Agent Control uses detected characteristics to dynamically "name" these verified detected bots using botnet ID.
-
Bot Category. The Bot Category dimension provides request data by Bot & Agent Control category.
These could be: verified, custom-categorized, or unknown bots (those not officially categorized but that tripped the detection specified, like Unknown Bots (Session Validation Failed)). -
Botnet ID. The Botnet ID dimension provides request data by individual botnets.
-
Bot Score. If you're using bot score to set your response strategy, this dimension lists the number of requests by bot score ranges of 10.
-
Bot Score Response Segment. If you're using bot score, this shows the number of requests by the Bot Score Response Segments, which you use to set response actions for different bot score ranges.
-
Request Type. Shows both request type set when you create your scope rule (left) and the request type provided in the origin response (right). If the left side shows “Auto” in front of the type that means the request type was set to “Both” in the scope rule and it was automatically determined based on the incoming headers.
-
Request Type Mismatch. Shows the traffic that has a different request type received than the request type that was set in the scope rule settings.
-
Bot Scope Rule | Policy. Displays either triggered policy rules or protected asset names (or both), depending on whether you use the legacy or the new Bot & Agent Control experience.
-
Rule. The Rule dimension provides request data by individual rules.
-
Rule Name. The rule name is the current name assigned to the rule ID. Should the name change during the analysis period, the new name is the one displayed.
-
Rule Combination. The Rule Combination dimension provides request data by
different combinations of rules.
Bot & Agent Control - User Details
The Bot & Agent Control - User Details group provides request data in several dimensions related to user behavior and risk.
The display provides the total number of requests by attack type, a graph with the average number of requests per second at given moments within the displayed time period, and tables breaking down the data by dimensions, such as User ID, User Risk Level, User Score Status, Device ID, and providing additional details.
- User ID. The User ID dimension provides request data by individual web users represented by their UUID (universally unique identifier).
- User Risk Score. The likelihood that a request to a protected endpoint doesn't come from the real account owner. Measured on a scale from 0 (least likely) to 100. Appears as a dimension, but you can also just filter on user risk score to focus on high scores, like greater than 90, for example.
- User Risk Level. View the number and distribution of requests grouped by risk level:
- Critical - requests by users with a score range from 76 to 100.
- High - requests by users with a score range from 51 to 75.
- Medium - requests by users with a score range from 26 to 50.
- Low - requests by users with a score range from 0 to 25.
- User Risk Response Segment. View the number and distribution of requests grouped by risk response segment:
- Aggressive Response. Contains higher scores, which most likely mean that the requester is not the legitimate account owner.
- Cautious Response. Most appropriate for lower risk scores.
- Strict Response. Middle ground where you can see requests with some suspicious traits, but not definitely malicious.
- User Score Status View the number and distribution of requests grouped by user score status:
- Critical - requests by users with a score range from 76 to 100.
- High - requests by users with a score range from 51 to 75.
- Medium - requests by users with a score range from 26 to 50.
- Low - requests by users with a score range from 0 to 25.
| Score | Description |
|---|---|
| 0 | User profile sufficient to score |
| 1 | No score: Unknown error |
| 2 | No user profile yet. Possibly no previous successful logins seen. Score based on other factors. |
| 3 | Partial user profile built: scored on other factors. Previously successful logins have been seen but not enough to have a full view of a user's activity. Score based on the partial user profile and other indicators. |
| 4 | Request scored without telemetry |
| 5 | No score: timed out |
| 6 | Username blank: scored on non-profile factors |
| 7 | Can’t identify user: scored on non-profile factors |
-
Device ID. View request data grouped by the unique device identifier used to send the request.
-
Email Domain. View request data grouped by the domain name extracted from the user email address.
-
Indicator. View requests by anomalies that contribute a user risk score.
-
Indicator Type. View requests by the type of indicator: risk or trust.
-
Rule. The Rule dimension provides request data by risk rules.
-
Rule name. The rule name is the current name assigned to the rule ID. Should the name change during the analysis period, the new name is the one displayed.
API Security
The API Security dimension group provides data for Runtime incidents detected by Akamai API Security.
Web Security Analytics includes a predefined API Security view in the Predefined and Recent views list. The view includes the following API Security-specific dimensions:
- Incident Type. View and filter activity by the type of Runtime incident detected.
- Incident Severity. View and filter incidents by severity.
- Attacker Identifier. View and filter activity associated with an attacker identified by API Security.
- API URL. View and filter activity targeting a specific API URL.
Use these dimensions individually or combine them with common Web Security Analytics dimensions, such as source IP address or JA4 client fingerprint, to narrow your analysis and correlate API Security incidents with related security events.
In the Samples view, common dimensions are displayed by default. The Action Applied column shows how API Security handled the activity: - Alert indicates that API Security detected and reported the activity as a Runtime incident.
- Deny indicates that an API Security native connector blocked the activity.
Sampled data
API Security Runtime incidents in Web Security Analytics include only one automatically selected request and response sample, not the full request history. To view complete incident details, go to API Security.
Updated 5 days ago
