Return-Path: <sentto-279987-4484-1013874756-fc=all.net@returns.groups.yahoo.com> Delivered-To: fc@all.net Received: from 204.181.12.215 [204.181.12.215] by localhost with POP3 (fetchmail-5.7.4) for fc@localhost (single-drop); Sat, 16 Feb 2002 07:54:08 -0800 (PST) Received: (qmail 9248 invoked by uid 510); 16 Feb 2002 15:52:48 -0000 Received: from n15.groups.yahoo.com (216.115.96.65) by all.net with SMTP; 16 Feb 2002 15:52:48 -0000 X-eGroups-Return: sentto-279987-4484-1013874756-fc=all.net@returns.groups.yahoo.com Received: from [216.115.97.165] by n15.groups.yahoo.com with NNFMP; 16 Feb 2002 15:51:53 -0000 X-Sender: fc@red.all.net X-Apparently-To: iwar@onelist.com Received: (EGP: mail-8_0_2); 16 Feb 2002 15:52:36 -0000 Received: (qmail 82527 invoked from network); 16 Feb 2002 15:52:35 -0000 Received: from unknown (216.115.97.171) by m11.grp.snv.yahoo.com with QMQP; 16 Feb 2002 15:52:35 -0000 Received: from unknown (HELO red.all.net) (12.232.72.152) by mta3.grp.snv.yahoo.com with SMTP; 16 Feb 2002 15:52:35 -0000 Received: (from fc@localhost) by red.all.net (8.11.2/8.11.2) id g1GFqeH21027 for iwar@onelist.com; Sat, 16 Feb 2002 07:52:40 -0800 Message-Id: <200202161552.g1GFqeH21027@red.all.net> To: iwar@onelist.com (Information Warfare Mailing List) Organization: I'm not allowed to say X-Mailer: don't even ask X-Mailer: ELM [version 2.5 PL3] From: Fred Cohen <fc@all.net> X-Yahoo-Profile: fcallnet Mailing-List: list iwar@yahoogroups.com; contact iwar-owner@yahoogroups.com Delivered-To: mailing list iwar@yahoogroups.com Precedence: bulk List-Unsubscribe: <mailto:iwar-unsubscribe@yahoogroups.com> Date: Sat, 16 Feb 2002 07:52:40 -0800 (PST) Subject: [iwar] [fc:SNMP.Threat.Shows.Why..IT.Can't.Afford.to.Be.Shortsighted] Reply-To: iwar@yahoogroups.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit SNMP Threat Shows Why IT Can't Afford to Be Shortsighted By Cameron Sturdevant, EWeek, 2/14/02 www.eweek.com A network security audit should be near the top of IT managers' list of things to do since Tuesday's disclosure of the existence of a test tool that, when used maliciously, can overcome SNMPv1 (Simple Network Management Protocol, version 1) in a wide variety of caching devices, routers, switches, printers and a myriad of other infrastructure devices. Instead of making the security audit the first step in a remediation plan, eWEEK Labs recommends that IT managers take this occasion to put together a plan that enables ongoing management of the wide range of devices that are threatened. A security audit is a good opportunity to manage devices with both short-term and long-term perspectives to reduce IT costs and improve business processes. The short-term response to the current threat is to apply the specific patch for SNMP 1. For the long term, IT departments should systematically upgrade their operating systems. Over the past several months, eWEEK Labs has advocated simplifying networks, systems and applications to improve security. In this case, SNMP commonly uses TCP ports 161 and 162, 191 (both TCP and UDP) along with three or four others. A good fix is to use a port scan tool to see if these ports are open. Next determine if the processes supported by these ports are needed. If yes, leave them open, but monitor their use. If no, consider turning them off. This is a great example of a short-term solution. Combined with a quick check of the equipment vendor's Web site for a patch to the SNMP code, managers should be able to make the equipment as good as gold. Now repeat for 3,000 or 4,000 devices. This is where the long-term management strategy must come into play. Designing a security audit that goes beyond simply locating equipment and determining operating system versions is essential for this type of project in order to reduce IT operational costs. In the case of the SNMP attack, eWEEK Labs advises that IT managers take the time to do the project right. Although reports show that the tool, designed by the Oulu University Secure Programming Group, is likely circulating underground, many SNMP-equipped devices are obsolete and are no longer supported by their manufacturers. Thus, a plan that combines shielding the network from SNMP probes while locating affected devices and installing updated software images is both urgent and massive. Putting plans in place to track and update software versions on these devices—not just fixing the current problem—is an essential step for IT to proactively strengthen network security. ------------------------ Yahoo! Groups Sponsor ---------------------~--> Sponsored by VeriSign - The Value of Trust When building an e-commerce site, you want to start with a secure foundation. Learn how with VeriSign's FREE Guide. http://us.click.yahoo.com/oCuuSA/XdiDAA/yigFAA/kgFolB/TM ---------------------------------------------------------------------~-> ------------------ http://all.net/ Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
This archive was generated by hypermail 2.1.2 : 2002-12-31 02:15:03 PST