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
Crafting Secure Software

You're reading from   Crafting Secure Software An engineering leader's guide to security by design

Arrow left icon
Product type Paperback
Published in Sep 2024
Publisher Packt
ISBN-13 9781835885062
Length 156 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
GitGuardian SAS GitGuardian SAS
Author Profile Icon GitGuardian SAS
GitGuardian SAS
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. Chapter 1: Introduction to the Security Landscape 2. Chapter 2: The Software Supply Chain and the SDLC FREE CHAPTER 3. Chapter 3: Securing Your Code-Writing Tools 4. Chapter 4: Securing Your Secrets 5. Chapter 5: Securing Your Source Code 6. Chapter 6: Securing Your Delivery 7. Chapter 7: Security Compliance and Certification 8. Chapter 8: Best Practices to Drive Security Buy-In 9. Other Books You May Enjoy Appendix: Glossary of Acronyms and Abbreviations: Index

Testing SAST, DAST, and SCA

Traditional testing checks for functionality and performance, but security testing takes it a step further. By looking at both the code and how the application behaves, as well as the components used, we can find and fix potential vulnerabilities. This helps protect against attacks and shows customers that we take their security seriously.

Why testing is important

Testing is more than a checkbox in the development process. It’s a step to ensure the safety and reliability of your software. Testing is the quality assurance process that catches errors and flaws before they end up in a release.

Regular testing is about proving to your customers and partners that you take their security seriously. As we’ll discuss later in this section, reports from testing can be used to create security compliance artifacts for pre-sales requirements and/or regulatory requirements.

While unit testing ensures code provides expected results when run against...

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