For a holistic view on security, anything by Bruce Schneier comes highly recommended -- not the threat-specific focus you have in mind, but a background that will make you more effective at security issues in whatever role you play, whatever background you have.
For more specific views, I would recommend this book (and just about every book I've looked at in depth in the same series, but I can't personally vouch for all of them, they're dozens!-).
Alex's suggestion of Bruce Schneier's work is excellent, and everyone should read his stuff, but probably won't address what you're talking about. Even so, you should read it. He's the clearest writer on security topics today, and a voice of sanity in an often hysterical industry.
A free place to start for the bare bones is the SANS reading room. It's far from enough, but it's the basics.
I was fairly pleased with The Shellcoder's Handbook. It's a good introduction with some practical code to work with. It shows how real exploits are written, which is the first step in understanding how to protect against them.
Exploit work is done in a variety of things, but for the classic stack-smashing attacks, you need to know C and the assembler of the target platform (generally Intel). C++ is much less common in this world. It's too twisty-turny by the time the compiler gets done with it, and too bloated for the kinds of things needed. Objective-C is almost more useful in my opinion so that you can understand Mac reverse engineering. But that isn't where security is usually done. In this I'm speaking of exploits themselves. Many security tools are of course written in C++.
For the security tools side, you probably want to ask on serverfault. There are many, and the SANS link above should have links to some of the common tools (Nessus, nmap, hping, metasploit and the like). sectools.org maintains a big list that I like.
If you're going to be a security developer, you need a lot of breadth and a lot of depth. You need to understand the network protocols as well as the code that talks to them. You should be reasonably comfortable in languages from assembler to ruby. Much of it is more a way of thinking than an actual skill set, but those who are good at it tend to have broad skills and pick up new things quickly and often.
Since you noted specifically detecting and monitoring for exploits, you should dig into tools like snort (for learning how to detect) and metasploit (for generating the attacks to detect).
发布评论
评论（4）
转至 http://www.milw0rm.com/ 查看漏洞。
go to http://www.milw0rm.com/ to see the exploits.
为了全面了解安全性，强烈推荐 Bruce Schneier 的任何内容 - 而不是您关注的特定威胁无论您扮演什么角色，无论您拥有什么背景，您的背景都将使您在安全问题上更加有效。
对于更具体的观点，我会推荐这本书（以及几乎每本书我深入研究了 同一系列，但我个人不能保证所有这些，他们'几十个！-)。
For a holistic view on security, anything by Bruce Schneier comes highly recommended -- not the threat-specific focus you have in mind, but a background that will make you more effective at security issues in whatever role you play, whatever background you have.
For more specific views, I would recommend this book (and just about every book I've looked at in depth in the same series, but I can't personally vouch for all of them, they're dozens!-).
除了 Alex Martelli 发布的内容之外，您也可以考虑这本书 。
As well as what Alex Martelli posted, this book might be something you can consider.
亚历克斯对布鲁斯·施奈尔作品的建议非常好，每个人都应该阅读他的作品，但可能不会解决你正在谈论的内容。 即便如此，你也应该阅读它。 他是当今安全主题上最清晰的作家，也是这个时常歇斯底里的行业中理智的代言人。
SANS 阅览室是一个免费的入门场所。 这还远远不够，但这是基础。
我对Shellcoder 手册相当满意。 这是一个很好的介绍，并提供了一些实用的代码。 它展示了如何编写真正的漏洞利用程序，这是了解如何防范它们的第一步。
利用工作的方式多种多样，但对于经典的堆栈粉碎攻击，您需要了解 C 语言和目标平台（通常是 Intel）的汇编程序。 C++ 在这个世界上不太常见。 当编译器完成它时，它太曲折了，而且对于所需的东西来说太臃肿了。 在我看来，Objective-C 几乎更有用，这样你就可以理解 Mac 逆向工程。 但这不是通常进行安全保护的地方。 在这里我谈论的是利用本身。 许多安全工具当然是用 C++ 编写的。
对于安全工具方面，您可能想询问服务器故障。 有很多，上面的SANS链接应该有一些常用工具的链接（Nessus、nmap、hping、metasploit之类）。 sectools.org 维护着一个我喜欢的大列表。
如果您想成为一名安全开发人员，您需要足够的广度和深度。 您需要了解网络协议以及与它们通信的代码。 您应该对从汇编到 ruby 的语言都相当熟悉。 其中大部分更多的是一种思维方式，而不是实际的技能，但擅长于此的人往往拥有广泛的技能，并且能够快速且频繁地学习新事物。
由于您专门指出了检测和监控漏洞，因此您应该深入研究 snort（用于学习如何检测）和 metasploit（用于生成要检测的攻击）等工具。
Alex's suggestion of Bruce Schneier's work is excellent, and everyone should read his stuff, but probably won't address what you're talking about. Even so, you should read it. He's the clearest writer on security topics today, and a voice of sanity in an often hysterical industry.
A free place to start for the bare bones is the SANS reading room. It's far from enough, but it's the basics.
I was fairly pleased with The Shellcoder's Handbook. It's a good introduction with some practical code to work with. It shows how real exploits are written, which is the first step in understanding how to protect against them.
Exploit work is done in a variety of things, but for the classic stack-smashing attacks, you need to know C and the assembler of the target platform (generally Intel). C++ is much less common in this world. It's too twisty-turny by the time the compiler gets done with it, and too bloated for the kinds of things needed. Objective-C is almost more useful in my opinion so that you can understand Mac reverse engineering. But that isn't where security is usually done. In this I'm speaking of exploits themselves. Many security tools are of course written in C++.
For the security tools side, you probably want to ask on serverfault. There are many, and the SANS link above should have links to some of the common tools (Nessus, nmap, hping, metasploit and the like). sectools.org maintains a big list that I like.
If you're going to be a security developer, you need a lot of breadth and a lot of depth. You need to understand the network protocols as well as the code that talks to them. You should be reasonably comfortable in languages from assembler to ruby. Much of it is more a way of thinking than an actual skill set, but those who are good at it tend to have broad skills and pick up new things quickly and often.
Since you noted specifically detecting and monitoring for exploits, you should dig into tools like snort (for learning how to detect) and metasploit (for generating the attacks to detect).