I care about this much --> . what anyone here thinks about my technical background/knowledge.
yes, that is why your certs are in your sig, and why you continue to reply to me in this thead.
I always thought things such as hps, acls, vpns (pptp, l2tp, ipsec), idss, design, se protocols, firewalls (packet filtering, kernel proxy, application level, sifs, dpfs,etc.) policy based routing, etc... (sorry for all the "buzzwords" but i assume a discussion at this level would accept that)
Heh, did you just recite every firewall buzword you know? you could of simply said "setup a firewall". Yes, it is super complicated to plug in a PIX / Netscreen and config it via a web interface (my secretary could do it).
I also hope you don't believe network security is wraped up loosley to scanning a network and suggesting patches
Well, network security has mostly to do with network traffic, and network services, all of which can be observed through scanning...
Since when has system/network security been easy
system security in a nutshell:
a) grep /home/LUSER/src gets
b) non-exececutable stack (most stack overflow sploits no longer work due to this)
network security in a netshell:
a) don't run dumb services (telnet, wftpd, sendmail)
b) chroot everything else
Wow, that was complicated.
It's one of the largest growing branches in the IT industry, especially after 911.
People get scared... network / app security is no secret. People get lazy, how many exploits (assuming they are public) are preventable with a patch? I would guess at 99%. If it is not public, it is folly to worry about it extensivly. However you chroot and use non exec stacks to prevent this (there are very few heap exploits about, anyways).
Ah, come on! I don't even know for sure if she's a girl yet!
That didn't seem to stop you.