Example: Web Application

Let's say your business generates revenue from a web application that has a portal for public access and a portal for administrative access. The public portal (172.16.1.1) runs on a web server that is located in your DMZ network, and the administration portal (10.10.10.3) runs on a web server that is located in your internal network. Both web servers send queries to a database server (192.168.1.1) that is located in a separate internal segment of your network.

In order to create the firewall rules to allow traffic for this application, you need to add rules to two different firewalls. After you do that, you still need to monitor the rules to make sure that no changes in the firewalls disrupt the traffic for the application. Because this web application is the core of your business, you cannot afford to have any downtime.

With SecureApp, you can build this connection with the information that you know about the application.

When you integrate with SecureChange, then you can create a SecureChange ticket that includes all of the information that the network and security teams need to approve and implement the changes.

SecureApp sends you a notification if there is any disruption to this traffic so you can correct it immediately.