I would very much say Perl and IS/IT tie very well together.
It really depends on what you are doing in security. Setting up PGP keyrings? Automating FTP processes? Moving from FTP to SSH? Running "Crack" Periodically? -- Or administrating firewalls?
The first four of these, "Thinking" security jobs, I would think a 2-4 year stint in security could be very good for your career. ESPECIALLY if you want to work in "real IS", not the shrink-wrapped world. If it's an "unthinking" job where you are really a computer operator who runs security software ... run away quickly.
JMHO. If location is an issue, consider it deeply.
regards,
Matthew Heusser,
heusserm at student dot gvsu dot edu | [reply] |
When I was doing a job that sounds similar to yours, I too re-implemented some tools in perl. With hind sight, I would have just used pre-existing tools, using perl for analysing their reports. Most of the important tools - snort, tripwire etc - are sufficiently cross platform already.
I think the original poster should be careful, and if he thinks he needs to write some tool from scratch should look very carefully at the options that area already available. His time is probably better spent in understanding the existing tools and writing better analysis tools, rather than re-implementing everything himself. | [reply] |