Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

ASA Configuration / Hiding Internal IP from DMZ

Posted on 2012-03-09
3
Medium Priority
?
437 Views
Last Modified: 2012-10-11
We have an ASA 5510 and we are trying to set up a new network segment that will function as a DMZ. We want requests to ports 25 and 443 to pass through the DMZ and then onto the internal network, which is connected through another interface. I am having trouble obfuscating the internal network segment from the DMZ. I don't want to give out any information about internal network addresses to the DMZ.

Let's say our DMZ address segment is 192.168.80.0/24 and our internal address segment is 192.168.240.0/24. I have successfully created rules that allow ports 25 and 443 from the outside into the DMZ and they route to the correct servers. Now, I'd like to be able to allow our DMZ servers to connect to obfuscated addresses (either fake addresses on the same network segment or ones that don't truly exist) instead of connecting directly to 192.168.240.X.

I do not entirely know if this is possible, but if you can generally describe without asking me to output my configuration, that would be preferable.

Thanks!
0
Comment
Question by:cculver
1 Comment
 
LVL 18

Accepted Solution

by:
max_the_king earned 2000 total points
ID: 37704939
Hi, you cannot do that but mostly it doesn't make sense.

Your servers sit in DMZ and are separated from internal LAN: this means that you are allowing access from outsdie (internet) on them without compromising internal servers and workstations (that's fine).

By default on ASA, DMZ hosts cannot communicate with hosts behind inside interface (that's fine again), while yous internal hosts can initiate communication towards DMZ hosts.

Now, if you need to open any socket (TCP/IP connection an any port) from DMZ to internal hosts you must apply a rule (access-list and correct "nat-routing") to allow this. That is how it is supposed to work and it is fine.
It is not a security hole, just a monitored rule that allows your users do their job. If a server in DMZ gets compromised, yes, theorically from there you might try and reach your internal hosts, but it can only happen through the rule (which you must know) you have applied.

hope this helps
Max
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Many of the companies I’ve worked with have embraced cloud solutions due to their desire to “get out of the datacenter business.” The ability to achieve better security and availability, and the speed with which they are able to deploy, is far grea…
WARNING:   If you follow the instructions here, you will wipe out your VTP and VLAN configurations.  Make sure you have backed up your switch!!! I recently had some issues with a few low-end Cisco routers (RV325) and I opened a case with Cisco TA…
Both in life and business – not all partnerships are created equal. Spend 30 short minutes with us to learn:   • Key questions to ask when considering a partnership to accelerate your business into the cloud • Pitfalls and mistakes other partners…
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…
Suggested Courses

564 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question