Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There was a show called "Tiger Team" that only had two episodes. They had people who specialize in various areas. Someone who was good social engineering people, someone who was an expert in physical security devices, and someone who was an expert at technical hacking.
A lot of businesses don't have as secure of a network infrastructure as they probably should. Also, security researchers are targeting Cisco equipment such as routers more now by developing exploits to run arbitrary code, and creating proof of concept rootkits for IOS. So I would think it's going to become more important over time, and being familiar with Cisco would help if you want to become a technical hacker.
I wouldn't narrow it down to just Cisco gear though, you should have general knowledge of Networking fundamentals, along with OS knowledge. There are certification tracks like Security+, Network+ and so on you can take.
Also you should keep up with security vulnerabilities and exploits. Good security practices and learn the other many ways people gain access to environments outside of computers as well. Security isn't limited to just computers.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
First off, security is not nearly as glamorous as it appears in hacker movies and security vulnerability mailing lists. A whole lot of it is about boring audits, controls, and processes. You have to be extremely detail-oriented and process-driven to work in the security field, just a warning...
From a practical standpoint, research the Common Body of Knowledge. It's used for the CISSP certification. There are tons of books and websites that have study material. Note that I'm not necessarily recommending you try to achieve the certification, but the study material for it is very useful. It covers things like business continuity planning, incident response, physical security, cryptography, etc... Note that the most important things you'll learn about security are the processes and methodologies. Being able to configure a firewall is great, but being able to quantify in dollar value what a particular firewall is worth to your company is even better.
Take some time to study programming/software development security practices. It's important to know what sort of things to keep in mind when developing software and how to be security-conscious. If you don't understand how applications become vulnerable, you won't be able to understand how attackers are exploiting them. One of the biggest things you'll learn in that process is to write human-readable code with plenty of documentation. Most security vulnerabilities occur when technology is poorly understood, or misinterpreted. The more/better you document things, the less chance for error.
There are so many different security applications, and the market is changing so quickly, that there isn't really any point in learning any one product or area right now. Just concentrate on the principles and you'll be able to pickup the specifics as you go along.
Oh yeah, and the #1 thing to understand: The "most secure" thing is almost never the "right thing" to do from an employer's standpoint. Why? Because it prevents work from getting done, which prevents them from making money. You'll need to accept the fact that you often have to compromise on "ideal" security to get something that is acceptable to the business. There's no point in complaining about it, that will just get you labeled as a trouble-maker. Instead, try to understand what your company does to make money and think of ways that security can cooperate with that and make it easier as well as safer. Then you'll be a hero instead of an outcast.
Oh yeah, and the #1 thing to understand: The "most secure" thing is almost never the "right thing" to do from an employer's standpoint. Why? Because it prevents work from getting done, which prevents them from making money. You'll need to accept the fact that you often have to compromise on "ideal" security to get something that is acceptable to the business. There's no point in complaining about it, that will just get you labeled as a trouble-maker. Instead, try to understand what your company does to make money and think of ways that security can cooperate with that and make it easier as well as safer. Then you'll be a hero instead of an outcast.
I know this all to well...There are a lot of things that I wish I could implement...but it just won't allow work to happen...
If you want a career in Internet/Network security, you must be an expert in these fields.
Here's an useful site for you: http://www.penetration-testing.com/
The Open Source methodology knowledge is required in order to get a job at most companies.
The Open Source methodology knowledge is required in order to get a job at most companies.
Really? A lot of the major corporations in the US could care less about Open Source Methodology. (Not saying you shouldn't, just saying that required isn't really true... )
Really? A lot of the major corporations in the US could care less about Open Source Methodology. (Not saying you shouldn't, just saying that required isn't really true... )
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
Quote:
Originally Posted by simonapnic
The Open Source methodology knowledge is required in order to get a job at most companies.
Not all all. The last 4 companies I've worked at have made extensive use of Open Source software, but none of them made source code available to the public and some of them spent quite a bit of time with lawyers making sure they could keep all their stuff secret.
Most companies don't give a damn about "Open Source methodology", they only care about "software that we don't have to pay huge license fees for", so they can in turn make higher profit margins when they turn around and sell it to someone else.
Even companies like IBM that seemingly "contribute" a lot to Open Source projects are only doing it out of greed: Investing a little bit in community projects is much cheaper than employing an army of employees to build the same thing. They can devote only a few employees to making just the changes they want, while the rest of the community maintains all the necessary, but very mundane features that IBM doesn't care that much about.
Don't buy into the gibberish that RMS spews. GNU isn't making any headway in the corporate world--free software is.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.