secure to place an internal server with access to one Internet destination in non-DMZ ?

Network zones are segregated such that DMZ hosts internet-facing servers while internal/secure zone are for servers that don't need access to Internet.

Q1:
What about servers that are only permitted access to one IP out there in the Internet, say for SMS purposes or sftp, is it Ok to place such server in the
internal/secure zone

Q2:
if a test/development server is permitted for outgoing to one Internet destination only, is it considered insecure to place it in the internal (non-DMZ) zone?
sunhuxAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

masnrockCommented:
Q1: What about servers that are only permitted access to one IP out there in the Internet, say for SMS purposes or sftp, is it Ok to place such server in the internal/secure zone
You could define a separate VLAN that's properly secured (limiting access as appropriate), and that would work just fine. Do any systems on the outside need to connect to it?

Q2: if a test/development server is permitted for outgoing to one Internet destination only, is it considered insecure to place it in the internal (non-DMZ) zone?
All in context. Do outside systems connect to this server? If not, you're not introducing any serious risk. But the ideal would be to have a VLAN for test systems. But this also partly depends on what that server needs to interact with.

Note in both of these, I never said anything about using a DMZ, because based on the information provided, you would have no reason for one.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sunhuxAuthor Commented:
Q1 & Q2:
>Do any systems on the outside need to connect to it?
Yes.  Only 1 external site (which is our vendor) connects to our internal server.
Historically  it was permitted / set up as such years ago so we are now trying to change this ie get the system owners
to migrate to DMZ but was asked to justify.  To move the existing servers to a separate VLan by itself involves changing
of IP address & as much effort as moving them to DMZ, so if really need to move, might as well move to DMZ rather
than now creating another VLAN.

Appreciate if anyone can point me to some authoritative sites/links on this
masnrockCommented:
I would agree with your comment. There is nothing wrong with moving the systems to a DMZ either.

I assume that the system sits on a corporate LAN right now. Your justification would extend more out of protection of the corporate network than anything else.
sunhuxAuthor Commented:
>I assume that the system sits on a corporate LAN
Just learnt that in that Developmt corporate LAN, there was previously no DMZ : all servers in a single internal LAN & DMZ was set up about 1 year back (that was before I joined) but everyone just ignored it after a while.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.