DokuWiki

You've loaded an old revision of the document! If you save it, you will create a new version with this data.

==== Firewall Settings ====

APEX communicates using SSL port 443 (https) and some communications take place using port 80 (http). The following table contains a list of hosts that must be reachable in order for APEX to be installed or be used after the installation:

{{tablelayout?colwidth="335px,125px,225px"&float=center}}
^ Host ^ IP Address ^ Description ^
| dev-ws02.certna.org | 204.246.133.236 | APEX installation |
| apex-setup.certna.org | 204.246.133.236 | APEX installation |
| apex-prd.certna.org | 204.246.133.237 | APEX production ERDS web|
| apex-prd.certnag2g.org | 209.170.199.196 | APEX production G2G web|
| reports.certna.org | 204.246.133.238 | APEX production ERDS reports|
| reports.certnag2g.org | 209.170.199.202 | APEX production G2G reports|
| *.digicert.com | * | PKI certificates (Note 2) |
| *.ssl.com | * | Code Signing certificate (Note 2) |
| *.godaddy.com | * | SSL certificates (Note 2) |

CeRTNA no longer interfaces with Entrust, therefore, the references to *.entrust.com and *.entrust.net shown above have been stricken out.

**Note 1:** CeRTNA recognizes that different firewalls are in service at our customers and that firewall features functions can vary broadly. CeRTNA prefers to minimize the amount of IT administrative support required by creating rules based on the following tolerance and/or capabilities of your firewall:

- Use wildcard domains if possible. (Ex: *.certna.org or *.certnag2g.org)
  - Use host names if possible. (Ex: apex-prd.certna.org or reports.certna.org)
  - Last resort, use IP addresses.

The preceding list is sorted in order of preference.

**Note 2:** Several digital certificates are used in support of CeRTNA/APEX, these include SSL certificates, PKI certificates for digital signatures, PKI certificates for encryption/decryption, and code-signing certificates. The CeRTNA APEX application uses core WCF & .NET functionality to verify that the PKI certifcates are still valid and have not expired. Further, during the APEX installation/update process, the code-signing certificate is validated. The lower level WCF & .NET API's communicate using port 80 for OCSP and CRL certificate validation functions. It is important that your firewall team take this into consideration.

=== Workstation Support ===

In addition to the locations listed above, there are some additional hosts that you also want to allow in order to facilitate the retrieval of Windows Updates and for CeRTNA remote support.

{{tablelayout?colwidth="175px,125px,300px"&rowsFixed=1&rowsVisible=10&float=center}}
^ Host ^ IP Address ^ Description ^
| *.microsoft.com | * | Top-level Microsoft domain, to avoid issues with Windows functionality. (Note 3)|
| *.update.microsoft.com | * | General Windows update domain. |

Configuring the firewall rules for Windows Updates and other fundamental OS support, for example, virus definition files for Endpoint Protection or other 3rd party system management tools is the responsibility of your organizations IT staff. The information provided in the preceding table is here simply point out that there are additional URL's that may need to be accommodated beyond those that are required for APEX and/or CeRTNA functionality.

**Note 3:** Support for Teams meetings and screensharing is also required for remote support of the APEX software.

Edit summary

Note: By editing this page you agree to license your content under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International