Strengthen Software Security by Helping Developers and Security Experts Work TogetherTraditional approaches to securing software are inadequate. The solution: Bring software engineering and network security teams together in a new, holistic approach to protecting the entire enterprise. Now, four highly-respected security experts explain why this "confluence" is so crucial, and show how to implement it in your organization.Writing for all software and security practitioners and leaders, they show how software can play a vital, active role in protecting your organization. Youll learn how to construct software that actively safeguards sensitive data and business processes and contributes to intrusion detection/response in sophisticated new ways.The authors cover the entire development lifecycle, including project inception, design, implementation, testing, deployment, operation, and maintenance. They also provide a full chapter of advice specifically for Chief Information Security Officers (CISO) and other enterprise security executives.Whatever your software security responsibilities, Enterprise Software Security delivers indispensable big-picture guidance–and specific, high-value recommendations you can apply right now.Coverage includes:• Overcoming common obstacles to collaboration between developers and IT security professionals• Helping programmers design, write, deploy, and operate more secure software• Helping network security engineers use application output more effectively• Organizing a software security team before youve even created requirements• Avoiding the unmanageable complexity and inherent flaws of layered security• Implementing positive software design practices and identifying security defects in existing designs• Teaming to improve code reviews, clarify attack scenarios associated with vulnerable code, and validate positive compliance• Moving beyond pentesting towards more comprehensive security testing• Integrating your new application with your existing security infrastructure• "Ruggedizing" DevOps by adding infosec to the relationship between development and operations• Protecting application security during maintenance
| Preface |
|
xiii | |
|
1 Introduction to the Problem |
|
|
1 | (32) |
|
Our Shared Predicament Today |
|
|
2 | (3) |
|
Why Are We in This Security Mess? |
|
|
5 | (2) |
|
|
|
7 | (4) |
|
|
|
11 | (4) |
|
The Status Quo: A Great Divide |
|
|
15 | (5) |
|
What's Wrong with This Picture? |
|
|
20 | (5) |
|
|
|
25 | (2) |
|
|
|
27 | (3) |
|
|
|
30 | (1) |
|
|
|
31 | (2) |
|
|
|
33 | (38) |
|
Without a Formal Software Security Process---The Norm Today |
|
|
34 | (8) |
|
The Case for a Project Security Team |
|
|
42 | (1) |
|
Tasks for the Project Security Team |
|
|
43 | (7) |
|
Putting Together the Project Security Team |
|
|
50 | (1) |
|
Roles to Cover on the Security Team |
|
|
51 | (13) |
|
Some Final Practical Considerations about Project Security Teams |
|
|
64 | (3) |
|
|
|
67 | (1) |
|
|
|
68 | (3) |
|
|
|
71 | (52) |
|
|
|
72 | (4) |
|
|
|
76 | (2) |
|
|
|
78 | (20) |
|
|
|
98 | (2) |
|
|
|
100 | (12) |
|
|
|
112 | (3) |
|
Deployment and Operations Planning |
|
|
115 | (6) |
|
|
|
121 | (1) |
|
|
|
121 | (2) |
|
4 Implementation Activities |
|
|
123 | (46) |
|
|
|
123 | (1) |
|
Stress the Positive and Strike the Balance |
|
|
124 | (2) |
|
Security Mechanisms and Controls |
|
|
126 | (20) |
|
|
|
146 | (2) |
|
|
|
148 | (4) |
|
Implementing Security Tiers |
|
|
152 | (2) |
|
|
|
154 | (3) |
|
A Day in the Life of a Servlet |
|
|
157 | (10) |
|
|
|
167 | (1) |
|
|
|
167 | (2) |
|
|
|
169 | (24) |
|
A Few Questions about Security Testing |
|
|
170 | (10) |
|
|
|
180 | (5) |
|
|
|
185 | (6) |
|
|
|
191 | (1) |
|
|
|
192 | (1) |
|
6 Deployment and Integration |
|
|
193 | (28) |
|
How Does Deployment Relate to Confluence? |
|
|
194 | (1) |
|
|
|
194 | (4) |
|
Advanced Topics in Deployment |
|
|
198 | (2) |
|
Integrating with the Security Operations Infrastructure |
|
|
200 | (13) |
|
Third-Generation Log Analysis Tools |
|
|
213 | (3) |
|
Retrofitting Legacy and Third-Party Components |
|
|
216 | (1) |
|
Notes for Small Shops or Individuals |
|
|
217 | (2) |
|
|
|
219 | (1) |
|
|
|
220 | (1) |
|
7 Operating Software Securely |
|
|
221 | (20) |
|
Adjusting Security Thresholds |
|
|
222 | (8) |
|
Dealing with IDS in Operations |
|
|
230 | (6) |
|
Identifying Critical Applications |
|
|
236 | (1) |
|
|
|
237 | (1) |
|
Notes for Small Shops or Individuals |
|
|
238 | (2) |
|
|
|
240 | (1) |
|
8 Maintaining Software Securely |
|
|
241 | (22) |
|
|
|
243 | (5) |
|
How Does Maintaining Software Securely Relate to Confluence? |
|
|
248 | (1) |
|
|
|
249 | (2) |
|
|
|
251 | (3) |
|
|
|
254 | (2) |
|
|
|
256 | (3) |
|
How Does Maintaining Software Securely Fit into Security SDLCs? |
|
|
259 | (2) |
|
|
|
261 | (1) |
|
|
|
262 | (1) |
|
9 The View from the Center |
|
|
263 | (32) |
|
Ideas for Encouraging Confluent Application Development |
|
|
265 | (4) |
|
Toward a Confluent Network |
|
|
269 | (4) |
|
Security Awareness and Training |
|
|
273 | (1) |
|
Policies, Standards, and Guidelines |
|
|
274 | (1) |
|
The Role of Other Departments and Corporate Entities |
|
|
275 | (2) |
|
Resource Budgeting and Strategic Planning for Confluence |
|
|
277 | (2) |
|
Assessment Tools and Techniques |
|
|
279 | (10) |
|
Mobile Plans---Postmortem Interviews |
|
|
289 | (3) |
|
Notes for Small Shops or Individuals |
|
|
292 | (1) |
|
|
|
292 | (1) |
|
|
|
293 | (2) |
| Index |
|
295 | |
Kenneth R. van Wyk is a career security guy, having started with Carnegie Mellon Universitys CERT/CC in the late 1980s and subsequently worked for the United States Department of Defense and in several senior technologist roles in the commercial sector. He is the co-author of two popular OReilly and Associates books on incident response and secure coding. He now owns and runs KRvW Associates, LLC, a software security consulting and training practice in Virginia, USA.
Mark G. Graff is the CISO of NASDAQ OMX. Formerly the chief cybersecurity strategist at Lawrence Livermore National Laboratory, he has appeared as an expert witness on computer security before Congress and analyzed electronic voting machine software security for the state of California. A past chairman of the International Forum of Incident Response and Security Teams (FIRST), Graff has lectured on risk analysis, the future of cyber security, and privacy before the American Academy for the Advancement of Science, the Federal Communications Commission (FCC), the Pentagon, and many U.S. national security facilities and think tanks.
Dan S. Peters has been involved with security for longer than he had first expected when he stumbled into this field out of curiosity while making a good living as a consultant and a commercial software developer. Many security disciplines are exciting to him, but mobile security has been the most intriguing topic as of late. Before working on this book, Dan repeatedly shared his passion for security in conference presentations and numerous publications.
Diana L. Burley, Ph.D., is an award-winning cyber-security workforce expert who has been honored by the U.S. Federal CIO Council and was named the CISSE 2014 Cybersecurity Educator of the Year. As a professor, researcher, and consultant on IT use and workforce development for nearly 20 years, she passionately promotes a holistic view of cyber security to influence education, policy, and practice from her home in the Washington, D.C., region.
Lisainfo e-raamatute kohta