Book Image

Security-Driven Software Development

By : Aspen Olmsted
Book Image

Security-Driven Software Development

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)
Free Chapter
1
Part 1: Modeling a Secure Application
8
Part 2: Mitigating Risks in Implementation
13
Part 3: Security Validation

Managing activity concurrency

Concurrency in databases refers to the ability of a database management system (DBMS) to handle multiple transactions or operations simultaneously without compromising data integrity. Concurrency control mechanisms are essential to ensure that multiple users or processes can access and manipulate data concurrently without causing conflicts or inconsistencies. Here are key concepts related to database concurrency:

  • Isolation levels:
    • Isolation levels define the degree to which the operations of one transaction are isolated from the operations of other concurrent transactions.
    • Common isolation levels include READ UNCOMMITTED, READ COMMITTED, REPEATABLE READ, and SERIALIZABLE. You can think of these isolation levels as a trade-off between increased availability and lower consistency. This is because locks are used to ensure the separation of transactions in stronger isolation levels, leading to lower concurrency levels.
  • Locking:
    • Locks are mechanisms...