|
|
|
|
| LEADER |
04081nmm a2200505 u 4500 |
| 001 |
EB001926059 |
| 003 |
EBX01000000000000001088961 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
210123 ||| eng |
| 020 |
|
|
|a 9781491917800
|
| 050 |
|
4 |
|a QA76.9.F34
|
| 100 |
1 |
|
|a Schnepp, Rob
|
| 245 |
0 |
0 |
|a Incident management for operations
|c Rob Schnepp, Ron Vidal, and Chris Hawley
|
| 250 |
|
|
|a First edition
|
| 260 |
|
|
|a Sebastopol, CA
|b O'Reilly Media
|c 2017
|
| 300 |
|
|
|a 1 online resource
|
| 505 |
0 |
|
|a Copyright; Table of Contents; Foreword; Preface; Conventions Used in This Book; O'Reilly Safari; How to Contact Us; Acknowledgments; Chapter 1. Evaluating the Incident Response PROCESS; Summary; Chapter 2. The Incident Management System (IMS); Overview of Incident Command; The Culture of Incident Response; Common Terminology for Job Functions; Summary; Chapter 3. The Incident Commander (IC); Resolving the Incident; Communication Methods; Developing the Incident Action Plan; Size Up the Incident; Triage; Act; Review; It's All About TIME; Tone; Interaction; Management; Engagement; Summary
|
| 505 |
0 |
|
|a AAR Case Study: The New SMEIssue Identified During the AAR; Change Recommendations from the AAR; Summary; Index; About the Authors
|
| 505 |
0 |
|
|a Chapter 4. Scaling the Incident ResponseIncident Response and Escalation; Span of Control; Transfer of Command; Summary; Chapter 5. Unified Command (UC); UC in Action; The UC Planning Wheel; Planning Wheel in Action; UC Org Chart; UC Case Study; Launching UC: The Programmatic Backend; Key UC Positions and Checklists; Summary; Chapter 6. After Action Review (AAR); The Name Is Important; AAR as an Integrated Effort; AAR Documentation and Data Collection; Documenting an Incident: A Case Study; Timeline; Case Study AAR; Training; Accountability; Leadership; Empowerment; Notification; Trust
|
| 653 |
|
|
|a Computer security
|
| 653 |
|
|
|a COMPUTERS / Computer Science / bisacsh
|
| 653 |
|
|
|a Sécurité informatique
|
| 653 |
|
|
|a Pannes système (Informatique)
|
| 653 |
|
|
|a Computer system failures / fast
|
| 653 |
|
|
|a Computer system failures / http://id.loc.gov/authorities/subjects/sh98002500
|
| 653 |
|
|
|a COMPUTERS / Hardware / General / bisacsh
|
| 653 |
|
|
|a COMPUTERS / Data Processing / bisacsh
|
| 653 |
|
|
|a COMPUTERS / Reference / bisacsh
|
| 653 |
|
|
|a COMPUTERS / Computer Literacy / bisacsh
|
| 653 |
|
|
|a COMPUTERS / Machine Theory / bisacsh
|
| 653 |
|
|
|a Computer security / fast
|
| 653 |
|
|
|a COMPUTERS / Information Technology / bisacsh
|
| 700 |
1 |
|
|a Vidal, Ron
|e author
|
| 700 |
1 |
|
|a Hawley, Chris
|e author
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 500 |
|
|
|a Includes index
|
| 776 |
|
|
|z 1491917806
|
| 776 |
|
|
|z 9781491917800
|
| 776 |
|
|
|z 9781491917626
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781491917619/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 500
|
| 082 |
0 |
|
|a 004.068
|
| 520 |
|
|
|a Are you satisfied with the way your company responds to IT incidents? How prepared is your response team to handle critical, time-sensitive events such as service disruptions and security breaches? IT professionals looking for effective response models have successfully adopted the Incident Management System (IMS) used by firefighters throughout the US. This practical book shows you how to apply the same response methodology to your own IT operation. You'll learn how IMS best practices for leading people and managing time apply directly to IT incidents where the stakes are high and outcomes are uncertain. This book provides use cases of some of the largest (and smallest) IT operations teams in the world. There is a better way to respond. You just found it. Assess your IT incident response with the PROCESS programmatic evaluation tool Get an overview of the IMS all-hazard, all-risk framework Understand the responsibilities of the Incident Commander Form a unified command structure for events that affect multiple business units Systematically evaluate what broke and how the incident team responded
|