×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Your completely missing the point. Re-read again. BIND is just a common example, but Apache, WAS, FTP are also very common exploit points.
So your logic is still not living up to the intent of the PCI guidelines.
-----Original Message-----
From: Nathan Andelin [mailto:nandelin@xxxxxxxxx]
Sent: Tuesday, September 03, 2013 3:28 PM
To: Midrange Systems Technical Discussion
Subject: Re: iSeries public WEB access, PCI security issues
From: Matt Olson
So lets say you run BIND on your IBM i box, along with your WAS, your
FTP server, your DB2 database.
Let's say that we NOT run BIND under IBM i. Or, if we do, then NOT expose it to anyone except your own internal, trusted network. Keep it behind the Firewall. Keep it behind the DMZ.
Go ahead and use the entire Internet's DNS to route external requests to your Firewall, but don't map any external DNS traffic to an internal DNS server.
Do run HTTP/SMTP/FTP/Telnet and other secure TCP/IP servers, web application servers, and databases servers under IBM i, however.
-Nathan
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
