Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.
Cisco ASA 5200 ACL question
Folks,
We have an ASA 5200 which we may be using to provide firewall services for more than one client. With that in mind I went to great lengths and some pain to configure it using the minimum number of interfaces necessary for the existing client using subinterfaces of a single interface.
Behind the subinterfaces for this client we plan to have exchange, web, citrix and sundry other applications which will need access to the internet. I've fiddled with the static (int, int) command and have it functioning for the sub interfaces.
I then began to fiddle with configuring the ACL. Ideally I'd like to permit pretty much everything in through the outside interface then allow or block traffic at the subinterface level. I created two separate ACL's, one called Global_ACL the other called AWF_ACL. The Global_ACL had a permit ip any any statement in it and the AWF_ACL had the more granular permit statements.
I then applied the Global_ACL to the outside interface and the AWF_ACL to the subinterface which I needed traffic to pass on. I tested my connection using RDP remapped to a different port and was able to connect to the server behind the ASA.
I looked at the access-lists and saw hits on the Global_ACL but none on the AWF_ACL. Curious to see if the AWF_ACL was being parsed I then removed it from the subinterface and found that I could still connect via RDP.
My question is this: how can I configure the ASA so that I am allowing everything into the outside interface but only what port traffic I want into each sub interface?
I can post the relevant portion of the config if needed.
Thanks
We have an ASA 5200 which we may be using to provide firewall services for more than one client. With that in mind I went to great lengths and some pain to configure it using the minimum number of interfaces necessary for the existing client using subinterfaces of a single interface.
Behind the subinterfaces for this client we plan to have exchange, web, citrix and sundry other applications which will need access to the internet. I've fiddled with the static (int, int) command and have it functioning for the sub interfaces.
I then began to fiddle with configuring the ACL. Ideally I'd like to permit pretty much everything in through the outside interface then allow or block traffic at the subinterface level. I created two separate ACL's, one called Global_ACL the other called AWF_ACL. The Global_ACL had a permit ip any any statement in it and the AWF_ACL had the more granular permit statements.
I then applied the Global_ACL to the outside interface and the AWF_ACL to the subinterface which I needed traffic to pass on. I tested my connection using RDP remapped to a different port and was able to connect to the server behind the ASA.
I looked at the access-lists and saw hits on the Global_ACL but none on the AWF_ACL. Curious to see if the AWF_ACL was being parsed I then removed it from the subinterface and found that I could still connect via RDP.
My question is this: how can I configure the ASA so that I am allowing everything into the outside interface but only what port traffic I want into each sub interface?
I can post the relevant portion of the config if needed.
Thanks
Asked:
-
6
5
1 Solution
Thanks for the reply.
This is essentially what I have done: The Global_ACL has a permit ip any any statement and the AWF_ACL has more granular statements.
The ACL on the subinterface seems to have no effect. It's as though the ASA assumes the traffic is alright for any interface once it's matched the ACL on the outside interface.
I do appreciate the thoughts though!
This is essentially what I have done: The Global_ACL has a permit ip any any statement and the AWF_ACL has more granular statements.
The ACL on the subinterface seems to have no effect. It's as though the ASA assumes the traffic is alright for any interface once it's matched the ACL on the outside interface.
I do appreciate the thoughts though!
You can now apply acls "out" on each interface.
Allow all/most "in" on the outside interface.
Restrict "out" on the vlan interfaces
Example:
access-list inbound permit ip any any
access-group inbound in interface outside
access-list to_vlan1 permit tcp any eq www any
access-list to_vlan1 permit udp any eq domain any
access-list to_vlan1 permit tcp any any eq https any
access-group to_vlan1 out interface vlan1
access-list to_vlan2 permit tcp any host a.b.c.d eq www
access-list to_vlan2 permit tcp any host a.b.c.d eq https
access-list to_vlan2 permit tcp any host alb.c.e eq smtp
access-group to_vlan2 out interface vlan2
Allow all/most "in" on the outside interface.
Restrict "out" on the vlan interfaces
Example:
access-list inbound permit ip any any
access-group inbound in interface outside
access-list to_vlan1 permit tcp any eq www any
access-list to_vlan1 permit udp any eq domain any
access-list to_vlan1 permit tcp any any eq https any
access-group to_vlan1 out interface vlan1
access-list to_vlan2 permit tcp any host a.b.c.d eq www
access-list to_vlan2 permit tcp any host a.b.c.d eq https
access-list to_vlan2 permit tcp any host alb.c.e eq smtp
access-group to_vlan2 out interface vlan2
I'll test this but looking at it wouldn't this restrict traffic outbound from inside the interface?
I'm trying to wrap my brain around how this would work...
I'm trying to wrap my brain around how this would work...
oh... wait... I think I see what you're saying.
So, If I have the following interfaces:
gig0/1
gig0/1.10
gig0/1.20
and I create an ACL which permits all IP traffic and apply it on gi0/1 inbound
then I create an ACL which restricts traffic and apply it to gi0/1.10 outbound
the result should be that all traffic flows into the primary interface but is restricted flowing through it to the sub-interface?
So, If I have the following interfaces:
gig0/1
gig0/1.10
gig0/1.20
and I create an ACL which permits all IP traffic and apply it on gi0/1 inbound
then I create an ACL which restricts traffic and apply it to gi0/1.10 outbound
the result should be that all traffic flows into the primary interface but is restricted flowing through it to the sub-interface?
No. Think of the ASA as a big box with multiple doors.
From the outside of the box, all doors say "IN"
From the inside of the box, all doors say "OUT"
packets can come in the outside interface, but can't go out the vlan interface
In the example above, "inside" and vlan3 can use FTP, RDP, etc, while users on vlan1 and 2 are restricted to http, https, dns, smtp, etc
These are just examples. Be careful what you wish for and plan it very carefully and don't forget about udp/53 for dns
From the outside of the box, all doors say "IN"
From the inside of the box, all doors say "OUT"
packets can come in the outside interface, but can't go out the vlan interface
In the example above, "inside" and vlan3 can use FTP, RDP, etc, while users on vlan1 and 2 are restricted to http, https, dns, smtp, etc
These are just examples. Be careful what you wish for and plan it very carefully and don't forget about udp/53 for dns
No/Yes.
No to your question "wouldn't this restrict traffic outbound from inside the interface? "
Yes to your last post. We must have cross-posted at the same time.
No to your question "wouldn't this restrict traffic outbound from inside the interface? "
Yes to your last post. We must have cross-posted at the same time.
lrmoore:
Thanks for the replies. So I understand correctly I described applying the ACL's correctly to achieve what I wish to accomplish, correct?
Thanks for the replies. So I understand correctly I described applying the ACL's correctly to achieve what I wish to accomplish, correct?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
the only thing i can thik of is to add an access list that opens everything up and bind it to the outside interface, then add your neccessary access-lists to block what you want on the sub interfaces
access-list inbound permit ip any any
access-group inbound in interface outside
this will open up the device with basically no security. then add you acl's for the subs