6) Always maintain a good back-up regimen for your database.
I think asking users to solve security issues by having "good backups"
is really ridiculous.
As most of us understood, he meant server-side backup of the
database, so if something does
go wrong, the admin can restore the pre-security breach situation.
Besides the fact that most people don't have good backups (even those
that think they do- when was the last time you unspooled all of your
backups to make sure they contained what you think they contain?)-
You are probably talking about your own database system. I don't use
tapes, and or
compression, in order to verify my backup integrity directly.
what's to say that once restored, the host isn't compromised again and
this time- even worse?
It goes without saying that after a breach, the hole must be plunged
before restoring the database, but wouldn't you be glad to say to
your users, it will take a few days, but your old mails are save,
instead of, it will take a few days, *and* all your emails are gone?
I think the recommendations where good for the average system.
What happens when the invaders manage to lie hidden for a long
time- are
you really going to roll your email back six months because that's the
last time you _know_ your data was safe?
It is a recommendation, as with all things, you can't do anything
better than your best.
If a hacker has taken up the task to destruct your database
thouroughly, than your sour, but at least you as system
*administrator* gave your best shot.
It's great advice- take regular backups- but it's also a cop-out.
Security issues must be fixed.
They must first exist, and be located. Meanwhile I do as Mike says,
create a good backup.
