Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: Linux hardening |
|---|---|
| Date: | Fri, 26 Aug 2005 22:47:50 +0100 |
Norwich University - Information Security wrote:
Since we're talking about Linux hardening... What do folks suggest as far as files that should be monitored with integrity checking tools? Obviously, tmp files and other frequently changed files are out of the question, and it is also impractical to do checking on all other files. Does anyone have a best practices list or suggestions of what files are critical to monitor with integrity checking?
Anything in: bin boot dev etc lib opt sbin usr although you can exclude stuff like documentation from /usr. You can exclude most of: home mnt proc root tmp var Although sometimes services live under /home (e.g. /home/httpd), in which case you might need to monitor such directories. -- Glynn Clements <glynn@gclements.plus.com>
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Linux hardening, Pär Johansson |
|---|---|
| Next by Date: | Re: Xvfb Question, Glynn Clements |
| Previous by Thread: | Re: Linux hardening, Jayson Anderson |
| Next by Thread: | Re: Linux hardening, Craig Holmes |
| Indexes: | [Date] [Thread] [Top] [All Lists] |