10.07.2015 Views

GAO-08-1157T Critical Infrastructure Protection: DHS Needs to ...

GAO-08-1157T Critical Infrastructure Protection: DHS Needs to ...

GAO-08-1157T Critical Infrastructure Protection: DHS Needs to ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>GAO</strong>For Release on DeliveryExpected at 2:00 p.m. (EDT)Tuesday, September 16, 20<strong>08</strong>United States Government Accountability OfficeTestimonyBefore the Subcommittee on EmergingThreats, Cybersecurity, and Science andTechnology, Committee on HomelandSecurity, House of RepresentativesCRITICALINFRASTRUCTUREPROTECTION<strong>DHS</strong> <strong>Needs</strong> <strong>to</strong> BetterAddress Its CybersecurityResponsibilitiesStatement of David PownerDirec<strong>to</strong>r, Information Technology Management Issues<strong>GAO</strong>-<strong>08</strong>-<strong>1157T</strong>


Mr. Chairman and Members of the Subcommittee:Thank you for the opportunity <strong>to</strong> join in <strong>to</strong>day’s hearing <strong>to</strong> discussefforts in protecting our nation’s critical infrastructures fromcybersecurity threats. The recent computer-based, or cyber, attacksagainst nation-states and others demonstrate the potentiallydevastating impact these pose <strong>to</strong> systems and the operations andcritical infrastructures that they support. 1 They also highlight theneed <strong>to</strong> be vigilant against individuals and groups with maliciousintent, such as criminals, terrorists, and nation-states perpetuatingthese attacks.Today, I will discuss the Department of Homeland Security’s (<strong>DHS</strong>)progress in fulfilling its responsibilities <strong>to</strong> protect systems thatsupport critical infrastructures—a practice referred <strong>to</strong> as cybercritical infrastructure protection or cyber CIP—as well as itsprogress in addressing our related recommendations. Due <strong>to</strong>concerns about <strong>DHS</strong>’s efforts <strong>to</strong> fully implement its CIPresponsibilities as well as known security risks <strong>to</strong> criticalinfrastructure systems, we added cyber CIP as part of our federalinformation technology systems security high-risk area in 2003 andhave continued <strong>to</strong> report on its status since that time. 2As requested, my testimony will summarize our key reports—two ofwhich are being released <strong>to</strong>day at this hearing—and their associatedrecommendations aimed at securing our nation’s cyber criticalinfrastructure. Specifically, these reports and recommendationsfocus on (1) providing cyber analysis and warning capabilities, (2)being effectively organized <strong>to</strong> plan for and respond <strong>to</strong> disruptions on1<strong>Critical</strong> infrastructure is systems and assets, whether physical or virtual, so vital <strong>to</strong> theUnited States that their incapacity or destruction would have a debilitating impact onnational security, national economic security, national public health or safety, or anycombination of those matters. There are 18 critical infrastructure sec<strong>to</strong>rs: agriculture andfood, banking and finance, chemical, commercial facilities, communications, criticalmanufacturing, dams, defense industrial base, emergency services, energy, governmentfacilities, information technology, national monuments and icons, nuclear reac<strong>to</strong>rs,materials and waste, postal and shipping, public health and health care, transportationsystems, and water.2For our most recent high risk report, see <strong>GAO</strong>, High-Risk Series: An Update, <strong>GAO</strong>-07-310(Washing<strong>to</strong>n, D.C.: January 2007).Page 1


with national consequences. The coordinated attack created massoutages of its government and commercial Web sites. 7To address threats posed against the nation’s computer-reliantinfrastructures, federal law and policy establishes <strong>DHS</strong> as the focalpoint for cyber CIP. For example, within <strong>DHS</strong>, the AssistantSecretary of Cyber Security and Communications is responsible forbeing the focal point for national cyber CIP efforts. Under theAssistant Secretary is NCSD which interacts on a day-<strong>to</strong>-day basiswith federal and nonfederal agencies and organizations (e.g., stateand local governments, private-sec<strong>to</strong>r companies) regarding, amongother things, cyber-related analysis, warning, information sharing,major incident response, and national-level recovery efforts.Consequently, <strong>DHS</strong> has multiple cybersecurity-related roles andresponsibilities. In May 2005, we identified, and reported on, 13 keycybersecurity responsibilities called for in law and policy. 8 Theseresponsibilities are described in appendix I.Since then, we have performed detailed work and maderecommendations on <strong>DHS</strong>’s progress in fulfilling specific aspects ofthe responsibilities, as discussed in more detail later in thisstatement.In addition <strong>to</strong> <strong>DHS</strong> efforts <strong>to</strong> fulfill its cybersecurity responsibilities,the President in January 20<strong>08</strong> issued HSPD 23—also referred <strong>to</strong> asNational Security Presidential Directive 54 and the President’s“Cyber Initiative”—<strong>to</strong> improve <strong>DHS</strong> and the other federal agencies’cybersecurity efforts, including protecting against intrusionattempts and better anticipating future threats. 9 While the directive7Computer Emergency Response Team of Es<strong>to</strong>nia, “Malicious Cyber Attacks AgainstEs<strong>to</strong>nia Come from Abroad,” April 29, 2007, and Remarks by Homeland Security SecretaryMichael Cher<strong>to</strong>ff <strong>to</strong> the 20<strong>08</strong> RSA Conference, April 8, 20<strong>08</strong>.8<strong>GAO</strong>, <strong>Critical</strong> <strong>Infrastructure</strong> <strong>Protection</strong>: Department of Homeland Security FacesChallenges in Fulfilling Cybersecurity Responsibilities, <strong>GAO</strong>-05-434 (Washing<strong>to</strong>n, D.C.:May 26, 2005); <strong>Critical</strong> <strong>Infrastructure</strong> <strong>Protection</strong>: Challenges in AddressingCybersecurity, <strong>GAO</strong>-05-827T (Washing<strong>to</strong>n, D.C.: July 19, 2005); and <strong>Critical</strong> <strong>Infrastructure</strong><strong>Protection</strong>: <strong>DHS</strong> Leadership Needed <strong>to</strong> Enhance Cybersecurity. <strong>GAO</strong>-06-1<strong>08</strong>7T(Washing<strong>to</strong>n, D.C.: Sept. 13, 2006).9The White House, National Security Presidential Directive 54/Homeland SecurityPresidential Directive 23 (Washing<strong>to</strong>n, D.C.: Jan. 8, 20<strong>08</strong>).Page 5


has not been made public, <strong>DHS</strong> officials stated that the initiativeincludes steps <strong>to</strong> enhance cyber analysis related efforts, such asrequiring federal agencies <strong>to</strong> implement a centralized networkmoni<strong>to</strong>ring <strong>to</strong>ol and reduce the number of connections <strong>to</strong> theInternet.<strong>DHS</strong> <strong>Needs</strong> <strong>to</strong> Address Several Key Areas Associated with ItsCybersecurity ResponsibilitiesOver the last several years, we have reported that <strong>DHS</strong> has yet <strong>to</strong>comprehensively satisfy its key cybersecurity responsibilities. Thesereports included about 30 recommendations that we summarizedin<strong>to</strong> the following key areas that are essential for <strong>DHS</strong> <strong>to</strong> address inorder <strong>to</strong> fully implement its cybersecurity responsibilities.Table 1: Key Cybersecurity Areas Reviewed by <strong>GAO</strong>1. Bolstering cyber analysis and warning capabilities.2. Reducing organizational inefficiencies.3. Completing actions identified during cyber exercises.4. Developing sec<strong>to</strong>r-specific plans that fully address all of the cyber-related criteria.5. Improving cybersecurity of infrastructure control systems.6. Strengthening <strong>DHS</strong>’s ability <strong>to</strong> help recover from Internet disruptions.Source: <strong>GAO</strong>Bolstering Cyber Analysis and Warning CapabilitiesIn July 20<strong>08</strong>, we identified 10 that cyber analysis and warningcapabilities included (1) moni<strong>to</strong>ring network activity <strong>to</strong> detectanomalies, (2) analyzing information and investigating anomalies <strong>to</strong>determine whether they are threats, (3) warning appropriateofficials with timely and actionable threat and mitigationinformation, and (4) responding <strong>to</strong> the threat. These fourcapabilities are comprised of 15 key attributes, which are detailed inappendix II.10<strong>GAO</strong>-<strong>08</strong>-588.Page 6


Reducing Organizational InefficienciesWe concluded that while US-CERT demonstrated aspects of each ofthe key attributes, it did not fully incorporate all of them. Forexample, as part of its moni<strong>to</strong>ring, US-CERT obtained informationfrom numerous external information sources; however, it had notestablished a baseline of our nation’s critical network assets andoperations. In addition, while it investigated if identified anomaliesconstitute actual cyber threats or attacks as part of its analysis, itdid not integrate its work in<strong>to</strong> predictive analyses of broaderimplications or potential future attacks, nor does it have theanalytical or technical resources <strong>to</strong> analyze multiple, simultaneouscyber incidents. The organization also provided warnings bydeveloping and distributing a wide array of attack and othernotifications; however, these notifications were not consistentlyactionable or timely—providing the right information <strong>to</strong> the rightpersons or groups as early as possible <strong>to</strong> give them time <strong>to</strong> takeappropriate action. Further, while it responded <strong>to</strong> a limited numberof affected entities in their efforts <strong>to</strong> contain and mitigate an attack,recover from damages, and remediate vulnerabilities, theorganization did not possess the resources <strong>to</strong> handle multiple eventsacross the nation.We also concluded that without the key attributes, US-CERT did nothave the full complement of cyber analysis and warning capabilitiesessential <strong>to</strong> effectively perform its national mission. As a result, wemade 10 recommendations <strong>to</strong> the department <strong>to</strong> address shortfallsassociated with the 15 attributes in order <strong>to</strong> fully establish a nationalcyber analysis and warning capability. <strong>DHS</strong> concurred with 9 of our10 recommendations.In June 20<strong>08</strong>, we reported 11 on the status of <strong>DHS</strong>’s efforts <strong>to</strong>establish an integrated operations center that it agreed <strong>to</strong> adopt perrecommendations from a <strong>DHS</strong>-commissioned expert task force. Thetwo operations centers that were <strong>to</strong> be integrated were within the11<strong>GAO</strong>, <strong>Critical</strong> <strong>Infrastructure</strong> <strong>Protection</strong>: Further Efforts Needed <strong>to</strong> Integrate Planningfor and Response <strong>to</strong> Disruption on Converged Voice and Data Networks, <strong>GAO</strong>-<strong>08</strong>-607(Washing<strong>to</strong>n, D.C.: June 26, 20<strong>08</strong>).Page 7


department’s National Communication System and National CyberSecurity Division. We determined that <strong>DHS</strong> had taken the first ofthree steps <strong>to</strong>wards integrating the operations centers—called theNational Coordination Center Watch and US-CERT—it uses <strong>to</strong> planfor and moni<strong>to</strong>r voice and data network disruptions. While <strong>DHS</strong>completed the first integration step by locating the two centers inadjacent space, it had yet <strong>to</strong> implement the remaining two steps.Specifically, although called for in the task force’srecommendations, the department had not organizationally mergedthe two centers or involved key private sec<strong>to</strong>r critical infrastructureofficials in the planning, moni<strong>to</strong>ring, and other activities of theproposed joint operations center. In addition, the department lackeda strategic plan and related guidance that provides overall directionin this area and has not developed specific tasks and miles<strong>to</strong>nes forachieving the two remaining integration steps.We concluded that until the two centers were fully integrated, <strong>DHS</strong>was at risk of being unable <strong>to</strong> efficiently plan for and respond <strong>to</strong>disruptions <strong>to</strong> communications infrastructure and the data andapplications that travel on this infrastructure, increasing theprobability that communications will be unavailable or limited intimes of need. As a result, we recommended that the departmentcomplete its strategic plan and define tasks and miles<strong>to</strong>nes forcompleting remaining integration steps so that we are betterprepared <strong>to</strong> provide an integrated response <strong>to</strong> disruptions <strong>to</strong> thecommunications infrastructure. <strong>DHS</strong> concurred with our firstrecommendation and stated that it would address the secondrecommendation as part of finalizing its strategic plan.<strong>DHS</strong> has recently made organizational changes <strong>to</strong> bolster itscybersecurity focus. For example, in response <strong>to</strong> the President’sJanuary 20<strong>08</strong> Cyber Initiative, the department established a NationalCybersecurity Center <strong>to</strong> ensure coordination among cyber-relatedefforts across the federal government. <strong>DHS</strong> placed the center at ahigher organizational level than the Assistant Secretary of CyberSecurity and Communications. As we previously reported, 12 this12<strong>GAO</strong>-<strong>08</strong>-588.Page 8


placement raises questions about, and may in fact, diminish theAssistant Secretary’s authority as the focal point for the federalgovernment’s cyber CIP efforts. It also raises similar questions aboutNCSD’s role as the primary federal cyber analysis and warningorganization.Completing Corrective Actions Identified During A Cyber ExerciseIn September 20<strong>08</strong>, we reported 13 on a 2006 major <strong>DHS</strong>-coordinatedcyber attack exercise, called Cyber S<strong>to</strong>rm, that included large scalesimulations of multiple concurrent attacks involving the federalgovernment, states, foreign governments, and private industry. Wedetermined that <strong>DHS</strong> had identified eight lessons learned from thisexercise, such as the need <strong>to</strong> improve interagency coordinationgroups and the exercise program. We also concluded that while <strong>DHS</strong>had demonstrated progress in addressing the lessons learned, moreneeded <strong>to</strong> be done. Specifically, while the department completed 42of the 66 activities identified <strong>to</strong> address the lessons learned, itidentified 16 activities as ongoing and 7 as planned for the future. 14In addition, <strong>DHS</strong> provided no timetable for the completion dates ofthe ongoing activities. We noted that until <strong>DHS</strong> scheduled andcompleted its remaining activities, it was at risk of conductingsubsequent exercises that repeated the lessons learned during thefirst exercise. Consequently, we recommended that <strong>DHS</strong> scheduleand complete the identified corrective activities so that its cyberexercises can help both public and private sec<strong>to</strong>r participantscoordinate their responses <strong>to</strong> significant cyber incidents. <strong>DHS</strong>agreed with the recommendation.13<strong>GAO</strong>-<strong>08</strong>-825.14<strong>DHS</strong> reported that one other activity had been completed, but the department was unable<strong>to</strong> provide evidence demonstrating its completion.Page 9


Developing Sec<strong>to</strong>r-Specific Plans That Fully Address All of the Cyber-Related CriteriaIn 2007, we reported and testified 15 on the cybersecurity aspects ofCIP plans for 17 critical infrastructure sec<strong>to</strong>rs, referred <strong>to</strong> as sec<strong>to</strong>rspecificplans. Specifically, we found that none of the plans fullyaddressed the 30 key cybersecurity-related criteria described in <strong>DHS</strong>guidance. We also determined that while several sec<strong>to</strong>rs’ plans fullyaddressed many of the criteria, others were less comprehensive. Inaddition <strong>to</strong> the variations in the extent <strong>to</strong> which the plans coveredaspects of cybersecurity, there was also variance among the plans inthe extent <strong>to</strong> which certain criteria were addressed. For example,fewer than half of the plans fully addressed describing (1) a process<strong>to</strong> identify potential consequences of cyber attack or (2) anyincentives used <strong>to</strong> encourage voluntary performance of riskassessments. We noted that without complete and comprehensiveplans, stakeholders within the infrastructure sec<strong>to</strong>rs may notadequately identify, prioritize, and protect their critical assets.Consequently, we recommended 16 that <strong>DHS</strong> request that the leadfederal agencies, referred <strong>to</strong> as sec<strong>to</strong>r-specific agencies, that areresponsible for the development of CIP plans for their sec<strong>to</strong>rs fullyaddress all cyber-related criteria by September 20<strong>08</strong> so thatstakeholders within the infrastructure sec<strong>to</strong>rs will effectivelyidentify, prioritize, and protect the cyber aspects of their CIP efforts.The updated plans are due this month.Improving Cybersecurity of <strong>Infrastructure</strong> Control SystemsIn a September 2007 report and Oc<strong>to</strong>ber 2007 testimony, 17 weidentified that federal agencies had initiated efforts <strong>to</strong> improve thesecurity of critical infrastructure control systems—computer-basedsystems that moni<strong>to</strong>r and control sensitive processes and physicalfunctions. For example, <strong>DHS</strong> was sponsoring multiple control15<strong>GAO</strong>, <strong>Critical</strong> <strong>Infrastructure</strong> <strong>Protection</strong>: Sec<strong>to</strong>r-Specific Plans’ Coverage of Key CyberSecurity Elements Varies, <strong>GAO</strong>-<strong>08</strong>-64T (Washing<strong>to</strong>n D.C.; Oc<strong>to</strong>ber 31, 2007); and <strong>Critical</strong><strong>Infrastructure</strong> <strong>Protection</strong>: Sec<strong>to</strong>r-Specific Plans’ Coverage of Key Cyber SecurityElements Varies, <strong>GAO</strong>-<strong>08</strong>-113 (Washing<strong>to</strong>n D.C.; Oct. 31, 2007).16<strong>GAO</strong>-<strong>08</strong>-113.17<strong>GAO</strong>-07-1036 and <strong>GAO</strong>-<strong>08</strong>-119T.Page 10


systems security initiatives, including efforts <strong>to</strong> (1) improve controlsystems cybersecurity using vulnerability evaluation and response<strong>to</strong>ols and (2) build relationships with control systems vendors andinfrastructure asset owners. However, the department had notestablished a strategy <strong>to</strong> coordinate the various control systemsactivities across federal agencies and the private sec<strong>to</strong>r. Further, itlacked processes needed <strong>to</strong> address specific weaknesses in sharinginformation on control system vulnerabilities. We concluded thatuntil public and private sec<strong>to</strong>r security efforts are coordinated by anoverarching strategy and specific information sharing shortfalls areaddressed, there was an increased risk that multiple organizationswould conduct duplicative work and miss opportunities <strong>to</strong> fulfilltheir critical missions.Consequently, we recommended 18 that <strong>DHS</strong> develop a strategy <strong>to</strong>guide efforts for securing control systems and establish a rapid andsecure process for sharing sensitive control system vulnerabilityinformation <strong>to</strong> improve federal government efforts <strong>to</strong> secure controlsystems governing critical infrastructure. In response, <strong>DHS</strong> officials<strong>to</strong>ok our recommendations under advisement and more recentlyhave begun developing a Federal Coordinating Strategy <strong>to</strong> SecureControl Systems, which is still a work in process. In addition, while<strong>DHS</strong> began developing a process <strong>to</strong> share sensitive information; ithas not provided any evidence that the process has beenimplemented or that it is an effective information sharingmechanism.Strengthening <strong>DHS</strong>’s Ability <strong>to</strong> Help Recovery from Internet DisruptionsWe reported and later testified 19 in 2006 that the department hadbegun a variety of initiatives <strong>to</strong> fulfill its responsibility fordeveloping an integrated public/private plan for Internet recovery.However, we determined that these efforts were not comprehensive18<strong>GAO</strong>-07-1036.19<strong>GAO</strong>, Internet <strong>Infrastructure</strong>: Challenges in Developing a Public/Private Recovery Plan,<strong>GAO</strong>-06-863T (Washing<strong>to</strong>n, D.C.: July 28, 2006); and Internet <strong>Infrastructure</strong>: <strong>DHS</strong> FacesChallenges in Developing a Joint Public/Private Recovery Plan, <strong>GAO</strong>-06-672 (Washing<strong>to</strong>n,D.C.: June 16, 2006).Page 11


or complete. As such, we recommended that <strong>DHS</strong> implement nineactions <strong>to</strong> improve the department’s ability <strong>to</strong> facilitatepublic/private efforts <strong>to</strong> recover the Internet in case of a majordisruption.In Oc<strong>to</strong>ber 2007, we testified 20 that the department had madeprogress in implementing our recommendations; however, seven ofthe nine have not been completed. For example, it revised key plansin coordination with private industry infrastructure stakeholders,coordinated various Internet recovery-related activities, andaddressed key challenges <strong>to</strong> Internet recovery planning. However, ithad not, among other things, finalized recovery plans and definedthe interdependencies among <strong>DHS</strong>’s various working groups andinitiatives. In other words, it has not completed an integratedprivate/public plan for Internet recovery. As a result, we concludedthat the nation lacked direction from the department on how <strong>to</strong>respond in such a contingency. We also noted that these incompleteefforts indicated <strong>DHS</strong> and the nation were not fully prepared <strong>to</strong>respond <strong>to</strong> a major Internet disruption.- - - -In summary, <strong>DHS</strong> has developed and implemented capabilities <strong>to</strong>satisfy aspects of key cybersecurity responsibilities. However, it stillneeds <strong>to</strong> take further action <strong>to</strong> fulfill all of these responsibilities. Inparticular, it needs <strong>to</strong> fully address the key areas identified in ourrecent reports. Specifically, it will have <strong>to</strong> bolster cyber analysis andwarning capabilities, address organizational inefficiencies byintegrating voice and data operations centers, enhance cyberexercises by completing the identified activities associated with thelessons learned, ensure that cyber-related sec<strong>to</strong>r-specific criticalinfrastructure plans are completed, improve efforts <strong>to</strong> address thecybersecurity of infrastructure control systems by completing acomprehensive strategy and ensuring adequate mechanisms forsharing sensitive information, and strengthen its ability <strong>to</strong> helprecover from Internet disruptions by finalizing recovery plans and20<strong>GAO</strong>, Internet <strong>Infrastructure</strong>: Challenges in Developing a Public/Private Recovery Plan,<strong>GAO</strong>-<strong>08</strong>-212T (Washing<strong>to</strong>n, D.C.: Oct. 23, 2007).Page 12


defining interdependencies. Until these steps are taken, our nation’scomputer-reliant critical infrastructure remains at unnecessary riskof significant cyber incidents.Mr. Chairman, this concludes my statement. I would be happy <strong>to</strong>answer any questions that you or members of the subcommitteemay have at this time.If you have any questions on matters discussed in this testimony,please contact me at (202) 512-9286, or by e-mail atpownerd@gao.gov. Other key contribu<strong>to</strong>rs <strong>to</strong> this testimony includeCamille Chaires, Michael Gilmore, Rebecca LaPaze, Kush Malhotra,and Gary Mountjoy.Page 13


Appendix I: <strong>DHS</strong>’s Key Cybersecurity ResponsibilitiesResponsibilitiesDevelop a national plan for CIP thatincludes cybersecurityDevelop partnerships and coordinate withother federal agencies, state and localgovernments, and the private sec<strong>to</strong>rImprove and enhance public/privateinformation sharing involving cyberattacks, threats, and vulnerabilitiesDevelop and enhance national cyberanalysis and warning capabilitiesProvide and coordinate incident responseand recovery planning effortsIdentify and assess cyber threats andvulnerabilitiesSupport efforts <strong>to</strong> reduce cyber threatsand vulnerabilitiesPromote and support research anddevelopment efforts <strong>to</strong> strengthencyberspace securityPromote awareness and outreachFoster training and certificationEnhance federal, state, and localgovernment cybersecurityStrengthen international cyberspacesecurityIntegrate cybersecurity with nationalsecurityDescription of responsibilitiesDeveloping a comprehensive national plan for securing the key resources and criticalinfrastructure of the United States, including information technology andtelecommunications systems (including satellites) and the physical and technologicalassets that support such systems. This plan is <strong>to</strong> outline national strategies, activities, andmiles<strong>to</strong>nes for protecting critical infrastructures.Fostering and developing public/private partnerships with and among other federalagencies, state and local governments, the private sec<strong>to</strong>r, and others. <strong>DHS</strong> is <strong>to</strong> serve asthe “focal point for the security of cyberspace.”Improving and enhancing information sharing with and among other federal agencies, stateand local governments, the private sec<strong>to</strong>r, and others through improved partnerships andcollaboration, including encouraging information sharing and analysis mechanisms. <strong>DHS</strong> is<strong>to</strong> improve sharing of information on cyber attacks, threats, and vulnerabilities.Providing cyber analysis and warnings, enhancing analytical capabilities, and developing anational indications and warnings architecture <strong>to</strong> identify precursors <strong>to</strong> attacks.Providing crisis management in response <strong>to</strong> threats <strong>to</strong> or attacks on critical informationsystems. This entails coordinating efforts for incident response, recovery planning,exercising cybersecurity continuity plans for federal systems, planning for recovery ofInternet functions, and assisting infrastructure stakeholders with cyber-related emergencyrecovery plans.Leading efforts by the public and private sec<strong>to</strong>r <strong>to</strong> conduct a national cyber threatassessment, <strong>to</strong> conduct or facilitate vulnerability assessments of sec<strong>to</strong>rs, and <strong>to</strong> identifycross-sec<strong>to</strong>r interdependencies.Leading and supporting efforts by the public and private sec<strong>to</strong>r <strong>to</strong> reduce threats andvulnerabilities. Threat reduction involves working with the law enforcement community <strong>to</strong>investigate and prosecute cyberspace threats. Vulnerability reduction involves identifyingand remediating vulnerabilities in existing software and systems.Collaborating and coordinating with members of academia, industry, and government <strong>to</strong>optimize cybersecurity-related research and development efforts <strong>to</strong> reduce vulnerabilitiesthrough the adoption of more secure technologies.Establishing a comprehensive national awareness program <strong>to</strong> promote efforts <strong>to</strong>strengthen cybersecurity throughout government and the private sec<strong>to</strong>r, including the homeuser.Improving cybersecurity-related education, training, and certification opportunities.Partnering with federal, state, and local governments in efforts <strong>to</strong> strengthen thecybersecurity of the nation’s critical information infrastructure <strong>to</strong> assist in the deterrence,prevention, preemption of, and response <strong>to</strong> terrorist attacks against the United States.Working in conjunction with other federal agencies, international organizations, andindustry in efforts <strong>to</strong> promote strengthened cybersecurity on a global basis.Coordinating and integrating applicable national preparedness goals with its National<strong>Infrastructure</strong> <strong>Protection</strong> Plan.Source: <strong>GAO</strong> analysis of the Homeland Security Act of 2002, the Homeland Security Presidential Directive-7, and the National Strategy <strong>to</strong> Secure Cyberspace.Page 14


Appendix II: Key Attributes of Cyber Analysis and WarningCapabilitiesCapabilityAttributeMoni<strong>to</strong>ring • Establish a baseline understanding of network assets and normal network traffic volume and flow• Assess risks <strong>to</strong> network assets• Obtain internal information on network operations via technical <strong>to</strong>ols and user reports• Obtain external information on threats, vulnerabilities, and incidents through various relationships,alerts, and other sources• Detect anomalous activitiesAnalysis • Verify that an anomaly is an incident (threat of attack or actual attack)• Investigate the incident <strong>to</strong> identify the type of cyber attack, estimate impact, and collect evidence• Identify possible actions <strong>to</strong> mitigate the impact of the incident• Integrate results in<strong>to</strong> predictive analysis of broader implications or potential future attackWarning • Develop attack and other notifications that are targeted and actionable• Provide notifications in a timely manner• Distribute notifications using appropriate communications methodsResponse • Contain and mitigate the incident• Recover from damages and remediate vulnerabilities• Evaluate actions and incorporate lessons learnedSource: <strong>GAO</strong> analysis.31<strong>08</strong>86Page 15


This is a work of the U.S. government and is not subject <strong>to</strong> copyright protection in theUnited States. The published product may be reproduced and distributed in its entiretywithout further permission from <strong>GAO</strong>. However, because this work may containcopyrighted images or other material, permission from the copyright holder may benecessary if you wish <strong>to</strong> reproduce this material separately.


<strong>GAO</strong>’s MissionObtaining Copies of<strong>GAO</strong> Reports andTestimonyOrder by Mail or PhoneTo Report Fraud,Waste, and Abuse inFederal ProgramsCongressionalRelationsPublic AffairsThe Government Accountability Office, the audit, evaluation, andinvestigative arm of Congress, exists <strong>to</strong> support Congress in meeting itsconstitutional responsibilities and <strong>to</strong> help improve the performance andaccountability of the federal government for the American people. <strong>GAO</strong>examines the use of public funds; evaluates federal programs and policies;and provides analyses, recommendations, and other assistance <strong>to</strong> helpCongress make informed oversight, policy, and funding decisions. <strong>GAO</strong>’scommitment <strong>to</strong> good government is reflected in its core values ofaccountability, integrity, and reliability.The fastest and easiest way <strong>to</strong> obtain copies of <strong>GAO</strong> documents at no costis through <strong>GAO</strong>’s Web site (www.gao.gov). Each weekday, <strong>GAO</strong> postsnewly released reports, testimony, and correspondence on its Web site. Tohave <strong>GAO</strong> e-mail you a list of newly posted products every afternoon, go<strong>to</strong> www.gao.gov and select “E-mail Updates.”The first copy of each printed report is free. Additional copies are $2 each.A check or money order should be made out <strong>to</strong> the Superintendent ofDocuments. <strong>GAO</strong> also accepts VISA and Mastercard. Orders for 100 ormore copies mailed <strong>to</strong> a single address are discounted 25 percent. Ordersshould be sent <strong>to</strong>:U.S. Government Accountability Office441 G Street NW, Room LMWashing<strong>to</strong>n, DC 20548To order by Phone: Voice: (202) 512-6000TDD: (202) 512-2537Fax: (202) 512-6061Contact:Web site: www.gao.gov/fraudnet/fraudnet.htmE-mail: fraudnet@gao.govAu<strong>to</strong>mated answering system: (800) 424-5454 or (202) 512-7470Ralph Dawn, Managing Direc<strong>to</strong>r, dawnr@gao.gov, (202) 512-4400U.S. Government Accountability Office, 441 G Street NW, Room 7125Washing<strong>to</strong>n, DC 20548Chuck Young, Managing Direc<strong>to</strong>r, youngc1@gao.gov, (202) 512-4800U.S. Government Accountability Office, 441 G Street NW, Room 7149Washing<strong>to</strong>n, DC 20548PRINTED ONRECYCLED PAPER

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!