# Remote access VPN - L2L VPN outside interface with access list
**URL:** https://forum.networklessons.com/t/remote-access-vpn-l2l-vpn-outside-interface-with-access-list/14773
**Category:** ASA
**Created:** [June 28, 2021, 4:17pm UTC](https://forum.networklessons.com/t/remote-access-vpn-l2l-vpn-outside-interface-with-access-list/14773 "2021-06-28T16:17:46Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@phenlerx](https://forum.networklessons.com/u/phenlerx)
#### Post date: [June 28, 2021, 4:17pm UTC](https://forum.networklessons.com/t/remote-access-vpn-l2l-vpn-outside-interface-with-access-list/14773/1 "2021-06-28T16:17:46Z")
On the ASA is an ACL necessary in order for remote access or L2L tunnels to land on the outside interface?
---
### Author:  [@lagapidis](https://forum.networklessons.com/u/lagapidis)
#### Post date: [June 30, 2021, 5:54am UTC](https://forum.networklessons.com/t/remote-access-vpn-l2l-vpn-outside-interface-with-access-list/14773/2 "2021-06-30T05:54:25Z")
Hello Phen
In order to allow access from outside to inside on an ASA, you must have an access list that allows this communication. The access list acts as an exception to the security levels configured, where communication from the outside interface to the inside interface is not allowed.
However, when creating a VPN such as that described in the ASA Site to Site IKEv1 IPSec VPN lesson below, you don’t need to specify such an access list.
> **[Cisco ASA Site-to-Site IKEv1 IPsec VPN](https://networklessons.com/cisco/asa-firewall/cisco-asa-site-site-ikev1-ipsec-vpn)**
>
> This lesson explains how to configure and the verification of Site-to-Site IKEv1 IPsec VPN on the Cisco ASA Firewall.
As you can see from the lesson, the configuration of the crypto map specifies the interface that is to be used. That is enough to enable communication using the VPN tunnel without the need to specifically define an access list on the outside interface.
I hope this has been helpful!
Laz