Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Security-Driven  Software Development
  • Table Of Contents Toc
Security-Driven  Software Development

Security-Driven Software Development

By : Aspen Olmsted
5 (6)
close
close
Security-Driven  Software Development

Security-Driven Software Development

5 (6)
By: Aspen Olmsted

Overview of this book

Extend your software development skills to integrate security into every aspect of your projects. Perfect for any programmer or developer working on mission-critical applications, this hands-on guide helps you adopt secure software development practices. Explore core concepts like security specifi cation, modeling, and threat mitigation with the iterative approach of this book that allows you to trace security requirements through each phase of software development. You won’t stop at the basics; you’ll delve into multiple-layer att acks and develop the mindset to prevent them. Through an example application project involving an entertainment ticketing software system, you’ll look at high-profi le security incidents that have aff ected popular music stars and performers. Drawing from the author’s decades of experience building secure applications in this domain, this book off ers comprehensive techniques where problem-solving meets practicality for secure development. By the end of this book, you’ll have gained the expertise to systematically secure software projects, from crafting robust security specifi cations to adeptly mitigating multifaceted threats, ensuring your applications stand resilient in the face of evolving cybersecurity challenges.
Table of Contents (20 chapters)
close
close
Lock Free Chapter
1
Part 1: Modeling a Secure Application
8
Part 2: Mitigating Risks in Implementation
13
Part 3: Security Validation

Stubs

In software integration testing, stubs are components or modules that simulate the behavior of natural components or dependencies. Stubs replace components or modules that are external to the unit being tested. The primary purpose of using stubs is to create a controlled testing environment and to isolate the unit under test from its external dependencies. Stubs provide simple predefined responses to requests made by the unit being tested, allowing developers to verify that the unit integrates correctly with its dependencies.

Here are some key concepts related to the use of stubs in integration software testing:

  • Stub definition: A stub is a minimal implementation of a component or module that provides predefined responses to calls being tested by the unit. It is a temporary replacement for the actual component to isolate the unit under test during integration testing. Stubs help create a controlled environment for testing and allow the unit under test to interact with...
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Security-Driven  Software Development
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon