Advertisement

Critical Infrastructure Protection and Information Security

Chapter

Abstract

One morning on a brisk fall day in early November, technicians at the Springfield Nuclear Power Plant notice a malfunctioning steam release valve on Cooling Tank One. A mechanical problem was discovered in a leaky seal that had been recently patched. No one thought to check the plant’s supervisory control and data acquisition (SCADA) system, which controls the cooling function for the plant. Technicians quickly recognized the leaky seal and corrected the problem without any impact on the plant’s overall operation. Shortly after the repair a similar situation is discovered in Cooling Tanks Two and Three. This time the technicians did not discover any mechanical failures and did not recognize the significance in reoccurring events. It is not until an examination of the SCADA system that the problem is diagnosed; the automated software has given the command to close the valves in Cooling Tanks Two and Three when hot air should have been vented. How did this occur? Only authorized plant employees have access to the software, which is password protected.

Keywords

Critical Infrastructure Homeland Security Infrastructure Protection Emergency Operation Center Critical Infrastructure Protection 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Baker, George. 2004. Critical infrastructure protection program workshop I working papers. George Mason University Press.Google Scholar
  2. Barnes, Joshua and Newbold, Kenneth. 2005. Humans as a critical infrastructure. IEEE Critical Infrastructure Protection Conference.Google Scholar
  3. Deaton, Michael. 2004. Critical infrastructure protection program workshop I working papers. George Mason University Press.Google Scholar
  4. Department of Homeland Security. 2005a. Interim National Infrastructure Protection Plan. Washington, D.C.Google Scholar
  5. Department of Homeland Security. 2005b. Strategic plan. <http://www.dhs.gov/interweb/assetlibrary/DHS_StratPlan_FINAL_spread.pdf>.
  6. Department of Homeland Security. 2006. <http://www.dhs.gov>.
  7. Office of Homeland Security. 2002. National strategy for homeland security. Washington, D.C. U.S.-Canada Power System Outage Task Force. 2004. Final report on the August 14, 2003 blackout in the United States and Canada: Causes and recommendations.Google Scholar
  8. USA PATRIOT Act. 2001. 42 USC 5195c(e).Google Scholar
  9. The White House. 1997. Critical foundations: Protecting America’s infrastructures. Washington, D.C.Google Scholar
  10. The White House. 1998. Presidential Decision Directive 63. Washington, D.C.Google Scholar
  11. The White House. 2003a. National strategy to secure cyberspace. Washington, D.C.Google Scholar
  12. The White Houses. 2003b. National Strategy for physical protection of critical infrastructures and key assets. Washington, D.C.Google Scholar

Copyright information

© John B. Noftsinger, Jr., Kenneth F. Newbold, Jr., and Jack K. Wheeler 2007

Authors and Affiliations

There are no affiliations available

Personalised recommendations