full-disclosure - sample of what's required to be written in a security related contract

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <200402031944.i13JiMK2005285@turing-police.cc.vt.edu>
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: sample of what's required to be written in a security related contract 

On Tue, 03 Feb 2004 08:39:52 PST, just for know how <justforknowhow@...oo.com>  said:
> 
> One of our customers asked us for a machine that would
> ensure their local network security. Our commercial
> representative came and asked if i had a solution for
> them. I told him i could install a linux machine in
> bridge between the customer's router and his local
> network and snort.

You missed your chance to say "Security is a process, not a
machine" and bill them for both the machine and tightening up
the rest of their local network security.  Do them a favor
and pay for a vacation someplace warm and sunny :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20040203/cedbdeef/attachment.bin