Testing Web Security: Assessing the Security of Web Sites and Applications
×
Success!
×
Error!
×
Information !
Rights Contact Login For More Details
More About This Title Testing Web Security: Assessing the Security of Web Sites and Applications
- English
English
STEVEN SPLAINE is a chartered software engineer with more than twenty years of experience in project management, software testing, and product development. He is a regular speaker at software testing conferences and lead author of The Web Testing Handbook.
- English
English
Acknowledgments.
Foreword.
Preface.
PART ONE: AN INTRODUCTION TO THE BOOK.
Introduction.
PART TWO: PLANNING THE TESTING EFFORT.
Test Planning.
PART THREE: TEST DESIGN.
Network Security.
System Software Security.
Client-Side Application Security.
Server-Side Application Security.
Sneak Attacks: Guarding Against the Less-Thought-of Security Threats.
Intruder Confusion, Detection, and Response.
PART FOUR: TEST IMPLEMENTATION.
Assessment and Penetration Options.
Risk Analysis.
Epilogue.
PART FIVE: APPENDIXES.
Appendix A: An Overview of Network Protocols, Addresses, and Devices.
Appendix B: SANS Institute Top 20 Critical Internet Security Vulnerabilities.
Appendix C: Test-Deliverable Templates.
Additional Rsources.
Index.
Foreword.
Preface.
PART ONE: AN INTRODUCTION TO THE BOOK.
Introduction.
PART TWO: PLANNING THE TESTING EFFORT.
Test Planning.
PART THREE: TEST DESIGN.
Network Security.
System Software Security.
Client-Side Application Security.
Server-Side Application Security.
Sneak Attacks: Guarding Against the Less-Thought-of Security Threats.
Intruder Confusion, Detection, and Response.
PART FOUR: TEST IMPLEMENTATION.
Assessment and Penetration Options.
Risk Analysis.
Epilogue.
PART FIVE: APPENDIXES.
Appendix A: An Overview of Network Protocols, Addresses, and Devices.
Appendix B: SANS Institute Top 20 Critical Internet Security Vulnerabilities.
Appendix C: Test-Deliverable Templates.
Additional Rsources.
Index.
- English
English
“…a helpful guide…a direct and easy to understand style of writing…” (Software Testing, Verification and Reliability, Dec 2004)