Privilege escalation, trojan’ed SSH daemons, key loggers… While the focus is still mostly on MS platforms, Unix boxes aren’t free of exploits. As they are made popular by Macs and ever more approachable distributions like Ubuntu, they become more of a focus. The large share of the server market they represent is a considerable source of information that is mouth-watering to hackers.
A good tool in the fight against ever evolving malware is Tripwire (the open source version cause we’re cheap). It takes the signature of key files on your systems (configuration, binaries) and checks them regularly for changes. Its major strength is the fact that no matter what exploit was used to compromise a certain binary, if this binary is infected, tripwire will go off. Modern antivirus softwares look for specific signatures of known infections, and there are so many of them that they only look for the ones that are thought to be in the wild at any given time. They also are in reactive mode against 0days and usually take a few days to adjust. Their behavioral analysis methods are based on heuristics and generate too many false positives to be worthwhile.
Tripwire doesn’t care what the infection is, it just goes off if something changed. This is simple and efficient. Now it should only be one piece of a comprehensive security policy.
In this article we’ll look at getting it installed and going on Ubuntu in a matter of minutes. You’ll want to be root for all this.
——————————————
First, get the package:
aptitude install tripwire
It’ll ask you for the passphrases used to secure itself.
You’ll end up with these config files in /etc/tripwire:
——————————————
Edit /etc/tripwire/twpol.txt to define which areas to keep an eye on, a pretty ok default is provided but needs some tweaking for Ubuntu and personal preference. I’d publish mine but hey, that’d be pretty stupid. Just keep in mind that you can use an exclamation mark “!” to negate a line, let’s say you want it to look at /etc but not /etc/shadow (user will want to change passwords in most cases) you’ll have a rule that looks like that:
{
/etc -> $(SEC_BIN) ;
! /etc/passwd ;
}
——————————————
When you’re done, run:
twadmin --create-polfile -S /etc/tripwire/site.key /etc/tripwire/twpol.txt
This will create the secured policy file based on the text file you just edited.
——————————————
The config file (/etc/tripwire/twcfg.txt) can be edited too but the defaults are nice too. When done run:
twadmin --create-cfgfile -S /etc/tripwire/site.key /etc/tripwire/twcfg.txt
Again, this creates it secured equivalent.
——————————————
Make sure that the created file are only readable/writable by root
chmod 600 /etc/tripwire/tw.cfg /etc/tripwire/tw.pol
Good practice dictates that you also should be removing plain text configuration files but you’ll want to keep them around for a little while, as you tweak your original config.
——————————————
Finally, you can initialize the database with:
tripwire --init
What this does is take a snapshot of everything you’ve specified in the policy file. If any of it changes, you’ll be notified.
——————————————
The following will run the check for changes manually.
tripwire --check
When you installed the package with aptitude, /etc/cron.daily/tripwire was automatically created to have this run everyday, root will received a mail report every day.
——————————————
If you want to make a change to the base config:
edit /etc/tripwire/twpol.txt twadmin --create-polfile -S /etc/tripwire/site.key /etc/tripwire/twpol.txt tripwire --init
If you want to update the base config, for example to acknowledge changes that happened on the box:
tripwire --update --twrfile /var/lib/tripwire/report/<hostname>-<date>-<hour>.twr