---
title: "Prostix Trade Portal External Access"
canonical: "https://kb.myframeworks.com.au/space/TPUG/28803222/Prostix%20Trade%20Portal%20External%20Access"
format: markdown
---
<span style="color: #222222">In order for the Prostix Trade Portal to be made publicly available via the internet, a number of security methods and the various implications need to be considered.</span>  
  
<span style="color: #222222">Ranked from most to least preferred, there are probably 3 common methods:</span>

| **Method** | **Description** |
| --- | --- |
| **VPN** | <span style="color: #222222">Using the VPN method requires a VPN server on the site hosting the Mobile Apps Web Server. This method is most secure, as it restricts access to the webserver, specifically to those users who can provide the user login credentials to the VPN server. Most modern PCs and mobile devices support VPN connectivity natively. This method allows the webserver to exist on the client's internal network natively without the need for complex firewall rules.</span> |
| **DMZ** | <span style="color: #222222">If the site maintains a separately configured DMZ network at or on the firewall gateway to the Internet, this method provides a secure disconnect between the webserver hosted on the DMZ network and the client's internal network. A set of firewall rules must be configured to allow specific port and protocol access between the webserver and the Prostix App Server. This method provides full public access to the webserver, with the username and passwords within the Prostix database providing authentication. It is also more complex in nature due to the requirement of firewall rules controlling access between the 2 components.</span> |
| **NAT** | <span style="color: #222222">This is the least preferred method, however unfortunately the most common connectivity method. In this method, the webserver typically sits on the client's internal production network, with a firewall rule to forward all traffic for mobile apps to the internal webserver. This method is the highest security risk as it provides full public Internet access to the webservice on a machine on the internal network.</span> |

> ✅ Refer to FAQ: [What are the considerations for making Sterland Mobile Apps publicly available?](https://sterkb.atlassian.net/wiki/pages/createpage.action?spaceKey=SAS&title=What%20are%20the%20considerations%20for%20making%20Sterland%20Mobile%20Apps%20publicly%20available%3F) for further information.

# Additional Information

> ✅ - Refer to the [Trade Portal FAQs](https://kb.myframeworks.com.au/space/TPF/720044037) to browse or search for a solution.
> ✅ - If you are still unable to find a solution, contact [Support](https://kb.myframeworks.com.au/page/support).