Re: preventing tampering with tripwire
From: Klaus Steden (klaus@compt.com)
Date: 06/19/02
- Next message: Maxlor: "Re: preventing tampering with tripwire"
- Previous message: Baldur Gislason: "Re: preventing tampering with tripwire"
- In reply to: Maxlor: "preventing tampering with tripwire"
- Next in thread: twig les: "Re: preventing tampering with tripwire"
- Reply: twig les: "Re: preventing tampering with tripwire"
- Reply: Eric F Crist: "RE: preventing tampering with tripwire"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 18 Jun 2002 19:49:59 -0400 From: Klaus Steden <klaus@compt.com> To: Maxlor <mail@maxlor.com>
Read-only media is a good thing, too.
It may be overkill (in the case of security, is there such a thing, though?),
but you could re-purpose an old disk drive, add security tools you want to it,
and jumper it read-only. That wouldn't necessarily prevent your database from
being compromised, but your tools would be intact.
With a read-only disk, I would ...
- install the security tools you want on it
- generate any baseline configuration data and signatures
- make the disk physically read-only
- run your nightly cron jobs, comparing your daily results against your
read-only baseline.
Of course, every time you upgrade something, you'll have to unjumper the disk,
update your signatures, and rejumper it, but that's not really such a big
deal when compared with what else you might have to do. :>
Keeping known good copies of essential programs (ls, find, dd, netstat, route,
ifconfig, mv, cp, df, etc.) on the read-only media is a good idea, too.
You could accomplish this with CDROMs if you don't want to use a disk drive,
but you lose the option of rewritability.
hope this helps,
Klaus
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
- Next message: Maxlor: "Re: preventing tampering with tripwire"
- Previous message: Baldur Gislason: "Re: preventing tampering with tripwire"
- In reply to: Maxlor: "preventing tampering with tripwire"
- Next in thread: twig les: "Re: preventing tampering with tripwire"
- Reply: twig les: "Re: preventing tampering with tripwire"
- Reply: Eric F Crist: "RE: preventing tampering with tripwire"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|