# Configure your applications

## Add a new domain

On the left side menu, click on ***Sites >> Domains***.

Once inside click in:

<div align="left"><img src="https://3407554211-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lc6SmWC2XaTk3mzBSlS%2F-Lc76ZAGg83M7B1vvwnS%2F-Lc76vfpwwVJR6xVVs83%2Fimage.png?alt=media&#x26;token=daeac032-dc55-484a-8a6c-9683c0213d4a" alt=""></div>

And you will see a form to enter a new domain name.

![Image 1: Domains management page](https://3407554211-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lc6SmWC2XaTk3mzBSlS%2F-Lc76ZAGg83M7B1vvwnS%2F-Lc784f3qk8xgC96MUEz%2Fimage.png?alt=media\&token=0b386da6-d7e9-482a-9513-fe45788a9fed)

## Add a new subdomain

In the section ***Sites >> Domains*** you can add a new subdomain to a previously registered domain. Press the next button:

<div align="left"><img src="https://3407554211-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lc6SmWC2XaTk3mzBSlS%2F-Lc76ZAGg83M7B1vvwnS%2F-Lc78Muy7aLEIetqpQa9%2Fimage.png?alt=media&#x26;token=b6c1f6bc-60b3-4ee1-88cb-6f3364487e6d" alt=""></div>

And once pressed press the next button:

<div align="left"><img src="https://3407554211-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lc6SmWC2XaTk3mzBSlS%2F-Lc76ZAGg83M7B1vvwnS%2F-Lc78ZxDzagjtFJYYYTa%2Fimage.png?alt=media&#x26;token=b3281fa7-9f55-4fb3-9b59-e04cfe94771f" alt=""></div>

![Image 2: New subdomain form](https://3407554211-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lc6SmWC2XaTk3mzBSlS%2F-Lc76ZAGg83M7B1vvwnS%2F-Lc78gQRI0IKuA6aL5PK%2Fimage.png?alt=media\&token=25620c1b-6ba1-4050-bc18-313580c5abc9)

The process will consist in 6 simple steps to configure all the necessary information to protect your web application with *SecureAccess® CLOUD*:

* In the first step we will be asked to point the *DNS* of the resource to our secure server ***my.secureaccess.com***<br>
* In the second step you must enter general data about your subdomain, like description, name and communication protocol (*HTTP/HTTPS*).<br>
* In the third step you need to add the IP address of your server. You can add more than one and *SecureAccess® CLOUD* will act as a load balancer. <br>
* Fourth step will allow you to create a list of whitelisted IP address, request coming from this address will skip authentication process for this subdomain. \
  \
  **This will disable the access control mechanism, so use it carefully**.  <br>
* In the fifth step allow you to upload your own *SSL* certificate for the HTTPS communication. In case you don´t have one, *SecureAccess® CLOUD* can generate one for you. To use this option, you must first point your subdomain *DNS* to our reverse proxy (***my.secureaccess.com***). In a few seconds your new certificate will be generated and ready to use.  Select the option that fits you better and click on Next. <br>
* Last step gives you the opportunity of enabling *SecureAccess® WAF* (*Web Application Firewall*), which will analyze all the requests going through the platform blocking the ones containing malicious content. This will help in the prevention of *SQL injection* or *XSS* attacks. As an administrator you will receive notifications and alerts when a request is deemed suspicious and therefore blocked. 

Once all steps are done, you can press:

<div align="left"><img src="https://3407554211-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lc6SmWC2XaTk3mzBSlS%2F-Lc76ZAGg83M7B1vvwnS%2F-Lc792aU3mI9BXfRiChC%2Fimage.png?alt=media&#x26;token=b742b5e8-046b-40c2-b5d1-3c51728b452d" alt=""></div>

And your subdomain will be registered and enabled.
