book

Software Test Attacks to Break Mobile and Embedded Devices

Name: Software Test Attacks to Break Mobile and Embedded Devices
Author: Jon Duncan Hagar
ISBN: 9781498760140

by Jon Duncan Hagar

September 2013

Intermediate to advanced

377 pages

11h 40m

English

Chapman and Hall/CRC

Read now

Unlock full access

Foreword by Dorothy Graham
Foreword by Lisa Crispin
Preface
Acknowledgments
Copyright and Trademarks Declaration Page
Introduction
Getting StartedWho Should Be Familiar with This BookWhat Is Not in This BookRelationship to Other Test References and Works by Other AuthorsAttack-Based Testing and Different Approaches to Software DevelopmentA Final Introduction WarningReferences
Author
Chapter 1 - Setting the Mobile and Embedded Framework
Objectives of Testing Mobile and Embedded Software SystemsWhat Is Embedded Software?What Are “Smart” Handheld and Mobile Systems?Why Mobile and Embedded Attacks?Framework for AttacksBeginning Your Test StrategyAttacks on Mobile and Embedded SoftwareIf You Are New to TestingAn Enlightened Tester Makes a Better TesterExercises (Answers Are on My Website)References
Chapter 2 - Developer Attacks: Taking the Code Head On
Attack 1: Static Code AnalysisWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackAttack 2: Finding White-Box Data Computation BugsWhen to Apply This AttackWho Conducts This Attack?Where Is This Attack Conducted?What Faults Make This Attack Successful?How to Determine If This Attack Exposes FailuresHow to Conduct This AttackAttack 3: White-Box Structural Logic Flow CoverageWho Conducts This Attack and When to Apply This Attack?What Faults Make This Attack Successful?How to Determine If This Attack Exposes FailuresHow to Conduct This AttackTest Coverage Concepts for White-Box Structural TestingNote of Concern in Mobile and Embedded EnvironmentsExercises (Answers on My Website)References
Chapter 3 - Control System Attacks
Attack 4: Finding Hardware–System Unhandled Uses in SoftwareWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackAttack 5: Hardware-to-Software and Software-to-Hardware Signal Interface BugsWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackAttack 6: Long-Duration Control Attack RunsWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where to Conduct This Attack?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackAttack 7: Breaking Software Logic and/or Control LawsWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Performs This Attack?Where to Run This Attack?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackAttack 8: Forcing the Unusual Bug CasesWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where to Conduct This Attack?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackExercises (Answers Are on My Website)References

Chapter 4 - Hardware Software Attacks
Attack 9: Breaking Software with Hardware and System OperationsWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where to Conduct This Attack?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackSub-Attack 9.1: Breaking Battery PowerAttack 10: Finding Bugs in Hardware–Software CommunicationsWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackAttack 11: Breaking Software Error RecoveryWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackAttack 12: Interface and Integration TestingWhen to Apply This AttackWho Conducts This Attack?Where Is This Attack Conducted?What Faults Make This Attack Successful?How to Conduct This AttackSub-Attack 12.1: Configuration Integration EvaluationAttack 13: Finding Problems in Software–System Fault ToleranceWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackExercises (Answers Are on My Website)References
Chapter 5 - Mobile and Embedded Software Attacks
Attack 14: Breaking Digital Software CommunicationsWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If the Attack Exposes a Failure?How to Conduct This AttackAttack 15: Finding Bugs in the DataWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackAttack 16: Bugs in System-Software ComputationWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where to Conduct This Attack?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackAttack 17: Using Simulation and Stimulation to Drive Software AttacksWhen to Apply This AttackWho Conducts This Attack?Where Is This Attack Conducted?What Faults Make This Attack Successful?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackExercises (Answers Are on My Website)References
Chapter 6 - Time Attacks: “It’s about Time”
Attack 18: Bugs in Timing Interrupts and Priority InversionsWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackState Modeling ExampleAttack 19: Finding Time-Related BugsWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackAttack 20: Time-Related Scenarios, Stories, and ToursWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where to Conduct This Attack?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackAttack 21: Performance Testing IntroductionWhen to Apply This AttackWho Conducts This Attack?Where Is the Test Conducted?What Faults Make This Attack Successful?How to Determine If This Attack Exposes FailuresHow to Conduct This AttackSupporting ConceptsCompleting and Reporting the Performance AttackWrapping UpExercises (Answers Are on My Website)References
Chapter 7 - Human User Interface Attacks: “The Limited (and Unlimited) User Interface”
How to Get Started—the UIAttack 22: Finding Supporting (User) Documentation ProblemsWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackSub-Attack 22.1: Confirming Install-AbilityAttack 23: Finding Missing or Wrong AlarmsWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackAttack 24: Finding Bugs in Help FilesWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where to Conduct This Attack?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackExercises (Answers Are on My Website)References
Chapter 8 - Smart and/or Mobile Phone Attacks
General Notes and Attack Concepts Applicable to Most Mobile–Embedded DevicesAttack 25: Finding Bugs in AppsWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If This Attack Exposes FailuresHow to Conduct This AttackAttack 26: Testing Mobile and Embedded GamesWhen to Apply This AttackWhat Faults Make This Attack Successful?Who Conducts This Attack?Where Is This Attack Conducted?How to Determine If This Attack Exposes FailuresHow to Conduct This AttackAttack 27: Attacking App–Cloud DependenciesWhen to Apply This AttackWho Conducts This Attack?Where Is This Attack Conducted?What Faults Make This Attack Successful?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackExercises (Answers Are on My Website)References
Chapter 9 - Mobile/Embedded Security
The Current SituationReusing Security AttacksAttack 28: Penetration Attack TestWhen to Apply This AttackWho Conducts This Attack?Where Is This Attack Conducted?What Faults Make This Attack Successful?How to Determine If This Attack Exposes FailuresHow to Conduct This AttackAttack 28.1: Penetration Sub-Attacks: Authentication—Password AttackHow to Conduct This AttackAttack 28.2: Sub-Attack Fuzz TestHow to Conduct This AttackAttack 29: Information Theft—Stealing Device DataWhen to Apply This AttackWho Conducts This Attack?Where to Conduct This Attack?How to Determine If This Attack Exposes FailuresWhat Faults Make This Attack Successful?How to Conduct This AttackAttack 29.1: Sub-Attack—Identity Social EngineeringAttack 30: Spoofing AttacksWhen to Apply This AttackWho Conducts This Attack?Where Is This Attack Conducted?What Faults Make This Attack Successful?How to Determine If This Attack Exposes FailuresHow to Conduct This AttackAttack 30.1: Location and/or User Profile Spoof Sub-AttackAttack 30.2: GPS Spoof Sub-AttackAttack 31: Attacking Viruses on the Run in Factories or PLCsWhen to Apply This AttackWho Conducts This Attack?Where Is This Attack Conducted?How to Determine If the Attack Exposes FailuresHow to Conduct This AttackExercises (Answers Are on My Website)References
Chapter 10 - Generic Attacks
Attack 32: Using Combinatorial TestsWhen to Apply This AttackWho Conducts This Attack?Where Is This Attack Conducted?What Faults Make This Attack Successful?How to Determine If This Attack Exposes FailuresHow to Conduct This AttackAttack 33: Attacking Functional BugsWhen to Apply This AttackWho Conducts This Attack?Where Is This Test Conducted?What Faults Make This Attack Successful?How to Determine If This Attack Exposes FailuresHow to Conduct This AttackExercises (Answers Are on My Website)References
Chapter 11 - Mobile and Embedded System Labs
Introduction to LabsTo StartTest FacilitiesWhy Should a Tester Care?What Problem Does a Test Lab Solve?Staged Evolution of a Test LabSimulation EnvironmentsPrototype and Early Development LabsDevelopment Support Test LabsIntegration LabsPre-Product and Product Release (Full Test Lab)Field LabsOther Places Labs Can Be RealizedDeveloping Labs: A Project inside of a ProjectPlanning LabsRequirement Considerations for LabsFunctional Elements for a Developer Support LabFunctional Elements for a Software Test LabTest Lab Design FactorsLab ImplementationLab CertificationOperations and Maintenance in the LabLab Lessons LearnedAutomation Concepts for Test LabsTooling to Support Lab WorkTest Data Set-UpTest Execution: For Developer TestingTest Execution: GeneralProduct and Security Analysis ToolsTools for the Lab Test Results RecordingPerformance Attack ToolingBasic and Generic Test Support ToolsAutomation: Test Oracles for the Lab Using Modeling ToolsSimulation, Stimulation, and Modeling in the Lab Test BedContinuous Real-Time, Closed-Loop Simulations to Support Lab Test EnvironmentsKeyword-Driven Test Models and EnvironmentsData Collection, Analysis, and ReportingPostTest Data AnalysisPostTest Data ReportingWrap Up: N-Version Testing Problems in Labs and ModelingFinal Thoughts: Independence, Blind Spots, and Test Lab StaffingExercises (Answers Are on My Website)References
Chapter 12 - Some Parting Advice
Are We There Yet?Will You Get Started Today?Advice for the “Never Ever” TesterBug Database, Taxonomies, and Learning from Your HistoryLessons Learned and RetrospectivesImplementing Software Attack PlanningRegression and RetestWhere Do You Go from Here?Exercises (Answers Are on My Website)References
Appendix A: Mobile and Embedded Error Taxonomy: A Software Error Taxonomy (for Testers)
IntroductionCharacteristics of the Enemy: A TaxonomySummary of the Taxonomy TableSome Details and ImplicationsWhere Did the Data Come From?What Does the Taxonomy Indicate?Changing the Face of Mobile and Embedded SoftwareSummaryReferences
Appendix B: Mobile and Embedded Coding Rules
Coding Guidance (to Be Followed) and the Evil of Code (to Be Avoided)Website
Appendix C: Quality First: “Defending the Source Code So That Attacks Are Not So Easy”
IntroductionWhy Would Anyone Want to Make Testing Harder?Who Should Do This?When to Apply This AttackHow to Conduct This AttackStandards and Commonality: The Dark Side of Commercial or Third-Party Software, Code Reuse, and Operating SystemsOff-the-Shelf and Software ReuseEveryone Hates Doing Documentation but Surely Misses It When They Need ItIs Testing Dead?Summary: The P Word: Processes and StandardsBibliography
Appendix D: Basic Timing Concepts
Basic Timing Concepts and TermsImpacts of Timing
Appendix E: Detailed Mapping of Attacks
Appendix F: UI/GUI and Game Evaluation Checklist
Checklist of Usability Factors and CriteriaReferences
Appendix G: Risk Analysis, FMEA, and Brainstorming
FMEA/FMECABrainstorming (Organized)References
References
References and Additional ReadingBooks on My Bookshelf and Many Used as ReferencesSampling of Standards That Testers Should Be Familiar With (Used in the Production of This Book)Tool Information (To Name Only a Few)Mobile Embedded News and WebsitesIndustry Communication Standards and Standard Location Websites (To Name Only a Few)
Glossary
Term Definition and/or Reference

Overview

This book presents an attack basis for testing mobile and embedded systems in "smart" devices. It explains patterns and techniques ranging from simple mind mapping to sophisticated test labs. For traditional testers moving into the mobile and embedded area, the book bridges the gap between IT and mobile/embedded system testing. It illustrates how to apply both traditional and new approaches. For those working with mobile/embedded systems without an extensive background in testing, the book brings together testing ideas, techniques, and solutions that are immediately applicable to testing smart and mobile devices.

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9781466575318

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills