Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Crafting Secure Software
  • Toc
  • feedback
Crafting Secure Software

Crafting Secure Software

By : Greg Bulmash, Thomas Segura
5 (1)
close
Crafting Secure Software

Crafting Secure Software

5 (1)
By: Greg Bulmash, Thomas Segura

Overview of this book

Drawing from GitGuardian's extensive experience in securing millions of lines of code for organizations worldwide, Crafting Secure Software takes you on an exhaustive journey through the complex world of software security and prepares you to face current and emerging security challenges confidently. Authored by security experts, this book provides unique insights into the software development lifecycle (SDLC) and delivers actionable advice to help you mitigate and prevent risks. From securing code-writing tools and secrets to ensuring the integrity of the source code and delivery pipelines, you’ll get a good grasp on the threat landscape, uncover best practices for protecting your software, and craft recommendations for future-proofing against upcoming security regulations and legislation. By the end of this book, you’ll have gained a clear vision of the improvements needed in your security posture, along with concrete steps to implement them, empowering you to make informed decisions and take decisive action in safeguarding your software assets.
Table of Contents (11 chapters)
close
Appendix: Glossary of Acronyms and Abbreviations: Index

Secrets in artifacts

Secrets in artifacts are one more thing that you need to watch out for because they are tougher to extract than from other sources. Artifacts are the images and applications produced by a compiler and/or build process. These can range from something as large as a container or virtual machine (VM) image to something as small as a plugin for VS Code.

How do secrets end up in artifacts?

Some people think that once packed up in an artifact, any secrets are beyond extraction. But that’s not the case at all.

If you go back to Chapter 3, Securing Your Code-Writing Tools, a process was explained for getting under the hood of a VS Code plugin. All you have to do is change the .vsix extension to .zip and use an unzipping tool to get access to the source code. We recommended using SCA, SAST, and/or DAST tools to evaluate the code for security issues. But what if there’s a secret in that source, too? If it’s not your secret, you might think it...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete