Re: Common Unix Security Risks - Your help please!
From: Gandalf Parker (gandalf_at_most.of.my.favorite.sites)
Date: 06/11/04
- Next message: Gandalf Parker: "Re: Common Unix Security Risks - Your help please!"
- Previous message: Gandalf Parker: "Re: IP Tracking"
- In reply to: Ben Watkins: "Common Unix Security Risks - Your help please!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 11 Jun 2004 16:55:04 GMT
b.u.watkins@gmx.co.uk (Ben Watkins) wrote in
news:f2b78b04.0406080956.21732a19@posting.google.com:
> I am currently writing a university assignment on Unix Security.
>
> I would be grateful if you guys could help me out...
>
> What, in your minds, are the most common (top five) and potentially
> most exploitable security risks that you see in Unix/Linux
> deployments?
IMHO
1) using defaults
2) getting secure, then adding an "easy administration" package
3) no internal policies to block social engineering attempts
4) considering security to be locking-out only with no watchdogs on the
system for spotting unusual changes
5) considering "secure" to be something you do once and thats adequate
If I were to add two more it would be
6) relying on any popular well-known package for security
7) relying only on ONE security package to make you secure
Gandalf Parker
-- alt.hacker newsgroup
(white-hats only need apply)
www.alt-hacker.org
- Next message: Gandalf Parker: "Re: Common Unix Security Risks - Your help please!"
- Previous message: Gandalf Parker: "Re: IP Tracking"
- In reply to: Ben Watkins: "Common Unix Security Risks - Your help please!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|