full-disclosure - Learn from history?

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>] [day] [month] [year] [list]

Message-ID: <D54AB2ADB72C164B8251422DE1D3234222AD36@srv900045>
From: svgn at orbid.be (Serge van Ginderachter (svgn))
Subject: Learn from history?

> The first thing to determine with the company management is: 
> What happens to
> the company if their network is down 1h? 2h? One day? One 
> week?  How much
> money does that represent?  If data is lost, how much does it cost to
> re-build it (resources, time spent, etc.)?

1 to 2 hours is no problem, and that's what happens most of the time.

> If you clearly assess the risks and come up with a solution showing an
> adequate cost-benefit ratio and you compare it to the possible losses,
> chances are that management will approve your proposal, 
> regardless of the
> company size (from SMB to Fortune-100).

True in theory, a hard sell in our experience.
The local market over here doesn't let you do that kind of stuff.

Btw, I'm talking about companies with (much) less than 30 or 50 users at
most.

Serge