Date: Sun, 19 Sep 1999 21:27:41 -0600 From: Nate Williams <nate@mt.sri.com> To: Brett Glass <brett@lariat.org> Cc: nate@mt.sri.com (Nate Williams), Wes Peters <wes@softweyr.com>, "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>, Warner Losh <imp@village.org>, security@FreeBSD.ORG Subject: Re: Real-time alarms Message-ID: <199909200327.VAA28019@mt.sri.com> In-Reply-To: <4.2.0.58.19990919175752.04577a20@localhost> References: <4.2.0.58.19990918201409.047f9f00@localhost> <199909180612.AAA00597@harmony.village.org> <4.2.0.58.19990918093306.047917c0@localhost> <37E4449B.ADDD68EE@softweyr.com> <199909191933.NAA25843@mt.sri.com> <4.2.0.58.19990919175752.04577a20@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
> Break-in detection systems work very well in the physical world Not. My company is doing alot of work in this area, including trying to reduce the amount of false alarms and other useless information the #1 'security' product generates. > where -- > as we all know -- it's ultimately possible to break into nearly > anything if you employ sufficient force or defeat a perimeter defense. That's the point. The *hard* problem is making something sufficiently secure *AND* informing the person of the breakin while minimizing the number of false alarms. Also, breakins are *NOT* just gaining root access, sometimes it's as trivial as getting inside a network. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909200327.VAA28019>