How to secure Virtual Office portal from all external access

12/22/2021 8 People found this article helpful 5,197 Views

Download

Print

Share

• LinkedIn
• Twitter
• Facebook
• Email
• Copy URL The link has been copied to clipboard

Description

CAUTION: Before proceeding Please Export Settings Configuration

NOTE: Due to some changes may have you change or add another physical interface or change on your local network host

Please be onsite with settings before proceeding.

There are two ways of Securing the Virtual Office to be seen from External Access

Option1:

• Simply edit portal your using for Users (Thats not Virtual Office) or add one new for users.
• Under Add Portals | portal | General
• Edit these fields: Portal Name, Portal Site Title , and Portal Banner Title

 EXAMPLE: CompanyNameUsers or Vendors or ....

• Now under Virtual Host Tab, Give Hostname based on your domain like example: vpn.domain.com
• Then change Virtual Host Interface from ALL Interfaces to X0 (or the interface you want to use)
• Edit Virtual Host IP Address to you new IP nomaly Ip address form same subnet as your SMA Appliance IP.

EXAMPLE:  SMA X0 is 192.168.200.1 and the Default GateWay is 192.168.200.2  So, the custom ip would be 192.168.200.3
Then change you firewall Nat policy to new custom address IP you created.
Submit/Save Changes

• Next navigate to  Portals | Domains | Edit Users Domain
• Then make sure Portal name: [ Box has correct Portal ] Remove virtual Office from it.

Summation: this will keep ip of sma not part of the indound Nat policy so virtual office is not seen publicly
NOTE: This has an Limitation only one portal with unquie internal ip to one public ip

Option 2:
 Secures the Virtual Office Portal from All External Access. However For Many Portal names you want attached to single public IP. You will need to do Second way of Securing Virtual Office from External Access

• Add new interface under Networks | Interfaces 
• Edit X1 Interface to your new virtual office admin network you wish to use

NOTE: (if using x1 then use another interface that is Available)

• Once added make sure that cable plugged in to network and make it visible on its own separate IP network range

TIP: For physical SMA device create new zone and network on another firewall interface for you new SMA interface connect cables

(if any issues set up please check with our firewall team or your 3rd party firewall support)

TIP: For virtual SMA device create new virtual switch tied to another separate physical interface of you virtual host server or create vlan to separate that
(if any issues set up please check your 3rd party virtual server support)

• Add New Portal for Users If not already done 

• Under Add Portals | portal | General
• Edit these fields: Portal Name, Portal Site Title , and Portal Banner Title

EXAMPLE: CompanyNameUsers or Vendors or ....

• Next Under Portals | portal | Edit existing portal or Add one | Virtual Host
• Edit Virtual Host Domain Name: example vpn.companyname.com 

NOTE: This is Hostname assigned to public ip of you SMA by global DNS tied to your company.com name  

• Now edit All Interfaces change to X0 or ( if thats the interface you use for your users / NAT policy ip )
• Add IP address you want for that portal 

CAUTION:  Make Sure you have access to other SMA Interface IP before proceeding

• Click OK will get warning box similar below and hit OK 

CAUTION: This change will disconnect active Users and Restart device is Suggested

• Next You may receive 2nd Warning Message Portal IP change click OK

• Now you successfully secured your administration portal ( Virtual Office ) to only be seen on internal ip addresses

CAUTION: Be Onsite with SMA do your  

that you may still need to do outside of this sma configuration. 

TIP:  you may need to make further adjustments on virtual SMA's to see both networks internally thru the virtual host or cloud provider 

If traffic does not flow check your firewall/router access rules and NAT policies for each sma internal ip you have

if many user portals give each separate ip then create group object in firewall set all of them to same public ip this may have you create a few NAT policy's for each or an group NAT.

**remember each user portal needs DNS Hostname created and posted publicly with your dns service provider**

Related Articles

• NetExtender users fail to get connected throwing an Error Failed to get vpn protocol on firmware 10.2.1.2 or above due to misconfigured protocol
• Is SRA/SMA appliance vulnerable to CVE-2016-2183 and CVE-2016-5915?

Categories

• Secure Mobile Access > SMA 100 Series
• Secure Mobile Access > SMA 100 Series > Configuration
• Secure Mobile Access > SMA 100 Series > Portals