Critical infrastructure protection

Critical infrastructure protection (CIP) is a concept that relates to the preparedness and response to serious incidents that involve the critical infrastructure of a region or nation.

The American Presidential directive PDD-63 of May 1998 set up a national program of "Critical Infrastructure Protection".[1]

In Europe the equivalent "European Programme for Critical Infrastructure Protection" (EPCIP) refers to the doctrine or specific programs created as a result of the European Commission's directive EU COM(2006) 786 which designates European critical infrastructure that, in case of fault, incident, or attack, could impact both the country where it is hosted and at least one other European Member State. Member states are obliged to adopt the 2006 directive into their national statutes.

History of the U.S. CIP

The U.S. CIP is a national program to ensure the security of vulnerable and interconnected infrastructures of the United States. In May 1998, President Bill Clinton issued Presidential directive PDD-63 on the subject of Critical Infrastructure Protection.[1] This recognized certain parts of the national infrastructure as critical to the national and economic security of the United States and the well-being of its citizenry, and required steps to be taken to protect it.

This was updated on December 17, 2003, by President Bush through Homeland Security Presidential Directive HSPD-7 for Critical Infrastructure Identification, Prioritization, and Protection.[2] The directive describes the United States has having some critical infrastructure that is "so vital to the United States that the incapacity or destruction of such systems and assets would have a debilitating impact on security, national economic security, national public health or safety."[2]

Overview

The systems and networks that make up the infrastructure of society are often taken for granted, yet a disruption to just one of those systems can have dire consequences across other sectors.

Take, for example, a computer virus that disrupts the distribution of natural gas across a region. This could lead to a consequential reduction in electrical power generation, which in turn leads to the forced shutdown of computerized controls and communications. Road traffic, air traffic, and rail transportation might then become affected. Emergency services might also be hampered.

An entire region can become debilitated because some critical elements in the infrastructure become disabled through natural disaster. While potentially in contravention of the Geneva Conventions,[3] military forces have also recognized that it can cripple an enemy's ability to resist by attacking key elements of its civilian and military infrastructure.

The federal government has developed a standardized description of critical infrastructure, in order to facilitate monitoring and preparation for disabling events. The government requires private industry in each critical economic sector to:

Infrastructure sectors

CIP defines sectors and organizational responsibilities in a standard way:

Oklahoma City bombing: Search and rescue teams formed from various emergency services coordinated by FEMA

In 2003 the remit was expanded to include:

With much of the critical infrastructure privately owned, the Department of Defense (DoD) depends on commercial infrastructure to support its normal operations. The Department of State and the Central Intelligence Agency are also involved in foreign affairs and intelligence analysis with friendly countries.

In May 2007 the DHS completed its sector-specific plans (SSP) for coordinating and dealing with critical events.[5] the Continuity of government (COG) in time of a catastrophic event can be used to preserve the government as seen fit by the president, at which point the welfare of the government can be placed above the welfare of the citizenry of the United States ensuring that the government is preserved to rebuild the economy and country when it is deemed safe to return to the surface of the United States of America.

Significance

On March 9, 1999, Deputy Defense Secretary John Hamre warned the United States Congress of a cyber terrorist "electronic Pearl Harbor" saying, "It is not going to be against Navy ships sitting in a Navy shipyard. It is going to be against commercial infrastructure". Later this fear was qualified by President Clinton after reports of actual cyber terrorist attacks in 2000: "I think it was an alarm. I don't think it was Pearl Harbor. We lost our Pacific fleet at Pearl Harbor. I don't think the analogous loss was that great.[6]"

There are many examples of computer systems that have been hacked or victims of extortion. One such example occurred in September 1995 where a Russian national allegedly masterminded the break-in of Citicorp's electronic funds transfer system and was ordered to stand trial in the United States. A gang of hackers under his leadership had breached Citicorp's security 40 times during 1994. They were able to transfer $12 million from customer accounts and withdraw an estimated $400,000.

In the past, the systems and networks of the infrastructure elements were physically and logically independent and separate. They had little interaction or connection with each other or other sectors of the infrastructure. With advances in technology, the systems within each sector became automated, and interlinked through computers and communications facilities. As a result, the flow of electricity, oil, gas, and telecommunications throughout the country are linked—albeit sometimes indirectly—but the resulting linkages blur traditional security borders.

While this increased reliance on interlinked capabilities helps make the economy and nation more efficient and perhaps stronger, it also makes the country more vulnerable to disruption and attack. This interdependent and interrelated infrastructure is more vulnerable to physical and cyber disruptions because it has become a complex system with single points of failure. In the past an incident that would have been an isolated failure can now cause widespread disruption because of cascading effects.[7] As an example, capabilities within the information and communication sector have enabled the United States to reshape its government and business processes, while becoming increasingly software driven. One catastrophic failure in this sector now has the potential bring down multiple systems including air traffic control, emergency services, banking, trains, electrical power, and dam control.

The elements of the infrastructure themselves are also considered possible targets of terrorism. Traditionally, critical infrastructure elements have been lucrative targets for anyone wanting to attack another country. Now, because the infrastructure has become a national lifeline, terrorists can achieve high economic and political value by attacking elements of it. Disrupting or even disabling the infrastructure may reduce the ability to defend the nation, erode public confidence in critical services, and reduce economic strength. Additionally, well chosen terrorist attacks can become easier and less costly than traditional warfare because of the interdependence of infrastructure elements. These infrastructure elements can become easier targets where there is a low probability of detection.

The elements of the infrastructure are also increasingly vulnerable to a dangerous mix of traditional and nontraditional types of threats. Traditional and non-traditional threats include equipment failures, human error, weather and natural causes, physical attacks, and cyber attacks. For each of these threats, the cascading effect caused by single points of failure has the potential to pose dire and far-reaching consequences.

Challenges

There are fears that the frequency and severity of critical infrastructure incidents will increase in the future.[8]

Although efforts are under way, there is no unified national capability to protect the interrelated aspects of the country's infrastructure. One reason for this is that a good understanding of the inter-relationships does not exist. There is also no consensus on how the elements of the infrastructure mesh together, or how each element functions and affects the others. Securing national infrastructure depends on understanding the relationships among its elements. Thus when one sector scheduled a three-week drill to mimic the effects of a pandemic flu, even though two-thirds of the participants claimed to have business continuity plans in place, barely half reported that their plan was moderately effective.[9]

Critical infrastructure protection requires the development of a national capability to identify and monitor the critical elements and to determine when and if the elements are under attack or are the victim of destructive natural occurrences. CIP is important because it is the link between risk management and infrastructure assurance. It provides the capability needed to eliminate potential vulnerabilities in the critical infrastructure.

CIP practitioners determine vulnerabilities and analyze alternatives in order to prepare for incidents. They focus on improving the capability to detect and warn of impending attacks on, and system failures within, the critical elements of the national infrastructure.

Organization and structure

PDD-63 mandated the formation of a national structure for critical infrastructure protection. To accomplish this one of the primary actions was to produce a National Infrastructure Assurance Plan, or NIAP, later renamed National Infrastructure Protection Plan or NIPP.

The different entities of the national CIP structure work together as a partnership between the government and the public sectors. Each department and agency of the federal government is responsible for protecting its portion of the government's critical infrastructure. In addition, there are grants made available through the Department of Homeland Security for municipal and private entities to use for CIP and security purposes. These include grants for emergency management, water security training, rail, transit and port security, metropolitan medical response, LEA terrorism prevention programs and the Urban Areas Security Initiative.[10]

PDD-63 identified certain functions related to critical infrastructure protection that must be performed chiefly by the federal government. These are national defense, foreign affairs, intelligence, and law enforcement. Each lead agency for these special functions appoints a senior official to serve as a functional coordinator for the federal government. In 2008 a mobile PDA-based Vulnerability Assessment Security Survey Tool (VASST) was introduced to speed physical security assessment of critical infrastructure by law enforcement to meet compliance requirements of PDD-63.[11]

National Infrastructure Assurance Plan / National Infrastructure Protection Plan

For each of the identified major sectors of the critical infrastructure, the federal government appointed a Sector Liaison Official from a designated Lead Agency. A private sector counterpart, a Sector Coordinator, was also identified. Together, the two sector representatives, one federal government and one corporate, were responsible for developing a sector NIAP.

In addition, each department and agency of the federal government was responsible for developing its own CIP plan for protecting its portion of the federal government's critical infrastructure. The federal department and agency plans were assimilated with the sector NIAPs to create one comprehensive National Infrastructure Assurance Plan. Additionally the national structure must ensure there is a national CIP program. This program includes responsibilities such as education and awareness, threat assessment and investigation, and research.

The process includes assessments of:

Controversy

There have been public criticisms of the mechanisms and implementation of some security initiatives and grants, with claims they are being led by the same companies who stand to benefit,[12] and that they are encouraging an unnecessary culture of fear. Commentators note that these initiatives started directly after the collapse of the Cold War, raising the concern that this was simply a diversion of the military-industrial complex away from a funding area which was shrinking and into a richer previously civilian arena.

Grants have been distributed across the different states even though the perceived risk is not evenly spread, leading to accusations of pork barrel politics that directs money and jobs towards marginal voting areas. The Urban Areas Security Initiative grant program has been particularly controversial, with the 2006 infrastructure list covering 77,000 assets, including a popcorn factory and a hot dog stand.[13] The 2007 criteria were reduced to 2,100 and now those facilities must make a much stronger case to become eligible for grants.[14] While well-intentioned, some of the results have also been questioned regarding claims of poorly designed and intrusive security theater that distracts attention and money from more pressing issues or creates damaging side effects.

An absence of comparative risk analysis and benefits tracking it has made it difficult to counter such allegations with authority. In order to better understand this, and ultimately direct effort more productively, a Risk Management and Analysis Office was recently created in the National Protection and Programs directorate at the Department of Homeland Security.

Department of Defense and CIP

The U.S. Department of Defense is responsible for protecting its portion of the government's critical infrastructure. But as part of the CIP program, DoD has responsibilities that traverse both the national and department-wide critical infrastructure.

PDD-63 identified the responsibilities DoD had for critical infrastructure protection. First, DoD had to identify its own critical assets and infrastructures and provide assurance through analysis, assessment, and remediation. DoD was also responsible for identifying and monitoring the national and international infrastructure requirements of industry and other government agencies, all of which needed to be included in the protection planning. DoD also addressed the assurance and protection of commercial assets and infrastructure services in DoD acquisitions. Other DoD responsibilities for CIP included assessing the potential impact on military operations that would result from the loss or compromise of infrastructure service. There were also requirements for monitoring DoD operations, detecting and responding to infrastructure incidents, and providing department indications and warnings as part of the national process. Ultimately, DoD was responsible for supporting national critical infrastructure protection.

In response to the requirements identified in PDD-63, DoD categorized its own critical assets by sector, in a manner similar to the national CIP organization. The DoD identified a slightly different list of infrastructure sectors for those areas that specifically required protection by DoD. DoD’s organizational structure for critical infrastructure protection reflects, complements, and effectively interacts with the national structure for CIP.

DoD sectors

There are ten defense critical infrastructure sectors that are protected by the DoD. These include:

DoD special functions

The DoD CIP special function components interface with the equivalent national functional coordinators and coordinate all activities related to their function within DoD.

DoD’s special function components currently include seven areas of focus. They include the following components:

DoD CIP lifecycle

As mandated by PDD-63, the DoD must protect its portion of the federal government's critical infrastructure. For DoD, this is the Defense Infrastructure or DI. Protecting the Defense Infrastructure is a complex task involving ten defense sectors.

It was deemed that it was nearly impossible to protect every critical asset at every location, therefore the focus was directed on protecting the critical Defense Infrastructure. The critical Defense Infrastructure is the critical assets essential to providing mission assurance.

Six phases

The six phases of the DoD CIP life cycle build on one another to create a framework for a comprehensive solution for infrastructure assurance. The life cycle phases occur before, during, and after an event that may compromise or degrade the infrastructure. A synopsis of the six phases are:

Effective management of the CIP life cycle ensures that protection activities can be coordinated and reconciled among all DoD sectors. In many ways, DoD CIP, is risk management at its most imperative. Achieving success means obtaining mission assurance. Missing the mark can mean mission failure as well as human and material losses. For critical infrastructure protection, risk management requires leveraging resources to address the most critical infrastructure assets that are also the most vulnerable and that have the greatest threat exposure.

The most important part of the CIP lifecycle is Phase 1. Because it is crucial to target the right assets for infrastructure protection, determining these assets is the first phase in the CIP life cycle. This phase, Analysis and Assessment, is the key and foundation of the seven lifecycle activities. Without a solid foundation, the remaining CIP life cycle phases may be flawed, resulting in a CIP plan that fails to protect the critical infrastructure and, therefore, mission assurance.

Phase 1: Analysis and Assessment

Phase 1 determines what assets are important, and identifies their vulnerabilities, and dependencies so that decision makers have the information they need to make effective risk management choices.

The Defense Infrastructure, or DI, is organized into ten sectors. Each sector is composed of assets, such as systems, programs, people, equipment, or facilities. Assets may be simple, such as one facility within one geographic location, or complex, involving geographically dispersed links and nodes.

The Analysis and Assessment is made up of five steps that include activities that span and encompass the ten DI sectors and their assets.

Phase 1 example in the “Real World”

On August 24, 2001, the Director of the Joint Staff requested USPACOM to serve as the lead support Combatant Command for creating a CIP first-ever theater CIP Plan – known as the “CIP Appendix 16 Plan”. The following is how USPACOM approached the task. USPACOM focused the Analysis and Assessment phase by organizing its activities to answer three major questions:

To answer the question, “What is critical?”, USPACOM outlined a three-step procedure:

To accomplish these steps, USPACOM adopted a methodology that focuses its CIP efforts on Tier 1 assets. Tier 1 assets are assets that could cause mission failure if they are compromised or damaged. The methodology UAPACOM adopted and modified is Mission Area Analysis, or MAA. The MAA links combatant command missions to infrastructure assets that are critical to a given Operations Plan, or OPLAN, Contingency Plan, or CONPLAN, or Crisis Action Plan. Typically, the MAA process determines the assessment site priorities. USPACOM modified the process and selected the CIP assessment sites and installations prior to conducting the MAA. The following is an illustration of the USPACOM MAA process:

USPACOM uses the MAA data it gathers to scope and focus its efforts on truly mission-critical assets to answer the next question in its process, Is it vulnerable?

The first step in answering this question is to complete an installation analysis. The next step is to complete a commercial infrastructure analysis. USPACOM relied upon two different DoD organizations for CIP assessments: Balanced Survivability Assessments, or BSAs, and Mission Assurance Assessments. The BSA is a two-week mission-focused assessment at a military installation or designated site. A Mission Assurance Assessment is unique because it uses an area assessment approach to focus on both commercial and military asset vulnerabilities and dependencies. The final step to determine vulnerabilities is to integrate the two analyses and assessments. With its critical assets and their vulnerabilities identified, USPACOM is ready to perform risk management activities to decide what can be done to protect the mission-critical assets.

Booz Allen Hamilton developed this process at PACOM.

Phase 2: Remediation

The first phase of the CIP life cycle, Analysis and Assessment, identified the critical assets of DoD sector infrastructures and the vulnerabilities or weaknesses of those critical assets.

The second phase is the Remediation phase. In the Remediation phase, the known weaknesses and vulnerabilities are addressed. Remediation actions are deliberate, precautionary measures designed to fix known virtual and physical vulnerabilities before an event occurs. The purpose of remediation is to improve the reliability, availability, and survivability of critical assets and infrastructures. Remediation actions apply to any type of vulnerability, regardless of its cause. They apply to acts of nature, technology failures, or deliberate malicious actions.

The cost of each remediation action depends on the nature of the vulnerability it addresses. The Defense Infrastructure Sector Assurance Plan that each infrastructure sector must develop, establishes the priorities and resources for remediation. Remediation requirements are determined by multiple factors. These are analysis and assessment, input from military planners and other DoD sectors, the National Infrastructure Assurance Plan and other plans, reports, and information on national infrastructure vulnerabilities and remediation, as well as intelligence estimates and assessments of threats.

Remediation requirements are also gathered through lessons learned from Defense Infrastructure sector monitoring and reporting and infrastructure protection operations and exercises. The CIP program tracks the status of remediation activities for critical assets. Remediation activities to protect the critical Defense Infrastructure cross multiple Department components.

Phase 3: Indications and warnings

The need to monitor activities and warn of potential threats to the United States is not new. From conventional assaults to potential nuclear attacks, the military has been at the forefront of monitoring and warning of potential dangers since the founding of the country. Protecting the security and well being of the United States, including the critical Defense Infrastructure, has now entered a new era. It has been deemed essential to have a coordinated ability to identify and warn of potential or actual incidents among critical infrastructure domains. The ability to detect and warn of infrastructure events is the third phase of the critical infrastructure protection life cycle, the Indications and Warnings phase.

Indications and warnings are actions or infrastructure conditions that signal an event is either”

Historically, DoD event indications have focused and relied on intelligence information about foreign developments. These event indications have been expanded to include all potential infrastructure disruption or degradation, regardless of its cause. DoD CIP indications are based on four levels of input:

This fusion of traditional intelligence information with sector-specific information has been determined to be essential for meaningful CIP indications.

If an indication is detected, a warning notifying the appropriate asset owners of a possible or occurring event or hazard can be issued. The sector’s assurance plan determines what conditions and actions are monitored and reported for each Defense Infrastructure Sector. Each sector must develop a written Defense Sector Assurance Plan that includes a compendium of sector incidents for monitoring and reporting. The sector incident compendium is made up of three types of incidents:

DoD critical asset owners, installations, and sector CIAOs determine the DoD and sector-defined incidents. Each of the reportable incidents or classes of incidents must include the following components:

The National Infrastructure Protection Center (NIPC) is the primary national warning center for significant infrastructure attacks. Critical asset owners, DoD installations, and Sector CIAOs monitor the infrastructure daily. Indications of an infrastructure incident are reported to the National Military Command Center, or NMCC. If indications are on a computer network, they are also reported to the Joint Task Force Computer Network Operations (JTF-CNO). The NMCC and JTF-CNO assess the indications and pass them to the NIPC and appropriate DoD organizations. When the NIPC determines that an infrastructure event is likely to occur, is planned, or is under way, it issues a national warning. For DoD, the NIPC passes its warnings and alerts to the NMCC and JTF-CNO. These warnings and alerts are then passed to the DoD components. The warning may include guidance regarding additional protection measures DoD should take.

Phase 4: Mitigation

Phase 1 of the CIP life cycle provided a layer of protection by identifying and assessing critical assets and their vulnerabilities. Phase 2 provided another layer of protection by remediating or improving the identified deficiencies and weaknesses of an asset. Even with these protections and precautions, an infrastructure incident was still possible. When it does the Indications and Warnings phase goes into effect.

The Mitigation phase (Phase 4), is made up of preplanned coordinated actions in response to infrastructure warnings or incidents. Mitigation actions are taken before or during an infrastructure event. These actions are designed to minimize the operational impact of the loss of a critical asset, facilitate incident response, and quickly restore the infrastructure service.

A primary purpose of the Mitigation phase is to minimize the operational impact on other critical Defense Infrastructures and assets when a critical asset is lost or damaged. As an example, if there is a U.S. installation, Site A, located in a host nation. Site A is a tier 1 asset, meaning that if it fails, the Combatant Commands mission fails. Site A has mutual Global Information Grid Command Control (GIG/C2), information interdependencies with Sites B and C. In addition, other Defense Infrastructure sectors rely on Site A for mission capabilities. In this scenario, what could be the impact if the supply line to the commercial power plant that provides the installation’s primary power is accidentally severed. Because of all the interdependencies, losing this asset is more than the loss of just one site. It means the loss of other sector capabilities.

A possible mitigation action might be for Site A to go on backup power. An alternate action could be to pass complete control of Site A’s functionality to another site, where redundancy has been previously arranged. These actions would limit the impact of this incident on the other sites and related sectors. In addition to lessening the operational impact of a critical infrastructure event, the Mitigation phase of the CIP life cycle supports and complements two other life cycle phases. Mitigation actions aid in the emergency, investigation, and management activities of Phase 5, Incident Response. They also facilitate the reconstitution activities of Phase 6.

During the Mitigation phase, DoD critical asset owners, DoD installations, and Sector Chief Infrastructure Assurance Officers, or CIAOs, work with the National Military Command Center (NMCC) and the Joint Task Force-Computer Network Operations (JTF-CNO) to develop, train for, and exercise mitigation responses for various scenarios. When there is a warning, emergency, or infrastructure incident, the critical asset owners, installations, and Sector CIAOs initiate mitigation actions to sustain service to the DoD. They also provide mitigation status information to the NMCC and JTF-CNO. The NMCC monitors for consequences from an event within one Defense Infrastructure sector that are significant enough to affect other sectors. For events that cross two or more sectors, the NMCC advises on the prioritization and coordination of mitigation actions. When event threats or consequences continue to escalate, the NMCC directs mitigation actions by sector to ensure a coordinated response across the DoD. The NMCC and the JTF-CNO keep the National Infrastructure Protection Center, or NIPC, apprised of any significant mitigation activities.

Phase 5: Incident response

When an event affects the Defense Infrastructure, the Incident Response phase begins. Incident Response is the fifth phase of the CIP life cycle. The purpose of the Incident Response phase is to eliminate the cause or source of an infrastructure event. For example, during the 9/11 attacks on the World Trade Center and Pentagon, all non-military airplanes were grounded over the United States to prevent further incidents. Response activities included emergency measures, not from the asset owners or operators, but from dedicated third parties such as law enforcement, medical rescue, fire rescue, hazardous material or explosives handling, and investigative agencies. Response to Defense Infrastructure incidents can take one of two paths depending on whether or not the event affects a DoD computer network.

When incidents compromise a DoD computer network, the Joint Task Force-Computer Network Operations (JTF-CNO) directs the response activities. These activities are designed to stop the computer network attack, contain and mitigate damage to a DoD information network and then restore minimum required functionality. JTF-CNO also requests and coordinates any support or assistance from other Federal agencies and civilian organizations during incidents affecting a DoD network. When incidents impact any other DoD owned assets, installation commanders and critical asset owners follow traditional channels and procedures to coordinate responses. This includes notifying affected Sector Chief Infrastructure Assurance Officers, or CIAOs, in the initial notice and status reporting. Although third parties play a major role in the response to Defense Infrastructure events, DoD CIP personnel also have responsibilities to fulfill.

Phase 6: Reconstitution

After the source or cause of an infrastructure event is eliminated or contained, the infrastructure and its capabilities must be restored. Reconstitution is the last phase of the critical infrastructure protection. Reconstitution is probably the most challenging and least developed process of the life cycle. DoD critical asset owners have the major responsibility for reconstitution.

International Perspective Of Critical Infrastructure Protection

Internet is full of unprotected and unsafe devices, SCADA systems and computers making critical infrastructures vulnerable to cyber attacks.[16] Further, conflict of laws in cyberspace[17] is a major hurdle before global critical infrastructure protection efforts. There is no global cyber law[18] and cyber security treaty[19] that can be invoked for enforcing global cyber security issues.

International legal issues of cyber attacks[20] are really tricky and complicated in nature.[21] For instance, even if a cyber attack is traced back to a particular jurisdiction, authorship attribution for cyber crimes and cyber attacks has become a major problem for international law enforcement agencies.[22]

India

Critical infrastructure protection in India [23] is facing many problems and challenges. Indian cyber security initiatives are grossly deficient [24] and they need to be improved. For instance, critical infrastructures like automated power grids [25] are facing cyber security challenges.[26] Similar is the position regarding Indian satellites [27] and other critical infrastructures that require immediate attention of Indian government. There is also no critical ICT infrastructure protection policy in India.[28] It has now been realised that critical infrastructure protection in India is needed.[29]

Indian government has also discussed few good projects in this direction. For instance, a national critical information infrastructure protection centre (NCIPC) of India [30] has been proposed by Indian government and it may become functional very soon.[31] Similarly, hints have been given regarding formulation of a tri service cyber command for armed forces of India [32] and cyber crisis management plan of India.[33] NTRO would protect [34] critical infrastructures like thermal power in India.[35] A national cyber security policy of India 2013 (NCSP 2013) has also been prescribed by Indian government but it has not become functional till now.[36]

See also

References

  1. ↑ 1.0 1.1 Presidential directive PDD-63
  2. ↑ 2.0 2.1 "December 17, 2003 Homeland Security Presidential Directive/Hspd-7". White House Archives. 17 December 2003. Retrieved 29 July 2014.
  3. ↑ Article 52 and 54 of the Protocol Additional to the Geneva Conventions of 12 August 1949, and relating to the Protection of Victims of International Armed Conflicts ("Geneva Conventions")
  4. ↑ Financial Services Information Sharing and Analysis Center
  5. ↑ Department of Homeland Security - Sector-Specific Plans
  6. ↑ Federation of American Scientists February 15, 2000 Presidential remarks on Computer Security
  7. ↑ Austen Givens, "Deepwater Horizon Oil Spill Is An Ominous Sign for Critical Infrastructure's Future", May 27, 2011.
  8. ↑ Paul J. Maliszewski, "Modeling Critical Vaccine Supply Location: Protecting Critical Infrastructure and Population in Central Florida" (2008)
  9. ↑ How Well Can Wall Street Handle Pandemic Flu? Drill Results Are Mixed Wall Street & Technology
  10. ↑ 2006 Catalog of Federal domestic assistance grants (CFDA), including security projects
  11. ↑ "Aegis Bleu Launches VASST, Vulnerability Assessment Security Survey Tool", PR Leap 11 September 2008.
  12. ↑ Elisa Williams, "Climate of Fear", Forbes magazine, 2 April 2002
  13. ↑ Eric Lipton, "Terror Target List", New York Times, July 12, 2006.
  14. ↑ Zack Phillips, "Security Theater," Government Executive, 1 August 2007.
  15. ↑ Critical Infrastructure Interdependency Wheel (CIIW) assessment tool
  16. ↑ "Internet Is Full Of Unprotected And Unsafe Devices, SCADA Systems And Computers". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 25 March 2013. Retrieved 11 September 2014.
  17. ↑ "Conflict Of Laws In Cyberspace, Internet And Computer Era". Conflict Of Laws In Cyberspace, Internet And Computer Era. 9 October 2013. Retrieved 11 September 2014.
  18. ↑ "International Cyber Law Treaty Is Required". Perry4Law Organisation’s Blog – An Exclusive And Global Techno Legal Knowledge Base. 10 October 2012. Retrieved 11 September 2014.
  19. ↑ "International Cyber Security Treaty Is Required". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 9 January 2014. Retrieved 11 September 2014.
  20. ↑ "International Legal Issues Of Cyber Attacks, Cyber Terrorism, Cyber Espionage, Cyber Warfare And Cyber Crimes". International And Indian Legal Issues Of Cyber Security. 11 March 2014. Retrieved 11 September 2014.
  21. ↑ "International Legal Issues Of Cyber Attacks And Indian Perspective". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 22 March 2014. Retrieved 11 September 2014.
  22. ↑ "Cross Border Cyber Attacks, Authorship Attribution And Cyber Crimes Convictions". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 29 March 2013. Retrieved 11 September 2014.
  23. ↑ "Critical Infrastructure Protection In India: The Problems, Challenges And Solutions". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 6 January 2014. Retrieved 11 September 2014.
  24. ↑ "India Is A Sitting Duck In The Cyberspace And Civil Liberties Protection Regime". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 2 July 2014. Retrieved 11 September 2014.
  25. ↑ "Cyber Security Of Automated Power Grids Of India". Global ICT Policies And Strategies And Indian Perspective. 23 November 2011. Retrieved 11 September 2014.
  26. ↑ "Power Grids Cyber Security In India And Its Challenges". Global ICT Policies And Strategies And Indian Perspective. 7 August 2012. Retrieved 11 September 2014.
  27. ↑ "Cyber Security Of Indian Satellites And Critical Infrastructure". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 23 February 2013. Retrieved 11 September 2014.
  28. ↑ "Critical ICT Infrastructure Protection Policy Of India". Global ICT Policies And Strategies And Indian Perspective. 3 June 2011. Retrieved 11 September 2014.
  29. ↑ "Critical Infrastructure Protection In India Is Needed". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 23 February 2013. Retrieved 11 September 2014.
  30. ↑ "National Critical Information Infrastructure Protection Centre (NCIPC) Of India". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 3 February 2013. Retrieved 11 September 2014.
  31. ↑ "National Cyber Coordination Centre (NCCC) Of India May Become Functional". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 20 January 2014. Retrieved 11 September 2014.
  32. ↑ "Tri Service Cyber Command For Armed Forces Of India In Pipeline". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 15 January 2014. Retrieved 11 September 2014.
  33. ↑ "Cyber Attacks Crisis Management Plan Of India". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 17 January 2014. Retrieved 11 September 2014.
  34. ↑ "NTRO Would Protect The Critical ICT Infrastructures Of India". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 13 January 2014. Retrieved 11 September 2014.
  35. ↑ "National Infrastructure Protection Plan In Thermal Power Sector Of India Proposed". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 8 March 2014. Retrieved 11 September 2014.
  36. ↑ "National Cyber Security Policy Of India 2013 (NCSP 2013)". Centre Of Excellence For Cyber Security Research And Development In India (CECSRDI). 26 December 2013. Retrieved 11 September 2014.

External links