Customize error pages
Error pages appear when a user violates SIA policy. For example, when a user attempts to access content that is blocked by the AUP or attempts to access a blocked domain or IP address. An error page warns users that website access is prohibited and a violation occurred.
The first time a policy is deployed with a Block action and an Error Page response, it may take up to 30 minutes for the error page to appear to the user.
SIA includes error pages that you can customize. You can customize the appearance of these pages, the language of text, and some of the text that’s provided. If you don’t want to use a SIA error page, you can also choose to show an error page that’s hosted by your organization.
For a complete list of settings that you can modify in SIA error pages, see Error page customization. To use a hosted error page instead of SIA error pages, see Use a hosted error page.
Error pages appear in the language that is associated with the end-user's browser. These pages are translated by the browser.
Know the following:
-
If you deployed ETP Client, a custom or hosted error page does not appear to end users who make requests from unidentified IP locations. Instead, the users see the Website Access Prohibited message without any customization.
-
If you configure a DNS Only policy, users who access blocked HTTPS websites will see a browser error page instead of a SIA error page by default. To show HTTPS error pages for blocked web traffic, enable the Enable HTTPS block pages for DNS only policies setting on the Connection Info page.
Before you enable this setting, make sure you:- Create and distribute a proxy certificate to use the HTTPS block pages.
- If you are using Zero Trust Client or Guardicore Platform Agent, enable Transparent Traffic Interception for Threat Protection.
This page only appears in known locations. Users who make requests from unknown locations cannot see the HTTPS block pages. If you are using the Zero Trust Client, this page does not appear for blocked traffic that’s outside your organization’s network. To resolve this issue, your organization can now deploy the latest client that’s called Guardicore Platform Agent. For more information on Guardicore Platform Agent, see the Guardicore Platform Agent documentation.
Types of error pages
If you choose to use SIA error pages, these error pages are available:
- Website Access Prohibited
- Threat Website Warning
- Acceptable User Policy Violation
- Error Warning
- User Authentication Error
Website Access Prohibited
This page warns that the website has been blocked based on the organization’s policy. The error page also indicates what URL was blocked.
This error page appears in these situations:
-
When a user from an Unidentified IPs location attempts to access a domain that may be a security risk. These users are typically remote users who access content from IP addresses that are not already configured as locations in SIA.
-
When SIA proxy is disabled and malicious HTTP or HTTPS traffic is directed to Enterprise Security Connector version 2.5.0.
Threat Website Warning
This message appears when a user attempts to access a domain that is a known or suspected threat. If the proxy is enabled, these error pages also appear for malicious HTTP or HTTPS traffic. The message is specific to the threat type. For example, any one of these warnings may appear on this page:
-
Phishing Website Warning. Appears when a user attempts to access a domain that is known or suspected to perform phishing attacks.
-
Malware Website Warning. Appears when a user attempts to access a domain that is known or suspected to host malware.
-
C&C Website Warning. Appears when a user attempts to access a domain that is known to perform C&C communications.
-
Risky Domains. Appears when a user attempts to access a domain that is known or suspected to be a risk to your organization. These domains are considered risky because they belong to these threat categories: Adware, Coin Mining, Newly Registered, Newly Seen, Potentially Harmful, and DNS Tunneling.
Regardless of threat type, the error page also shows what URL was blocked.
For more information on SIA threat categories, see Threat categories.
Acceptable User Policy (AUP) or Application Visibility and Control (AVC) Violation
This message appears when a user violates the AUP or AVC settings in a policy. The message indicates which AUP or AVC category was violated. It also shows what URL was blocked.
If a file is blocked as a result of a DLP configuration, this message appears:
Error Warning
An error message similar to this one appears when SIA or SIA Proxy cannot connect to the requested website. This may occur in any of these situations:
-
Connectivity issue to the origin website.
-
TLS certificate issue. This includes cases where SIA Proxy cannot validate an origin certificate. If an SIA administrator chooses to block origin certificates that cannot be verified, this error page appears to the user.
-
Unknown user or group attempting to access a website.
The blocked URL is shown in the error page.
Depending on the situation, the error message may differ. For example, this error message appears when there is an issue with the TLS certificate:
The blocked URL is shown on the error page.
User Authentication Error
If authentication is enabled and configured in an acceptable use policy, this error message appears when a user enters invalid credentials to access a website.
The blocked URL is shown on the error page.
Error page customization
If you choose to use SIA error pages instead of an error that is hosted by your organization, you can modify these areas of the SIA error pages:
-
Logo. Area at the top-left of the page that is reserved for the logo image. You can upload an image in JPEG or PNG format.
-
Title. Title header of the page that indicates website access is prohibited. You can select the background color and the color of the text. You can also modify the font, font size, and style of the text.
-
Message Area. Area of the page that is reserved for:
-
The reason or cause of the error
-
The category associated with the error
-
A message and explanation
-
IT help desk contact information such as the email, phone, and the ticket URL
In this area of the page, you can:
-
Select a supported language or languages for the error message.
-
Select the default language for the error page. If the user’s browser is not set to one of the selected languages, the error page appears in the default language.
-
Modify the color, font, font size, and font style of the text that appears on the page.
-
Select a background color for the message.
-
Define the explanation text that describes why the error occurred or the violation was detected.
-
Provide text that describes who users should contact for assistance.
-
Enter the IT email address, phone number, and ticket URL.
-
Show or hide the IT email address, phone number, or ticket URL.
Many of these settings for customization are in limited availability. To try out these settings, contact your Akamai representative.
-
-
Window Background. Setting where you can select the background color of top and bottom of the page where no text is provided. You can also select whether you want to show the corner image.
Any modification you make to these areas impacts all error messages. For example, if you modify the font style of the message, the message in all of the error pages then uses the new font style.
Customize the SIA error pages
You can configure the appearance, language, and some of the text that appears for a SIA error page. An error page appears when a user attempts to go to a website that violates access control settings or is a known or suspected malware, phishing, or C&C communication security threat. Error pages appear for known or suspected domains that are configured in the policy with a Block action and the Error Page response. For details, see Error page customization.
Any modification that you make to an element or item of an error page is applied to all SIA error pages. For example, if you select a specific font for the message that is provided in an error page, all error pages use that font for the message.
To change the appearance of error pages:
-
In the Threat Protection menu of Enterprise Center, select Policies > Error Pages.
-
To define images for the logo or favicon, click Upload and locate the image that you want to upload for each element. The image that’s used for the favicon cannot exceed 10 KB, and the image for the logo cannot exceed 100 KB.
-
To define the Support information that appears in the error page, do the following:
- To show an email address, select Email and enter an email address in the provided field.
- To show a phone number, select Phone and enter a phone number in the provided field.
- To show a ticket URL, select Ticket URL and enter the URL in the provided field.
-
To customize the language that’s used in the error page, complete these steps.
- Click the Texts tab.
- Click the plus sign icon to add a language.
- In the dialog that appears, select the language or languages.
- Click Add.
- Select the language that you want to set as the primary language and enable the This is the primary language toggle.
-
To customize the text that explains the error and indicates who users should contact for assistance, complete these steps:
- In the Explanation field, enter text that explains why this error or violation was detected.
- In the Contact Reference field, enter text that describes who users should contact for further assistance.
You cannot modify text for the title, reason, and category areas of the error page.
-
To modify the appearance of the error page, complete these steps:
- Click the Color and fonts tab.
- Define the page background. You can upload an image or select a background color. If you upload an image, the image file cannot exceed 500 KB.
- For the page header (banner), select the background color, as well as the font color, font, font style, and font size.
- For the message modal, select the background color for the modal.
- For each area of the modal (reason, category, explanation, and contact reference), select the font color, font, font style, and font size of text.
- For the action buttons, select the button background color, the color of the button border, as well as the font, font color, font style, and font size for the button label.
-
Click Save.
Use a hosted error page
If your organization maintains its own error pages, you can choose to show users a hosted error page instead of SIA error pages. When you enable this feature, users are redirected to the hosted error page for all blocked websites.
To use a hosted error page:
-
In the Threat Protection navigation menu, select Policies > Error Pages.
-
Enable Self Hosted Error Page.
-
In the provided field for the host, enter the URL where your organization hosts the error page.
-
Click Save.
Parameters in an error page URL
While an error page indicates that access is denied to a website, the URL of the page also provides additional information to your users and help desk administrators. This information includes the error type, host or URI that the user attempted to access, the type of error that occurred, and more. These parameters are available in the URL of SIA error pages and in the URL of the error page that's hosted by your organization.
The parameters in the URL may look like this:
https://error.etp.akamai.com/error.html?lang=en_US&cust=<ID>&category=CONTROL&class=NO_AUTH&host=<www.example.com>&uri=&source=<IP_ADDRESS>&unauthenticated_reason=auth_declined
This error page URL includes the configuration ID, the specific threat category, domain that the user tried to access, the source IP address, and the reason why access was denied.
Depending on the error, these parameters may appear in the error page URL:
| Parameter | Description |
|---|---|
| lang | Language that's displayed for the error page |
| category | Shows the category that was blocked. One of these values may appear for this parameter:
|
| class | Values that show additional details about the category. When a category is THREAT, the class parameter value includes three numerical values (for example, &class=1-2-3), where the middle numerical value represents the specific category ID. The category ID maps to these threat categories:
When the category is either AUP or CONTROL, the class parameter provides more details on the reason for the block. If the value is a numeric ID, this is the specific AUP or access control category ID that caused the block action. For more information on these IDs, see AUP and Access Control Category IDs. If the category is ERROR, the error_type parameter will show the specific value. |
| error_type | Type of error that occurred. Possible values for this parameter include:
|
| code | If error_type information is provided, a code also appears with more specific information. Any one of these codes can appear:
|
| unauthenticated_reason | Indicates why an authentication failure occurred. Any of these reasons may appear:
|
| hashThatCausedBlock | The hash value of the file that was blocked. |
| host | Host that user attempted to access. |
| uri | URI that user attempted to access. |
AUP and Access Control Category IDs
In a class parameter (for example, &class=1-2-3) of an error page URL, the middle numerical value represents the specific category ID. These numerical values map to the category ID that’s associated with AUP and access control operation categories.
For more information on AUP categories, see Acceptable use policy categories.
| Numeric ID | AUP Category or Access Control Operation Category |
|---|---|
| 1 | Uploading |
| 2 | Downloading |
| 3 | Posting |
| 4 | Sharing |
| 5 | Editing |
| 6 | Viewing Contents |
| 7 | Chatting |
| 8 | File Transfer |
| 9 | Listening |
| 10 | Viewing Mail |
| 11 | Sending Mail |
| 12 | Sending Attachments |
| 13 | Calling |
| 14 | Searching |
| 15 | Login/Authentication |
| 16 | Alcohol/Tobacco |
| 17 | Broadcasting |
| 18 | Paying and Transferring Money |
| 19 | Inviting |
| 20 | File Sharing |
| 22 | Healthcare |
| 23 | Financing & Investing |
| 31 | Chat |
| 33 | Virtual Community |
| 34 | Forums & Message Boards |
| 35 | Blogging |
| 37 | Personals & Dating |
| 38 | Gore |
| 39 | Hate |
| 40 | Violence |
| 46 | Weapons Related |
| 47 | Lingerie |
| 49 | Nudism & Naturism |
| 50 | Hacking |
| 51 | Plagiarism |
| 52 | Criminal Skills |
| 53 | Peer to Peer |
| 54 | Anonymizers |
| 55 | Streaming Websites |
| 56 | Pornography Websites |
| 60 | Self Harm |
| 70 | Sex Education |
| 71 | Motor Vehicles |
| 72 | Real Estate |
| 73 | Business & Economy |
| 74 | Marijuana |
| 75 | Abortion |
| 76 | Kids |
| 77 | Military |
| 78 | Legal |
| 79 | Government |
| 80 | Travel |
| 81 | Entertainment & Arts |
| 82 | Local Information |
| 83 | Hunting & Fishing |
| 84 | Recreation & Hobbies |
| 85 | Music |
| 86 | Image & Video Search |
| 87 | Fashion & Beauty |
| 88 | News & Media |
| 89 | Political Advocacy |
| 90 | Cult & Occult |
| 91 | Religion |
| 92 | Training & Tools |
| 93 | Job Search |
| 94 | Translation |
| 95 | Reference & Research |
| 96 | Educational Institutes |
| 97 | Search Engines |
| 98 | Web Advertisements |
| 99 | Auctions |
| 100 | Shopping |
| 101 | Home & Garden |
| 102 | Online Greeting Cards |
| 103 | Computer & Internet Security |
| 104 | Computer & Internet Info |
| 105 | Keyloggers & Monitoring |
| 106 | Dead Sites |
| 107 | Shareware & Freeware |
| 108 | Pay to Surf |
| 109 | Internet Portals |
| 110 | Web-Based Email |
| 111 | Spyware & Adware |
| 112 | Content Delivery Networks |
| 113 | Confirmed Spam Sources |
| 114 | Spam URLs |
| 115 | Dynamic Content |
| 116 | Parked Domains |
| 117 | Web Hosting |
| 118 | DNS-over-HTTPS Providers |
| 119 | IT Services |
| 120 | Productivity and CRM Tools |
| 121 | Sales and Marketing |
| 122 | System & Development |
| 123 | Collaboration and Online Meetings |
| 124 | General Internet (News, Utilities, Misc) |
| 125 | Document Management |
| 127 | Individual Stock Advice & Tools |
| 128 | Child Abuse / Exploitation |
Enable HTTPS block pages for DNS only policies
Complete this procedure to show HTTPS block pages for web traffic when DNS Only is selected as the policy type. This page only appears in known locations. Users who make requests from unknown or unidentified locations cannot see the HTTPS block page.
Before you begin:
- If you haven’t done so already, make sure you create and distribute a proxy certificate. For more information, see Create a SIA Proxy MITM certificate.
- Make sure Transparent Traffic Interception is enabled for Zero Trust Client.
To enable HTTPS block pages for DNS only policies:
- In the Threat Protection menu of Enterprise Center, select Clients & Connectors > Connection Info.
- Turn on the toggle for Enable HTTPS block pages for DNS only policies.
- Click Save. If you want to save and deploy the policy, click Save and Deploy.
Next Steps:
If you haven’t deployed the policy, make sure you deploy it to the SIA network. For instructions, see Deploy configuration changes.
Updated 3 days ago
