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

Securing built-in CI/CD tools

Each major SCM has its own native CI/CD tool. There are GitHub Actions, GitLab CI/CD, and Bitbucket Pipelines, to name a few. Let’s look at a few high-level concerns to consider.

Be sure and intentional about "which" does "what"

Continous integration and continuous delivery (CI/CD) are two different pipelines. CI brings all the pieces together and builds and tests the artifacts. All the SAST, DAST, SCA, secrets scanning, and so on can be done in the CI pipeline, but can also be triggered by hooks and run before commits or to inspect pull requests before merging.

CD is intended to deploy the artifacts built in CI. They can be delivered to production or a testbed/staging environment. Some companies employ a green/blue method in which the last good deployment is demoted to the blue (backup) environment while the new artifacts are deployed to green (production). Should the latest code fail, the system can switch over to...

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