Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Practical Security Automation and Testing

You're reading from   Practical Security Automation and Testing Tools and techniques for automated security scanning and testing in DevSecOps

Arrow left icon
Product type Paperback
Published in Feb 2019
Publisher Packt
ISBN-13 9781789802023
Length 256 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Tony Hsiang-Chih Hsu Tony Hsiang-Chih Hsu
Author Profile Icon Tony Hsiang-Chih Hsu
Tony Hsiang-Chih Hsu
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. The Scope and Challenges of Security Automation FREE CHAPTER 2. Integrating Security and Automation 3. Secure Code Inspection 4. Sensitive Information and Privacy Testing 5. Security API and Fuzz Testing 6. Web Application Security Testing 7. Android Security Testing 8. Infrastructure Security 9. BDD Acceptance Security Testing 10. Project Background and Automation Approach 11. Automated Testing for Web Applications 12. Automated Fuzz API Security Testing 13. Automated Infrastructure Security 14. Managing and Presenting Test Results 15. Summary of Automation Security Testing Tips 16. List of Scripts and Tools 17. Solutions 18. Other Books You May Enjoy

Case study – XXE security

The XXE security issue is one of the OWASP Top 10 security issues. The solution to the XXE issue is to disable XXE and DTD (Document Type Definition) processing. Therefore, when we are doing source code review, we are looking for whether the configuration of DTD is missing in the source code, as shown in the following example:

Factory.setFeature(“http://apache.org/xml/features/disallow-doctype-decl”, true);

White-box review is still the most efficient approach to identifying XXE issues. The easiest thing to do is to discover whether one of the following XML libraries is being used to parse XML. We may use one of the tools such as CRASS or VCG mentioned in previous section to do such a search with the keywords listed here:

Programming language

Source code patterns for potential XXE issues

Java

SAXParser | SAXParserFactory...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image