Secure and Resilient Software: Requirements, Test Cases, and Testing Methods

Overview

Secure and Resilient Software: Requirements, Test Cases, and Testing Methods provides a comprehensive set of requirements for secure and resilient software development and operation. It supplies documented test cases for those requirements as well as best practices for testing nonfunctional requirements for improved information assurance. This resource-rich book includes:

  • Pre-developed nonfunctional requirements that can be reused for any ...
See more details below
Other sellers (Hardcover)
  • All (7) from $80.02   
  • New (4) from $80.02   
  • Used (3) from $121.74   
Sending request ...

Overview

Secure and Resilient Software: Requirements, Test Cases, and Testing Methods provides a comprehensive set of requirements for secure and resilient software development and operation. It supplies documented test cases for those requirements as well as best practices for testing nonfunctional requirements for improved information assurance. This resource-rich book includes:

  • Pre-developed nonfunctional requirements that can be reused for any software development project
  • Documented test cases that go along with the requirements and can be used to develop a Test Plan for the software
  • Testing methods that can be applied to the test cases provided
  • A CD with all security requirements and test cases as well as MS Word versions of the checklists, requirements, and test cases covered in the book

Offering ground-level, already-developed software nonfunctional requirements and corresponding test cases and methods, this book will help to ensure that your software meets its nonfunctional requirements for security and resilience. The accompanying CD filled with helpful checklists and reusable documentation provides you with the tools needed to integrate security into the requirements analysis, design, and testing phases of your software development lifecycle.

Some Praise for the Book:

This book pulls together the state of the art in thinking about this important issue in a holistic way with several examples. It takes you through the entire lifecycle from conception to implementation ... .
—Doug Cavit, Chief Security Strategist, Microsoft Corporation

...provides the reader with the tools necessary to jump-start and mature security within the software development lifecycle (SDLC).
—Jeff Weekes, Sr. Security Architect at Terra Verde Services

... full of useful insights and practical advice from two authors who have lived this process. What you get is a tactical application security roadmap that cuts through the noise and is immediately applicable to your projects.
—Jeff Williams, Aspect Security CEO and Volunteer Chair of the OWASP Foundation

Read More Show Less

Editorial Reviews

From the Publisher
Developing more secure and resilient software has to be an integral part of the design and the implementation of an application and not an afterthought. The key to better security and resiliency comes down to education, continuous improvement and accountability. This book pulls together the state of the art in thinking about this important issue in a holistic way with several examples. It takes you through the entire lifecycle from conception to implementation and highlights where methodologies like the Microsoft Security Development Lifecycle can play a significant role in improving the security and reliability of your software.
—Doug Cavit, Chief Security Strategist, Microsoft Corporation

Demonstrating thorough understanding of the problems facing development organizations today, Secure and Resilient Software provides the reader with the tools necessary to jump-start and mature security within the software development lifecycle (SDLC). The authors bridge the gap between theory and practical application by providing valuable processes, checklists, frameworks, and examples. The material presented fills a gap that was desperately needed and is a must read for anyone participating in requirements gathering, quality assurance, development, and/or application security testing processes.
—Jeff Weekes, Sr. Security Architect at Terra Verde Services

It’s hard to imagine a more difficult and less well understood challenge than developing secure and resilient software. This book is full of useful insights and practical advice from two authors who have lived this process. What you get is a tactical application security roadmap that cuts through the noise and is immediately applicable to your projects. What’s really unique is the way that the book links together different standards to illuminate security across the entire software development process. You’ll learn how security evolves from threats to security requirements, through security services like OWASP ESAPI, into security architecture, and then into security testing and analysis leveraging OWASP ASVS. Highly recommended for anyone who cares about the future of the world’s software.
—Jeff Williams, Aspect Security CEO and Volunteer Chair of the OWASP Foundation

Read More Show Less

Product Details

  • ISBN-13: 9781439866214
  • Publisher: Taylor & Francis
  • Publication date: 12/9/2011
  • Pages: 278
  • Product dimensions: 6.10 (w) x 9.30 (h) x 0.80 (d)

Meet the Author

Mark S. Merkow, CISSP, CISM, CSSLP works at PayPal Inc. (an eBay company) in Scottsdale, Arizona, as Manager of Information Security Policies, Standards, Training, and Awareness in the Information Risk Management area. Mark has more than 35 years of experience in information technology in a variety of roles, including applications development, systems analysis and design, security engineering, and security management. Mark holds a masters degree in decision and info systems from Arizona State University (ASU), a masters of education in distance learning from ASU, and an undergraduate degree in computer info systems from ASU. In addition to his day job, Mark engages in a number of other extracurricular activities, including consulting, course development, online course delivery, and writing columns and books on information technology and information security.

Mark has authored or coauthored ten books on IT and is a contributing editor on four others. Mark remains very active within the information security community, working in a variety of roles for the Financial Services Information Sharing and Analysis Center (FS-ISAC), the Financial Services Technology Consortium (FSTC), and the Financial Services Sector Coordinating Council (FSCCC) on Homeland Security and Critical Infrastructure Protection.

He is the chairman of the Education Committee for the FS-ISAC and is a founding member of the Research and Development Committee of the FSSCC.

Lakshmikanth Raghavan, CISM, CRISC (Laksh) works at PayPal Inc. (an eBay company) as Staff Information Security Engineer in the Information Risk Management area, specializing in application security. Laksh has more than ten years of experience in the areas of information security and information risk management, and has provided consulting services to Fortune 500 companies and financial services companies around the world. Laksh holds a bachelor’s degree in electronics and telecommunication engineering from the University of Madras, India. He enjoys writing security-related articles and has spoken on the various dimensions of software security at industry forums and security conferences. This is Laksh’s second book.

Read More Show Less

Table of Contents

Introduction
Secure and Resilient
Bad Design Choices Led to the Vulnerable Internet We Know Today
HTTP Has Its Problems, Too
Design Errors Continue Haunting Us Today
Requirements & Design: The Keys to a Successful Software Project
How Design Flaws Play Out
DNS Vulnerability
The London Stock Exchange
Medical Equipment
Airbus A380
Solutions Are In Sight!
Notes

Nonfunctional Requirements (NFRs) in Context
System Quality Requirements Engineering (SQUARE)
Agree on Definitions
Identify Assets and Security/Quality Goals
Perform Risk Assessments
Elicit Security Requirements
Prioritize Requirements
Characteristics of Good Requirements
Summary
Notes

Resilience and Quality Considerations for Application Software and the Application Runtime Environment
Relationships among Nonfunctional Requirements
Considerations for Developing NFRs for your Applications and Runtime Environment
Checking Your Work
Summary
Notes

Security Requirements for Application Software
Security Control Types
Think Like an Attacker
Detailed Security Requirements
Identification Requirements
Authentication Requirements
Authorization Requirements
Security Auditing Requirements
Confidentiality Requirements
Integrity Requirements
Availability Requirements
Nonrepudiation Requirements
Immunity Requirements
Survivability Requirements
Systems Maintenance Security Requirements
Privacy Requirements
Summary
References

Security Services for the Application Operating Environment
The Open Group Architecture Framework (TOGAF)
Standardizing Tools for an Enterprise Architecture
Security Technical Reference Model (TRM)
Identification and Authentication
System Entry Control
Audit
Access Control
Nonrepudiation
Security Management
Trusted Recovery
Encryption
Trusted Communications
Summary
References

Software Design Considerations for Security and Resilience
Design Issues
Architecture and Design Considerations
Special Security Design Considerations for Payment Applications on Mobile Communications Devices
Designing for Integrity
Architecture and Design Review Checklist
Summary
References

Best Practices for Converting Requirements to Secure Software Designs
Secure Design Approach
Reusable Security APIs/Libraries
Security Frameworks
Establishing and Following Best Practices for Design
Security Requirements
Security Recommendations
What’s an Attack Surface?
What Is Managed Code?
Understanding Business Requirements for Security Design
Summary
References

Security Test Cases
Standardized Testing Policy
Security Test Cases
Test Cases for Identification Requirements
Test Cases for Authentication Requirements
Test Cases for Authorization Requirements
Test Cases for Security Auditing Requirements
Test Cases for Confidentiality Requirements
Test Cases for Integrity Requirements
Test Cases for Availability Requirements
Test Cases for Nonrepudiation Requirements
Test Cases for Immunity Requirements
Test Cases for Survivability Requirements
Test Cases for Systems Maintenance Security Requirements
Summary

Testing Methods and Best Practices
Secure Testing Approach
OWASP’s Application Security Verification Standard (ASVS)
Application Security Verification Levels
Level 1—Automated Verification
Level 2—Manual Verification
Level 3—Design Verification
Level 4—Internal Verification
Security Testing Methods
Manual Source Code Review
Automated Source Code Analysis
Automated Reviews Compared with Manual Reviews
Automated Source Code Analysis Tools—Deployment Strategy
IDE Integration for Developers
Build Integration for Governance
Automated Dynamic Analysis
Limitations of Automated Dynamic Analysis Tools
Automated Dynamic Analysis Tools—Deployment Strategy
Developer Testing
Centralized Quality Assurance Testing
Penetration (Pen) Testing
Gray Box Testing
Summary
References

Connecting the Moving Parts
OpenSAMM
Security Requirements
Security Requirements: Level 1
Security Requirements: Level 2
Security Requirements: Level 3
Security Testing
Security Testing: Level 1
Security Testing: Level 2
Security Testing: Level 3
Wrap-Up
References
Index

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)