> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ras-secure-gateway/configuring-a-ras-secure-gateway/secure-gateway-security.md).

# Secure Gateway security

You can allow or deny user access to a Secure Gateway based on a MAC address. This can be accomplished using the **Security** tab in the **RAS Secure Gateway Properties** dialog.

### **Using Site defaults**

To use Site default settings, click the **Inherit default settings** option. To specify your own settings, clear the option. For more info, see [**Site defaults (Gateways)**](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ras-secure-gateway/configuring-a-ras-secure-gateway/site-defaults-secure-gateways.md).

### **Configuring security**

#### **Access Control**

Here, an administrator can restrict the usage of the Secure Gateway to specific modes of operation. For example, to enable the exclusive use of the Connection Broker API for user connections, but not the use of the User Portal directly.

The options available are:

* **Block access to standard RAS sessions.** Blocks new authentication to standard RAS sessions, preventing application listing and remote session launch. Existing sessions are not affected.
* **Block access to User Portal sign in page.** Blocks access to the User Portal user interface, including portal login and related pages such as cookie policy and download. Other APIs may still be used.
* **Block access to sessions via Web API.** Blocks new session launch through the Web API. Existing sessions are not affected.
* **Block access to deprecated Web API.** Blocks deprecated Web APIs to reduce security and compatibility risks. This option is ON by default for new installations as well as upgrades. If the option “Block access to sessions via Web API” is enabled, this option is automatically enforced.
* **Block access to sessions via Connection Broker API.** Blocks new session launch through the [Connection Broker API](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ras-connection-broker/enabling-connection-broker-api.md). Existing sessions are not affected.

#### **MAC Address Filtering**

To configure a list of allowed or denied MAC addresses, click the **Configure button** and select one of the following options:

* **Allow all except.** All devices on the network will be allowed to connect to the Secure Gateway except those included in this list. Click **Tasks** > **Add** to select a device or to specify a MAC address.
* **Allow only**. Only the devices with the MAC addresses included in the list are allowed to connect to the Secure Gateway. Click **Tasks** > **Add** to select a device or to specify a MAC address.

Please note that the Secure Gateway MAC address filtering is based on ARP, so the client and server must be on the same network for the filtering to work. It does not work across network boundaries.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ras-secure-gateway/configuring-a-ras-secure-gateway/secure-gateway-security.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.