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="175px,125px,300px"&rowsFixed=1&rowsVisible=10&float=center}}
^ Host ^ IP Address ^ Description ^
| dev-ws02.certna.org | 204.246.133.236 | APEX installation host. |
| apex-prd.certna.org | 204.246.133.237 | APEX production ERDS application servers. |
| apex-prd.certnag2g.org | 209.170.199.196 | APEX production G2G application servers. |
| reports.certna.org | 204.246.133.238 | APEX production ERDS report servers. |
| reports.certnag2g.org | 209.170.199.202 | APEX production G2G report servers. |
| *.digicert.com | * | DigiCert PKI certificate services. (Note 1) |
| <del>*.entrust.com</del> | * | <del>Entrust PKI certificate services. (Note 1) </del> |
| <del>*.entrust.net</del> | * | <del>Entrust Code Signing certificate services. (Note 1) </del> |
| *.ssl.com | * | SSL certificate services. (Note 1) |
| *.godaddy.com | * | SSL certificate services. (Note 1) |
| checkip.dyndns.org | * | Used by APEX to obtain public IP address of client. (Note 2) |

**Note 1:** 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.

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. (This is the least preferred.)

The preceding list is sorted in order of preference.

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 ^
| wiki.certna.org | 184.168.131.241 | CeRTNA's documentation portal. Listens on port 80 (http) |
| *.microsoft.com | * | Top-level Microsoft domain, to avoid issues with Windows functionality. |
| *.update.microsoft.com | * | General Windows update domain. |
| *.gotomeeting.com | * | Top-level domain for GoToMeeting web meeting. |
| *.goto.com | * | Top-level domain for GoTo web meeting. |
| *.citrixonline.com | * | GoToMeeting is implemented using Citrix servers. |

Configuring the firewall rules for Windows Updates and other fundamental OS support, for example, virus definition files for Symantec Endpoint Protection or other 3rd party anti-virus/anti-malware protection 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 accomodated beyond those that are required for APEX and/or CeRTNA functionality.

**Note 2:** Although APEX will function properly without knowing its public IP, allowing APEX to report the public IP of the client is very helpful in diagnostic and troubleshooting as it allows CeRTNA to identify the specific client traffic in our firewall. It preferred that you allow http://checkip.dyndns.org to be accessed from the ERDS or G2G workstation. Please note that the connection is made over the standard http port 80.

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