Network Security

Networks

VoipNow Managed Firewall

VoipNow does not manage security. While it does its best to protect on the application stack level, it cannot guess your network topology and it cannot manage firewalls.

For convenience we included a node level firewall that is designed to help you deploy a basic network firewall on the host level.

A firewall installer is available on each VoipNow node. It will automatically detect the roles running on your node roles and apply only the corresponding access rules. Furthermore, it also contains a built-in safety feature to ensure you don't lose access to your server.

Installation

Trust some networks (optional)

You can always fully trust some networks. The installed firewall will never perform filtering for them (in/out).

Edit /etc/voipnow/local.conf and uncomment the TRUSTED_NET variable, replacing its value with your local network IP and netmask:

Apply firewall (test mode)

Execute the following command:

• save your existing firewall rules into a temporary file ( /tmp/iptables.20463 in the above example)
• inspect the VoipNow Cloud Management for roles assigned to this role
• attempt to detect ports used by each role and apply the corresponding firewall rules
• install a "SafetyNet" consisting of a cron job which does a firewall flush after 3 minutes

You can see this safety net as a line in crontab:

Apply firewall (final mode)

Assuming that everything is ok, run the firewall script again with the ok parameter (this will remove the cron job and leave your newly generated firewall rules in place):

Private Network

The private network must be isolated. Only VoipNow nodes must be able to access it - it should not be shared with any other system. Furthermore, generic host level network firewalls must be configured to allow connection only on the ports that are opened on each role.

Public Network

The public network must be protected with firewalls. Connections must be allowed only on the ports configured to be accessed by customers' devices.

The sections below offer several recommendations on how to set up firewalls based on the role of the node.

Role Network Filtering

Functionaly Layer

Web Management Interface

Requires public network access, as well as private network access for management and database traffic. Traffic is encrypted; both private and public networks are required. Supports authentication and authorization methods. Could be protected with an application level firewall.

SIP

Requires public network access, as well as private network access for management and database traffic. Traffic can be encrypted with TLS as long as involved parties support this protocol otherwise its not encrypted; both private and public networks are required. Supports authentication and authorization methods. Could be protected with an application level firewall.

PBX

Requires public network access, as well as private network access for management and database traffic. Traffic can be encrypted (SRTP) as long as involved parties support the protocol otherwise traffic not encrypted; both private and public networks are required. Supports authentication and authorization methods.

Infrastructure Management

Infrastructure Controller

Requires private network access. Traffic is encrypted.

Worker

Task scheduler that does not listen on any port but requires private network access to connect to other roles.

Storage Layer

SQL

Traffic must be kept in the private network. Traffic is not encrypted; connection is made using authentication.

Distributed Database

Traffic must be kept in the private network. Traffic is not encrypted; connection is authenticated, but some basic operations to the database are possible without credentials.

Elasticsearch

Traffic must be kept in the private network. Traffic is not encrypted; connection is authenticated.

Amazon S3

Traffic is on the public network and is encrypted, connection is authenticated.