To learn how to keep things secured, and to do a good job at it, what books should one check out?
closed as not constructive by Iszi, Polynomial, Rory Alsop♦ Aug 4 '12 at 20:08
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. If this question can be reworded to fit the rules in the help center, please edit the question.
This is a very broad question. I'd start by understanding the basic security principals or even the CISSP domains, check out https://www.isc2.org/cissp-domains/default.aspx. Then I'd probably buy a book or heavily read about whatever OS you are planning on using. However, I'd focus on:
- Server hardening (don't let stuff you don't need run and secure what you do; i.e. Denyhosts for SSH).
- IDS/Firewall/Security SW (know what works well for your distro)
I don't think such a definite set of books exists- there is a lot to security, and everyone on here is going to have a different opinion on what papers and books are superior and inferior. For example, some books cover certain topics excellently but others vaguely. Some are perfect for a certain type of individual, with a specific skill and level, but absolutely trivial and boring for another.
Personally I think you are best researching one specific topic at a time, with a variety of resources that you have picked. So instead of grabbing a suggested, broad, security book and reading it from front to back, pick up several books and resources, and read how they each cover one specific topic. Make your way through topics using an array of resources.
While doing this ensure you remain hands on. You don't want to just read, you want to actually do it yourself. So set up a local server environment and get to work; set up your own experiments and be prepared to break things (recursive: breaking, fixing, securing).
Securing a server also involves securing the applications running on it. There is no point having a super secure server if the main application running is vulnerable to SQL injection and remote file inclusion. That then opens up the available learning content massively. So make sure you remain open. Also remember, even if you take all precautions, you still, sooner or later fail; Keep damage minimisation and mitigation on your mind- limit scope and verify backups.
Digital security is a long, forever changing road.
If you were to provide a bit about yourself: your skills and proficiencies, maybe someone would be able to recommend some starting resources and topics (are you a confident server administrator and/or engineer? / are you aware of the top server/web application vulnerabilities? / What is your experience in digital security? / What type of application and server you are working on? / etc)