Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
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

Secrets in tools

Secrets in tools is another problem you need to watch out for. Quite often, these are collaboration or support tools such as Slack, Jira, or even GitHub issues.

How do secrets end up in tools?

Convenience is probably the biggest reason why secrets end up in tools. For example, you’ve set up a database server for a project, but it’s misbehaving, and you need to submit a ticket to the helpdesk for them to inspect it.

However, to inspect it, they need the admin username/password or key pair. How will they do that? Perhaps they ask for it in the Jira template for filing a support ticket. Perhaps, out of an abundance of caution, they don’t, but instead contact you via Slack to get it when they need it.

In the first instance, the data is now in the Jira ticket database. In the second, it becomes part of the Slack direct message (DM) database. If a hacker were to gain admin access to either, they could search those databases.

How do you...

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