Intrusion Detection Systems mailing list archives
Request for IDS Interoperability Information
From: "Woodall, Chuck" <woodallc () fhu disa mil>
Date: Tue, 19 Sep 2000 08:56:42 -0700
Archive: http://msgs.securepoint.com/ids FAQ: http://www.ticm.com/kb/faq/idsfaq.html IDS: http://www-rnks.informatik.tu-cottbus.de/~sobirey/ids.html HELP: Having problems... email questions to ids-owner () uow edu au NOTE: Remove this section from reply msgs otherwise the msg will bounce. SPAM: DO NOT send unsolicted mail to this list. UNSUBSCRIBE: email "unsubscribe ids" to majordomo () uow edu au ----------------------------------------------------------------------------- We at the Joint Interoperability Test Command (JITC) at Fort Huachuca, Arizona have several IDS under test in our Information Assurance Lab. See JITC at http://jitc.fhu.disa.mil/ and IA Lab at http://jitc.fhu.disa.mil/brochure/ia.pdf. The IDS under test are: THREE FIREWALLS: New Technology (NT) 4.0 Network Associates Gauntlet ver 5.0/5.5, Secure Operating System Secure Computing Corporation Sidewinder ver 4.1.0.07, and NT 4.0 AXENT Raptor ver 6.0; and FOUR SECURITY TOOLS: Internet Security Scanner (ISS) ver 6.0.1, ISS RealSecure ver 3.2.1 Engine and Management Console/System Agent, ISS SafeSuite Decisions ver 2.0 and its Structured Query Language (SQL) Server ver 7.0. During our Interoperability Test Phase of these IDS, we are trying to collect real operational data on interoperability (IOP) issues/problems (technical and non-technical) that have evidenced themselves during operational use (or performance issues that might affect IOP). The interoperability information may fall into three categories: 1. Technical. Interfaces, crashes, packet loss, performance degradations, IDS issues on host or within a network, etc 2. Process/Procedural. Those that ensure IOP during installation, configuration, launch, menu navigation and operational use. 3. People. Training or operator issues that might affect IOP. If you have IOP information that we might use, please pass it to me at woodallc () fhu disa mil in this format: IDS: <name> IOP Issue: <definition and impact> Recommendation for Resolution: <the patch or fix> If I'm unclear or you have a question, please feel free to call me. We need your support, since you have deeper operational IDS experience than I do. Appreciate any assistance anyone might offer. Thanks, CHUCK WOODALL Senior Engineer JITC-TRW (520) 538-5366 (DSN 879)
Current thread:
- Request for IDS Interoperability Information Woodall, Chuck (Sep 19)
- <Possible follow-ups>
- Re: Request for IDS Interoperability Information mark . teicher (Sep 20)
