20% Off - Limited time only. Exclusive web offer for individuals on print titles only. Terms & Conditions may apply.
Robert Radvanovsky, Jacob Brodsky
February 19, 2013
by CRC Press
Reference - 383 Pages - 17 B/W Illustrations
ISBN 9781466502260 - CAT# K14428
The availability and security of many services we rely upon—including water treatment, electricity, healthcare, transportation, and financial transactions—are routinely put at risk by cyber threats. The Handbook of SCADA/Control Systems Security is a fundamental outline of security concepts, methodologies, and relevant information pertaining to the supervisory control and data acquisition (SCADA) systems and technology that quietly operate in the background of critical utility and industrial facilities worldwide.
Divided into five sections, the book examines topics comprising functions within and throughout industrial control systems (ICS) environments. Topics include:
The final chapters outline the data relied upon for accurate processing, discusses emerging issues with data overload, and provides insight into the possible future direction of ISC security.
The book supplies crucial information for securing industrial automation/process control systems as part of a critical infrastructure protection program. The content has global applications for securing essential governmental and economic systems that have evolved into present-day security nightmares. The authors present a "best practices" approach to securing business management environments at the strategic, tactical, and operational levels.
Social Implications and Impacts
Introduction; Robert Radvanovsky
Sociological and Cultural Aspects; Jacob Brodsky
Threat Vectors; Jim Butterworth
Risk Management; Wayne Boone
Governance and Management
Disaster Recovery and Business Continuity of SCADA; Steven Young
Incident Response and SCADA; Steven Young
Forensics Management; Craig Wright
Governance and Compliance; Wayne Boone
Architecture and Modeling
Communications and Engineering Systems; Jacob Brodsky
Metrics Framework for a SCADA System; Robert Radvanovsky
Network Topology and Implementation; Jacob Brodsky
Commissioning and Operations
Obsolescence and Procurement of SCADA; Bernie Pella
Patching and Change Management; Bernie Pella
Physical Security Management; Allan McDougall and Jeff Woodruff
Tabletop/Red-Blue Exercises; Robert Radvanovsky
Integrity Monitoring; Craig Wright
Data Management and Records Retention; Jacob Brodsky
Conclusion and References
The Future of SCADA and Control Systems Security; Robert Radvanovsky
Appendix A—Listing of Online Resources SCADA/Control Systems
Appendix B—Terms and Definitions
I wish that each SCADA developer read this book while developing the software, as the focus on functionality is remarkable in this collection. It explains in an easy way what happens when ‘there are some security and reliability issues around’ and what should be remembered so that it does not appear again. Every aspect is well described with clear examples.
—IEEE Communications Magazine
After Stuxnet, everything has changed in the automation industry. Computer worms devastating power plants and many other sites reminded people managing industrial control systems (ICS) that they are equally as vulnerable as standard IT systems. The book edited by Radvanovsky and Brodsky provides, in a collection of various contributions, a thorough guide on how to design supervisory control and data acquisition (SCADA) systems to prevent most security hazards, what to take into consideration while implementing various methods of authentication, and how to prepare and respond efficiently in case of ICS faults.
The book consists of five sections divided into eighteen compact chapters describing all the aspects of risks and assets related to designing and maintaining ICS. ... In short, it is a guidebook on good (automated) security practice. I wish that each SCADA developer read this book while developing the software, as the focus on functionality is remarkable in this collection. It explains in an easy way what happens when ‘there are some security and reliability issues around’ and what should be remembered so that it does not appear again.
—Robert Wojcik writing in IEEE Communications Magazine, May 2014