In light of the recent viruses/worms that have have shown up on our network, the administrator in charge of our two Unix servers wants to restrict access as to who can get to the servers via what protocols, but he doesn’t want to put that overhead on his servers. Our group has been talking about access lists on the Cisco router vs. putting up a second firewall in front of just the Unix servers. Which would be the best way to go? – Via the InternetIn light of the recent viruses/worms that have have shown up on our network, the administrator in charge of our two Unix servers wants to restrict access as to who can get to the servers via what protocols, but he doesn’t want to put that overhead on his servers. Our group has been talking about access lists on the Cisco router vs. putting up a second firewall in front of just the Unix servers. Which would be the best way to go?– Via the InternetThe answer depends on how much protection you want to provide for the servers. Using access control lists will control what protocols and/or ports can be used to get to the servers, but nothing else. You won’t have any logging as to when someone is trying to spoof an address or send a malformed packet, for example. This is an easy way to control access to servers but it does have its limits. Using an interior firewall gives you the logging that using just access rules may not be able to. You may be able to use syslog to send the alerts/errors back to a central console so you don’t have to check the firewall to see if someone has been doing something they shouldn’t. The next question is whether to use the same vendor’s firewall for your exterior firewall or use a different vendor’s product. What you need to consider is the ease of administration when you use the same vendor’s product for both firewalls vs. potential additional safety by using different vendors’ products matched against having to learn yet another firewall product. One of the arguments I have heard is if you use different vendors’ products for the firewall, if the first firewall gets compromised, the work to get past the second firewall will make them start all over since it is on a different platform and, theoretically, won’t have the same “vulnerabilities” as the first firewall. Either way, make sure you’re running the latest firmware for the routers to help this be an issue regardless of the vendor(s) you choose for the firewall(s). Related content news analysis Cisco joins $10M funding round for Aviz Networks' enterprise SONiC drive Investment news follows a partnership between the vendors aimed at delivering an enterprise-grade SONiC offering for customers interested in the open-source network operating system. By Michael Cooney Dec 01, 2023 3 mins Network Management Software Industry Networking news Cisco CCNA and AWS cloud networking rank among highest paying IT certifications Cloud expertise and security know-how remain critical in building today’s networks, and these skills pay top dollar, according to Skillsoft’s annual ranking of the most valuable IT certifications. Demand for talent continues to outweigh s By Denise Dubie Nov 30, 2023 7 mins Certifications Network Security Networking news Mainframe modernization gets a boost from Kyndryl, AWS collaboration Kyndryl and AWS have expanded their partnership to help enterprise customers simplify and accelerate their mainframe modernization initiatives. By Michael Cooney Nov 30, 2023 4 mins Mainframes Cloud Computing Data Center news AWS and Nvidia partner on Project Ceiba, a GPU-powered AI supercomputer The companies are extending their AI partnership, and one key initiative is a supercomputer that will be integrated with AWS services and used by Nvidia’s own R&D teams. By Andy Patrizio Nov 30, 2023 3 mins CPUs and Processors Generative AI Supercomputers Podcasts Videos Resources Events NEWSLETTERS Newsletter Promo Module Test Description for newsletter promo module. Please enter a valid email address Subscribe