Book a Demo!
CoCalc Logo Icon
StoreFeaturesDocsShareSupportNewsAboutPoliciesSign UpSign In
Download
29547 views
1
2
3
4
5
United States General Accounting Office
6
Report to Senator Robert F. Bennett,
7
8
9
10
Ranking Minority Member, Joint Economic
11
Committee, Congress of the United States
12
13
October 2001
14
INFORMATION SHARING
15
16
17
18
Practices That Can Benefit Critical Infrastructure
19
Protection
20
a
21
22
23
GAO-02-24
24
25
Contents
26
27
Figures
28
Contents
29
30
Abbreviations
31
CDC Centers for Disease Control and Prevention CERT/CC CERT®
32
Coordination Center
33
34
A
35
United States General Accounting Office Washington, D.C.
36
20548
37
October 15, 2001
38
The Honorable Robert F. Bennett Ranking Minority Member Joint
39
Economic Committee Congress of the United States
40
Dear Senator Bennett:
41
This report responds to your May 2001 request that we study the
42
practices of organizations that successfully share sensitive or
43
time-critical information. Information sharing and coordination are
44
key elements in developing comprehensive and practical approaches
45
to defending against computer-based, or cyber, attacks, which could
46
threaten the national welfare. Such attacks could severely disrupt
47
computer-supported operations, compromise the confidentiality of
48
sensitive information, and diminish the integrity of critical data.
49
Computer-based incidents, such as the ILOVEYOU virus in May 2000
50
and the recent Code Red, SirCam, and Nimda attacks, have caused
51
significant disruptions and damage.1 In addition, the terrorist
52
attacks of September 11 illustrate the importance of having timely
53
information from others on threats and possible precursors to an
54
attack.
55
The importance of sharing information and coordinating the
56
response to cyber threats among various stakeholders has increased
57
as our government and our nation have become ever more reliant on
58
interconnected computer systems to support critical operations and
59
infrastructures, such as telecommunications, power distribution,
60
financial services, national defense, and critical government
61
operations. Information on threats and incidents experienced by
62
others can help stakeholders identify trends, better understand the
63
risks they face, and determine what preventative measures should be
64
implemented. Accordingly, the federal government's strategy for
65
protecting the nation's critical computer-dependent infrastructure
66
sectors includes efforts to establish information sharing and
67
analysis centers (ISACs) within both the federal government and
68
individual industry sectors. Such analysis centers can use
69
comprehensive, timely information on incidents to determine the
70
nature of an attack, provide warnings, and advise on how to
71
mitigate an imminent attack.
72
1Information Security: Code Red, Code Red II, and SirCam Attacks
73
Highlight Need for Proactive Measures
74
(GAO-01-1073T,August 29, 2001).
75
76
77
78
To identify practices that could be adopted by federal agencies
79
and others to (1) promote successful sharing of information on
80
computer-based vulnerabilities and incidents and (2) overcome
81
related challenges, we studied 11 organizations experienced in
82
developing pertinent informationsharing relationships and
83
procedures. Appendix I contains a description of our objectives,
84
the scope of our study, and the methodology we used. Appendix II
85
describes each organization covered by our review.
86
The organizations identified a number of
87
factors that they deemed critical
88
89
90
91
Results in Brief
92
to their success in building successful information-sharing
93
relationships with and among their members. All of the
94
organizations identified trust as the essential underlying element
95
to successful relationships and said that trust could be built only
96
over time and, primarily, through personal relationships. Other
97
critical success factors identified included
98
99
100
101
(1)
102
establishing effective and appropriately secure
103
communication mechanisms, such as regular meetings and secure Web
104
sites, (2) obtaining the support of senior managers at member
105
organizations regarding the sharing of potentially sensitive member
106
information and the commitment of resources, and (3) ensuring
107
organization leadership continuity. In addition, to be successful,
108
information-sharing organizations provided identifiable membership
109
benefits, such as current information about threats,
110
vulnerabilities, and incidents; information on lessons learned; and
111
free member advice. Without such benefits, according to the
112
representatives we met with, members would not continue
113
participating.
114
115
Among the challenges identified, one of the most difficult was
116
overcoming new members' initial reluctance to share information.
117
Other challenges included (1) developing agreements on the use and
118
protection of shared information, (2) obtaining adequate funding to
119
cover the cost of items such as Web sites and meetings while
120
avoiding seeking contributions intended primarily to promote the
121
interests of an individual organization,
122
123
124
(3)
125
maintaining a focus on emerging issues of interest to
126
members, and
127
128
129
(4)
130
maintaining professional and administrative staff with
131
appropriate skills.
132
133
134
The critical success factors and challenges described by the
135
organizations provide useful insights for other entities that are
136
developing informationsharing relationships to assist in critical
137
infrastructure protection. In addition, as it did regarding the
138
Year 2000 computing challenge, the Congress can play a key role by
139
actively monitoring progress in meeting critical infrastructure
140
protection goals, including improved information sharing, and by
141
assisting in clarifying the way federal agencies may use sensitive
142
information provided for critical infrastructure protection
143
purposes. In 1998, Congress passed legislation intended to address
144
concerns from private-sector entities about exposure to legal
145
liability and antitrust law violations that might arise due to
146
sharing information on Year 2000 readiness. The Congress is
147
currently considering measures intended to address several of the
148
practices and challenges we identified pertaining to critical
149
infrastructure protection.
150
In commenting on a draft of this report, the participants of our
151
study agreed with the critical success factors and challenges that
152
we identified. Several provided additional supporting points and
153
examples, which we have included in the report as appropriate.
154
Over the last decade, our government and
155
our nation have become
156
157
158
Background
159
increasingly reliant on computer systems to support critical
160
operations and infrastructures, such as telecommunications, power
161
distribution, financial services, emergency services, national
162
defense, and critical government operations. Over the same period,
163
computer interconnectivity experienced an unprecedented growth,
164
most notably in the use of the Internet, that has revolutionized
165
the way our government, our nation, and much of the world
166
communicate and conduct business. The benefits have been enormous
167
in terms of facilitating communications, business processes, and
168
access to information. However, without proper safeguards, this
169
widespread interconnectivity poses enormous risks to our computer
170
systems and, more importantly, to the critical operations and
171
infrastructures they support.
172
Attacks could severely disrupt computer-supported operations,
173
compromise the confidentiality of sensitive information, and
174
diminish the integrity of critical data. A significant concern is
175
that terrorists or hostile foreign states could severely damage or
176
disrupt critical operations, resulting in harm to the public
177
welfare. Threats are increasing, in part, because the number of
178
individuals with computer skills is increasing and because
179
intrusion, or "hacking," techniques have become readily accessible
180
through magazines, computer bulletin boards, and Internet Web
181
sites. However, the sources of and motives behind cyber attacks
182
often cannot be readily determined. This is because groups or
183
individuals can attack remotely from anywhere in the world, over
184
the Internet, other networks, or dial-up lines, and they can
185
disguise their identity, location, and intent by launching attacks
186
across a span of communications systems and computers. Figure 1
187
provides an overview of the various types of risks to
188
computer-based operations.
189
190
The federal government has recognized that mitigating risks to
191
our nation's critical computer-dependent infrastructures, many of
192
which are privately owned, is a serious challenge requiring
193
coordination and cooperation among federal agencies, public and
194
private-sector entities, and other nations. In 1991, the National
195
Research Council studied the issue and reported that "as computer
196
systems become more prevalent, sophisticated, embedded in physical
197
processes, and interconnected, society becomes more vulnerable to
198
poor system design, accidents that disable systems, and attacks on
199
computer systems."2 In July 1996, the President's Commission on
200
Critical Infrastructure Protection was established to investigate
201
the nation's vulnerability to both cyber and physical threats. The
202
commission's October 1997 report, Critical Foundations: Protecting
203
America's Infrastructures, described the potentially devastating
204
implications of poor information security from a national
205
perspective.
206
In May 1998, in response to the commission's 1997 report, the
207
President issued Presidential Decision Directive (PDD) 63, which
208
outlined a strategy for combating the threat of cyber attacks by
209
terrorists, nation states, criminals, or others. The directive
210
tasked federal agencies with developing critical infrastructure
211
protection plans.
212
In addition, PDD 63 recognized the importance of establishing
213
mechanisms for sharing information on system vulnerabilities,
214
threats, intrusions, and anomalies so that both government and
215
industry could better prepare to warn and defend against
216
computer-based attacks. Specifically, it designated "lead agencies"
217
within the federal government to work with private-sector and
218
government entities in each of eight infrastructure sectors and
219
five special function areas. The eight infrastructures identified
220
were (1) information and communications; (2) banking and finance;
221
(3) water supply; (4) aviation, highway, mass transit, pipelines,
222
rail, and waterborne commerce; (5) emergency law enforcement; (6)
223
emergency fire services and continuity of government; (7) electric
224
power and oil and gas production and storage; and (8) public health
225
services. The five special function areas were (1) law enforcement
226
and internal security, (2) intelligence, (3) foreign affairs, (4)
227
national defense, and (5) research and development. The directive
228
also encouraged the creation of ISACs that could serve as
229
mechanisms for gathering, analyzing, appropriately sanitizing, and
230
disseminating information to and from infrastructure
231
2Computers at Risk: Safe Computing in the Information Age, the
232
National Research Council, 1991.
233
Page 5 GAO-02-24 Information Sharing Practices
234
sectors and the government. Further, it recognized the Federal
235
Bureau of Investigation's National Infrastructure Protection Center
236
as a national threat assessment, warning, vulnerability, and law
237
enforcement investigation and response center.
238
Information sharing and coordination among organizations are
239
central to producing comprehensive and practical approaches and
240
solutions to combating computer-based threats. Having information
241
on threats and on actual incidents experienced by others can help
242
an organization identify trends, better understand the risks it
243
faces, and determine what preventative measures should be
244
implemented. In addition, comprehensive, timely information on
245
incidents can help federal and nonfederal analysis centers
246
determine the nature of an attack, provide warnings, and advise on
247
how to mitigate an imminent attack.
248
However, we previously reported that progress in implementing
249
PDD 63, including the establishment of information-sharing
250
relationships, has been slow. Although six ISACs in five industry
251
sectors had been established as of March 2001, three had been in
252
existence only since December 2000.3 Further, as we reported in
253
April 2001, the National Infrastructure Protection Center had mixed
254
success in establishing information-sharing relationships with
255
other government entities and private industry.4
256
Despite this limited progress, a number of government and
257
private organizations have gained experience in establishing
258
information-sharing relationships. These organizations range from
259
groups that disseminate information on immediate threats and
260
vulnerabilities, to those that seek to facilitate information
261
sharing between public and private entities on industry-specific
262
threats, to those that promote coordination across infrastructure
263
sectors and on an international scale. However, developing the
264
information-sharing and coordination capabilities that could assist
265
in effectively addressing computer-based threats and actual
266
incidents has proven to be challenging as organizations grapple
267
with ways to ensure that useful and complete data are collected;
268
appropriately analyzed; protected from inappropriate disclosure;
269
and efficiently and effectively disseminated, often in the form of
270
warnings.
271
3Combating Terrorism: Selected Challenges and Related
272
Recommendations
273
(GAO-01-822,September 20, 2001).
274
4Critical Infrastructure Protection: Significant Challenges in
275
Developing National Capabilities
276
(GAO-01-323, April 25, 2001).
277
Page 6 GAO-02-24 Information Sharing Practices
278
279
280
Factors Critical to Successful Information
281
Sharing
282
The organizations identified several critical success factors
283
that they viewed as essential to establishing, developing, and
284
maintaining effective information-sharing relationships, which
285
could benefit critical infrastructure protection efforts. These
286
factors included (1) fostering trust and respect; (2) establishing
287
effective, timely, and appropriately secure communication; (3)
288
obtaining top management support; (4) ensuring organization
289
leadership continuity; and (5) generating clearly identifiable
290
membership benefits.
291
Foster Trust and Respect An underlying
292
element to the success of information-sharing organizations was
293
developing trusted relationships among the members and the
294
organizations' staffs. Several of the organizations had
295
professional and administrative staffs that provided analytical
296
capabilities and facilitated their members' participation in the
297
organization's activities. Others were less formally structured
298
organizations that relied primarily on members for such support.
299
Trust was critical to overcome members' reluctance to disclose
300
their weaknesses, vulnerabilities, and other confidential or
301
proprietary business information to other members-some of whom were
302
business competitors. In general, members were reluctant to share
303
information due to concerns that an inadvertent release of this
304
type of information could damage reputations; lower customer
305
confidence; provide an advantage to competitors; and possibly
306
negatively affect members' businesses and lead to punitive measures
307
against an individual member or a member organization.
308
All of the organizations agreed that trust had to be built over
309
time and through personal relationships, and they had taken various
310
steps to facilitate the process, such as the following:
311
312
313
314
Most held regular-bimonthly, quarterly, or
315
annual-meetings or forums to discuss issues and establish
316
face-to-face contact. Beyond the time used to discuss technical
317
issues, these meetings included time for members to build personal
318
relationships and contacts. Many of the organizations and the
319
members stated that the personal relationships and contacts
320
developed through participating in information-sharing
321
organizations was as important, if not more important, in
322
developing trust than the information received by attending an
323
organization's function.
324
325
326
327
Many organizations encouraged consistent member
328
participation, noting that trust was built most effectively when
329
members consistently attended and participated in the
330
organizations' activities. Also important was for members to
331
consistently send the same representatives and not rotate different
332
people as representatives to the organizations' functions. To
333
maintain consistency, some organizations did not allow alternate
334
attendees when designated representatives could not
335
attend.
336
337
338
339
Most followed established procedures or performed
340
background checks to evaluate prospective members before allowing
341
their participation. For example, some organizations allowed
342
nonmembers to participate only if the organization invited them or
343
an existing member invited and escorted them. Another organization
344
had an official board that reviewed membership applications to
345
determine whether the applicant and the applicant's organization
346
met established membership criteria. Also, groups that served
347
specific audiences had established lists of pertinent organizations
348
that were allowed to participate as members and receive information
349
of specific interest to that group.
350
351
352
353
Many attempted to establish an atmosphere of mutual
354
respect among the members so that each member's issues and
355
expertise merited consideration regardless of the company they
356
represented or the individual representative's position in that
357
company. Often, each member was required to share information or,
358
in some cases, time was set aside to give each member an
359
opportunity to raise issues for discussion. In addition, many
360
organizations encouraged members to subordinate individual or
361
individual organizations' interests to the interests of the entire
362
information-sharing group. For example, one organization had simple
363
rules of behavior. Members were to support one another in improving
364
the security posture of each other's organization without regard
365
for their own self-promotion or for the profit or publicity of
366
their individual organization.
367
368
369
370
All had established procedures for handling violations of
371
the rules because any violation of trust undermined the
372
organization's purpose and diminished members' willingness to share
373
in the future. The organizations had both formal and informal means
374
of encouraging compliance and sanctioning violators. In some cases,
375
members were formally asked to terminate their participation, a
376
member's access was terminated, or a member's organization was
377
asked to replace its representative. For example, one organization
378
would restrict access to a secure server, thereby terminating the
379
individual's ability to share or
380
381
382
383
Establish Mechanisms For Effective,
384
Timely, and Appropriately Secure Communication
385
receive information. Informally, other members would no longer
386
include a violator in sensitive conversations. One participant
387
emphasized that once the group lost trust in a member, trust could
388
not be easily restored. Our study participants said that their
389
organizations rarely experienced a violation of trust because
390
members did not want to jeopardize their ability to participate
391
and, thus, lose the benefits of membership.
392
The organizations used a variety of mechanisms to ensure
393
effective and timely communication among members and with the
394
professional and administrative staffs that some of the
395
organizations had established. In addition, the organizations were
396
concerned about appropriately securing the information being shared
397
to maintain member anonymity, when desired, and avoid
398
inappropriately disseminating sensitive or proprietary information
399
to nonmembers.
400
Regularly scheduled meetings were the primary method for sharing
401
information as well as a method for building trust, as previously
402
discussed. These meetings offered a generally secure environment to
403
share information, while also encouraging broader member
404
participation. The organizations also adjusted the meeting times
405
and lengths to accommodate member needs and attempted to enhance
406
the meeting's efficiency and effectiveness by limiting the time for
407
presentations, approving most topics and presentations before the
408
meetings, and adjusting meeting times to maximize face-to-face
409
discussions between members.
410
Typically, the meetings lasted 1/2 day to 2 days for the entire
411
membership, and some meetings included separate sessions for
412
smaller groups to discuss specific technical or member issues. For
413
example, one organization had quarterly 2-day meetings, the first
414
day of which was typically restricted to a small number of members
415
with expertise pertinent to the specific topic under discussion.
416
These closed meetings tended to be more technical than the open
417
meetings and include information and discussions that were more
418
sensitive and detailed. The second day's meeting, which was for all
419
members of the organization, included discussions about the latest
420
software tools and the latest technology and allowed time for any
421
member to openly discuss specific topics. Another organization held
422
more informal quarterly half-day meetings that included
423
presentations about a wide variety of topics and allowed
424
considerable time for members to develop personal contacts and have
425
face-to-face discussions. Beyond the regularly scheduled meetings,
426
three organizations had created committees to perform specific
427
tasks, such as policy setting, that allowed for greater contact
428
between some members and more topic-based information sharing.
429
Various types of information technology provided important
430
communication mechanisms as well. For example, Web sites were used
431
to
432
(1) disseminate all types of information, including alerts,
433
advisories, reports, and other analysis; (2) make databases
434
available to the members; and (3) provide methods for members to
435
ask each other about particular incidents, vulnerabilities, or
436
potential solutions. Many organizations had secure Web sites to
437
share sensitive information; others used open sites to share
438
general information with their members and the public. One
439
organization established a secure telephone line that allowed
440
immediate contact with multiple parties, thereby speeding
441
communication of timecritical information. In addition, some
442
organizations used e-mail to communicate less sensitive information
443
to the entire membership. However, members from one organization
444
did not typically use e-mail because of the lack of security and
445
the inability to control subsequent distribution. This organization
446
relied primarily on regular mail and telephone conversations to
447
disseminate information about most things, including meeting
448
agendas and real-time problem solving.
449
Due to concerns about the inadvertent release of sensitive
450
information, membership lists, and victim identification, some of
451
the organizations had implemented special security procedures. For
452
example, several organizations carefully sanitized victim
453
identifiers from documentation or did not document discussions
454
about specific vulnerabilities and incidents. One organization took
455
special precautions to hide the identity of victims by limiting its
456
staff's access to the information and segregating the information
457
on a special network. Another organization's membership list was
458
maintained by only one person and never generally released to all
459
members.
460
Several representatives stated that an underlying requirement
461
for communications was establishing standard terms and reporting
462
thresholds so that the magnitude of an incident could be easily and
463
consistently understood and members could quickly determine an
464
incident's potential impact on them. According to one official,
465
such standardization helped to ensure that (1) members understood
466
the level of risk imposed by the circumstance, (2) information was
467
appropriately sanitized to protect the victim's identity, and (3)
468
solutions were easily understood. One organization had developed an
469
extensive policy that defined each member's responsibility for
470
reporting information, the terms that would be used for the
471
reporting, and the thresholds that required reporting. Also, two
472
organizations were developing reporting forms to standardize the
473
mechanism and language used to report incidents to the organization
474
for further analysis and dissemination.
475
In addition, organizations sought member input in developing new
476
systems and mechanisms for communicating information, thereby
477
better fulfilling member needs and giving the members a sense of
478
ownership in the system or product. For example, one organization
479
solicited suggestions about how to improve existing databases and
480
what new databases were needed by the members.
481
Members told us that senior management
482
support for their participation in an information-sharing
483
organization was critical to their success in obtaining valuable
484
information and contributing to the success of the entire
485
information-sharing organization. For example, management approval
486
was needed before individuals could share information about
487
potentially sensitive incidents and vulnerabilities. Without such
488
support, members could not fully participate in the
489
information-sharing process. Top management support was also needed
490
to ensure that a member organization's representative could obtain
491
funding for travel and other resources. For example, two
492
organizations charged membership fees-one of which exceeded $25,000
493
a year-and other organizations requested people to provide support
494
staff and analysts.
495
496
497
Obtain Top Management Support
498
Ensure Leadership Continuity
499
Several organizations were led by individuals who had spent
500
years building personal relationships with members and working to
501
champion the purpose and mission of their organizations. In our
502
discussions with members, these leaders were given considerable
503
credit for the quality and value of the information that the
504
members received and the success of the information-sharing
505
organizations. These long-term leaders told us that, to help ensure
506
continuity and diminish reliance on a single individual, they
507
attempted to institutionalize their roles by bringing in additional
508
people to assist in leading their organizations and performing such
509
duties as enforcing membership rules and keeping current on issues
510
and topics affecting their organization's members.
511
Generate Clearly Organization
512
representatives said that generating clearly identifiable benefits
513
was essential for maintaining active member participation and
514
515
516
Identifiable Membership
517
Benefits support in their organizations. Many representatives
518
told us that due to members' own resource and time constraints,
519
members would not participate in information-sharing organizations
520
unless they received benefits. Benefits the representatives cited
521
included the following:
522
523
524
525
Members were provided access to current information about
526
incidents, threats, and vulnerabilities that had been analyzed by
527
trusted experts. Some of the organizations performed expert
528
analysis on incidents reported to them by members or the public and
529
provided analyses and alerts to the members that included
530
information on the incident's level of threat and any possible
531
mitigation techniques. Another organization provided its members
532
with a method for soliciting advice from the entire membership. In
533
this case, a member would send a query to the organization's
534
experts, who would review the request, clarify any questions with
535
the member, and then send the request to the rest of the
536
membership. While the rest of the membership reviewed and commented
537
on the query, the organization's experts continued to analyze the
538
problem, eventually providing its final analysis, which could
539
include a threat rating and potential solutions to the entire
540
membership. Some participants stated that the amount of analysis
541
performed before informing the members had to be balanced with the
542
need to quickly warn the members about the potential threat.
543
Several participants stated that sharing information for the sake
544
of sharing was not valuable because information security
545
professionals need analyses that offer solutions.
546
547
548
549
Members were informed about emerging technology so that
550
they could discuss or at least be aware of possible vulnerabilities
551
and the associated risks. These discussions were valuable to
552
members because the information was useful in their employer's
553
planning efforts. For example, several of the organizations had
554
recently discussed, or were planning to discuss, the
555
vulnerabilities surrounding the use of wireless networking
556
technology.
557
558
559
560
Members shared information concerning information
561
security management practices, including corporate governance
562
practices, business risk management processes, computing and
563
network contract provisions, application development and support,
564
disaster recovery planning, and performance measurement regarding
565
control effectiveness.
566
567
568
569
Members shared lessons learned and offered free expert
570
advice on individual projects. The opportunity to draw on a network
571
of experts gave members insight into their own problems and the
572
shortfalls in proposed projects. For example, in many cases, one
573
organization's members were willing to help each other by reviewing
574
the requirement documentation for new systems development projects
575
or system enhancement projects and participate in meetings to
576
expose weaknesses and raise questions about a proposed project.
577
According to one participant, his employer had received hundreds of
578
thousands of dollars worth of free expert advice during a half-day
579
discussion of a proposed information system that his employer was
580
developing. The discussion led to the development of a better, more
581
secure system. The sharing of free advice also occurred more
582
informally.
583
584
585
586
Members received real-time assistance in response to
587
problems. For example, one member's entity experienced a
588
sophisticated network intrusion that was originating from a foreign
589
Internet service provider. Through the contacts made at one of the
590
information-sharing organizations, the system administrator was
591
able to contact the Internet service provider and stop the
592
intrusion. According to an individual involved, this incident was
593
stopped much faster than it otherwise would have been because of
594
the trusted relationships developed through the information-sharing
595
organization that allowed open and candid discussions to
596
occur.
597
598
599
600
Members established more cooperative relationships with
601
law enforcement entities than would have otherwise occurred. Of 11
602
organizations, 2 were sponsored by law enforcement entities and
603
most included members from the law enforcement community. Although
604
law enforcement organizations could not share certain sensitive
605
information, including them in the information-sharing groups led
606
to trusted relationships between law enforcement organizations and
607
the others; shared expertise about computer forensics and evidence
608
gathering related to electronic crimes; and, thus, awareness about
609
these topics, which encouraged organizations to report crimes.
610
Representatives of one group told us that their members' ability to
611
properly gather and protect computer-related evidence had
612
facilitated law enforcement investigations, thus limiting the time
613
and resources that the victim and the law enforcement officers
614
needed to carry out an investigation. In addition, the trusted
615
relationships provided law enforcement with a greater pool of
616
experts to use as expert witnesses or consultants.
617
618
619
620
Members developed valuable professional relationships
621
through participation. Many members that participated in our study
622
stated that their exposure to other experts and cutting-edge
623
technology was a valuable learning experience that increased their
624
own technical expertise. In addition, the large network of
625
colleagues that members developed by participating assisted their
626
employers in identifying potential professionals to fill open
627
positions.
628
629
630
631
Members told us that they believed that the information
632
sharing their organizations engaged in contributed to the overall
633
security of the nation's critical infrastructures-an effort that
634
they viewed as being in their own self-interest, as well as that of
635
others.
636
637
638
In addition to the critical success factors
639
previously discussed, organizations identified a number of related
640
challenges to effective information sharing. These challenges
641
included (1) initially establishing and maintaining trust
642
relationships, (2) developing agreements on the use and protection
643
of shared information, (3) obtaining adequate funding, (4)
644
developing and retaining a membership base, and (5) developing and
645
maintaining an organization staff with appropriate skills.
646
647
648
649
Challenges to Building and Maintaining Effective Information
650
Sharing
651
652
Initially Establishing and Maintaining
653
Trust Relationships
654
All of the participating organizations told us that initially
655
establishing trust among the original members was a challenge. This
656
was because members were reluctant to share their organization's
657
problems and vulnerabilities with outsiders, some of whom were
658
commercial competitors. Members stated that the first meetings
659
discussed broad subjects that individuals were concerned about or
660
equally affected by, such as computer forensics.
661
In some cases, members initially participated because of an
662
existing trust relationship with individual leaders or sponsors,
663
and it was a challenge to keep them returning until they saw value
664
in participating and had built trust with other members. In such
665
situations, the persistence of trusted leaders in encouraging
666
effective member participation was essential.
667
Over time, this challenge diminished as members became familiar
668
with each other, enthusiastic members moved past general topics,
669
and rules of behavior were clarified. In addition, over time,
670
members began to better understand the perspectives of others. For
671
example, discussions among members gradually led those from the
672
private sector to gain an
673
674
675
Developing Agreements on the Use and
676
Protection of Shared Information
677
understanding of the law enforcement community's approach to
678
investigating crime. Further, some members from federal agencies
679
said that it took time for them to determine how they could share
680
sensitive, including classified, information with nonfederal
681
government entities.
682
Another challenge, previously mentioned, was the need to
683
institutionalize trust, rather than depend indefinitely on personal
684
one-on-one relationships. Institutionalizing trust was especially
685
important for large organizations and federal entities that
686
typically experienced a great deal of staff turnover.
687
Information sharing is impeded when there is a lack of clearly
688
understood agreements and expectations on how potentially sensitive
689
information will be used and protected by the recipients. To
690
overcome this obstacle, most of the organizations required members
691
to sign confidentiality or informationsharing agreements. These
692
agreements varied among the organizations: some agreements were
693
general, while others were specific. Though many of the
694
organizations did not consider these agreements to be essential,
695
representatives of one organization considered them important
696
because they clarified and helped to institutionalize agreements,
697
ensured senior management understanding and support, and fostered
698
acceptance of new members. For example, one organization determined
699
that more formal agreements were needed when its membership was
700
significantly expanded. The more formal agreements helped ensure
701
that new members were familiar with the organization's practices,
702
which had previously been informal and undocumented. These new
703
agreements described how the sensitivity of information would be
704
defined, how shared information would be protected from
705
dissemination outside the group, and what information could be
706
shared with nonmembers.
707
Noting that information-sharing agreements cannot cover every
708
situation that may arise, one organization emphasized the
709
importance of promoting an attitude of sensitivity to the concerns
710
of others regarding disclosure of potentially confidential or
711
damaging information. Officials from this organization described a
712
situation in which a company had notified them of a newly
713
identified vulnerability. Before disseminating information on the
714
vulnerability to its constituent members, the information-sharing
715
organization worked with the company to develop a message that
716
would provide the needed vulnerability information but not disclose
717
sensitive details. This collaborative effort helped ensure and
718
maintain trust between the organization and the company.
719
Representatives of a few organizations said that members had
720
raised concerns about their potential liability for any damage that
721
occurred as a result of the information they shared and the advice
722
they gave. Specifically, members were concerned that they might be
723
held liable if other members took their advice and experienced
724
negative results. Officials from one organization were also
725
concerned that they might be held responsible if their advice
726
adversely affected a vendor. To mitigate the risk of any such
727
liability, some organizations addressed this issue specifically in
728
their information-sharing agreements, stating that members who took
729
the advice of others did so at their own risk. In addition, some
730
members of federally sponsored organizations expressed the concern
731
that members' potentially sensitive information voluntarily shared
732
with federal entities could be required to be made publicly
733
available under provisions of the Freedom of Information Act,
734
despite existing exemptions for sensitive or proprietary
735
information.
736
The organizations also faced challenges
737
obtaining adequate funding for various items, including mailings;
738
meeting space; technological enhancements; and other administrative
739
activities and, when applicable, salaries for permanent staff. They
740
noted that the funding must be reliable so that the organization
741
could plan, budget, and remain consistent in its activities. For
742
example, one organization had to stop development of a secure Web
743
site because the sponsor withdrew its support. Representatives from
744
several organizations that relied on voluntary contributions from
745
members emphasized, however, that such funding must be
746
unbiased-that is, used for promoting open and honest information
747
sharing rather than furthering an individual's or organization's
748
stature in the community or for gaining clients.
749
750
751
Obtaining Adequate Funding
752
Developing and Retaining the Membership
753
Base
754
Most of the organizations said that they had to work to overcome
755
the challenge of maintaining their memberships' enthusiasm and
756
participation so that members would use the communication
757
mechanisms, maintain confidentiality, and continue to share
758
relevant information. In addition, organizations had to solicit new
759
members to stay at their chartered number and to keep an influx of
760
new ideas.
761
For the organizations that strictly controlled their membership
762
or the number of members, developing and maintaining their
763
membership base was a formidable challenge. For these
764
organizations, the loss of members (e.g., due to the loss of the
765
members' management support or difficult
766
767
768
Developing and Maintaining Appropriate
769
Analytical and Administrative Skills
770
economic times) threatened their survival. For one organization,
771
this meant that the leaders had to continually establish contacts
772
in their industry and determine which prospective companies would
773
provide the most benefit to the entire group.
774
In addition, the organizations that focused on the information
775
technology area faced the challenge of a very transient membership
776
because information technology professionals often moved from
777
organization to organization. When the individuals moved, the
778
information-sharing organizations had to determine if they would be
779
allowed to continue participating, which was usually based on the
780
contributions and the enthusiasm of the individual. The
781
organizations usually allowed individual members who had changed
782
employers to continue participation. However, two organizations
783
specifically did not allow individuals to continue participating if
784
they changed employers and their new employer was not a member of
785
the organizations because their membership was based on the
786
organizations, not the individuals.
787
Most of the organizations faced the challenge of developing and
788
maintaining an organization with the appropriate operational skills
789
to facilitate the members' participation and oversee administrative
790
activities that ensured continued and effective information
791
sharing. For example, the organizations that had professional and
792
administrative staffs said that it was difficult to find and retain
793
employees with the level of skills and foresight that would
794
contribute to the organization's mission. Staff members were
795
expected to assist members in participating in information sharing
796
by arranging meetings and travel, maintaining the communications
797
mechanisms, and keeping abreast of current and emerging issues.
798
Further, to build trusted relationships and gain the acceptance of
799
member organizations, staff needed to have pertinent skills and
800
knowledge.
801
Because the job market was so competitive, one of the sponsoring
802
organizations established flexible working arrangements for and
803
gave competitive pay to their professional staff that supported its
804
informationsharing organization. Another organization recruited
805
staff from its industry who had relevant technical experience and
806
understood the organization's role in the industry. In addition,
807
one of the organizations used contractors to maintain its
808
communications mechanisms and analyze reported incidents.
809
810
811
812
Information on Critical Success Factors
813
and Challenges Can Benefit Critical Infrastructure Protection
814
In addition, the representatives from organizations without
815
professional and administrative staffs believed that an even more
816
difficult challenge was encouraging volunteers to donate additional
817
time to perform the administrative tasks required to organize
818
meetings and further facilitate information sharing. In one
819
organization, the leader had taken most of the responsibility for
820
these tasks.
821
Information sharing and coordination among organizations are
822
important aspects of producing comprehensive and practical
823
approaches to combating computer-based attacks. Information on
824
threats and incidents experienced by others can help an
825
organization identify trends, better understand the risks it faces,
826
and determine what preventative measures should be implemented. In
827
addition, comprehensive, timely information on incidents can help
828
federal and nonfederal analysis centers determine the nature of an
829
attack, provide warnings, and advise on how to mitigate an imminent
830
attack.
831
The critical success factors and challenges described by
832
organizations experienced in sharing sensitive and time-critical
833
information and the lessons they have learned provide useful
834
insights for other entities who are also trying to develop means of
835
appropriately sharing information on computer-based vulnerabilities
836
and the related risks. As the government's critical infrastructure
837
protection strategy evolves, both public and privatesector entities
838
can adopt the practices described to
839
840
841
842
establish trusted relationships with a wide variety of
843
federal and nonfederal entities that may be in a position to
844
provide potentially useful information and advice on
845
vulnerabilities and incidents;
846
847
848
849
develop standards and agreements on how shared
850
information will be used and protected;
851
852
853
854
establish effective and appropriately secure
855
communication mechanisms;
856
857
858
859
take steps to ensure that sensitive information is not
860
inappropriately disseminated, which may require statutory
861
changes;
862
863
864
865
ensure that benefits are realized by developing and
866
maintaining staff with the skills to support analytical
867
capabilities and facilitate communication among information-sharing
868
partners;
869
870
871
• obtain the support of senior officials in both federal and
872
nonfederal entities; and
873
• obtain adequate funding.
874
The Congress can play a key role in facilitating the
875
information-sharing aspect of critical infrastructure protection,
876
as it did regarding the Year 2000 computing challenge. For example,
877
the Congress can actively monitor progress in meeting critical
878
infrastructure protection goals, including improved information
879
sharing, and promote trust by assisting in clarifying the way
880
federal agencies may use sensitive information provided for
881
critical infrastructure protection purposes. Prior to 2000, the
882
Congress held important hearings on Year 2000 readiness, and, in
883
1998, passed legislation intended to address concerns from
884
private-sector entities about exposure to legal liability and
885
antitrust law violations that might arise due to sharing
886
information on Year 2000 readiness.
887
The Congress is currently considering measures intended to
888
address several of the practices and challenges we identified. Two
889
recently introduced bills, S. 1456 and H.R. 2435, include
890
provisions that address the receipt, care, and storage of critical
891
infrastructure protection information as well as specific
892
exemptions from public disclosure of such information.
893
Implementation of such provisions, as well as other monitoring
894
actions, could facilitate information sharing and, thus, federal
895
and private efforts to protect critical infrastructures.
896
In commenting on a draft of this report,
897
the participants of our study
898
899
900
Participants Comments
901
agreed with the critical success factors and challenges that we
902
identified. Several provided additional supporting points and
903
examples, which we have included in the report as appropriate.
904
As we agreed with your staff, unless you publicly announce the
905
contents of this report earlier, we plan no further distribution of
906
it until 30 days from the date of this letter. At that time, we
907
will send copies to the Chairman, Vice Chairman, and Ranking
908
Minority Member of the Joint Economic Committee. In addition, we
909
are sending copies to other interested congressional committees. We
910
are also sending copies to the heads of the lead agencies,
911
including the Secretaries of Commerce, Defense, Energy, Health and
912
Human Services, State, Transportation, and the Treasury and the
913
U.S. Attorney General; the Administrator, Environmental Protection
914
Agency; the Director, Federal Emergency Management Agency; the
915
Director, Federal Bureau of Investigation; the Director of Central
916
Intelligence; the Assistant to the President for Science and
917
Technology; the Director, Critical Infrastructure Assurance Office;
918
the Director, National Infrastructure Protection Center; the
919
organizations that participated in our study; and other interested
920
parties. We will make copies available to other interested parties
921
upon request. This report also will be available on our
922
Web site at www.gao.gov.
923
If you have any questions, please call me at (202) 512-3317, or
924
you may e
925
mail me at [email protected]. Major contributors to this
926
report included Jean Boltz, Michael Gilmore, Danielle Hollomon, and
927
Catherine Schweitzer.
928
Sincerely yours,
929
930
Robert F. Dacey Director, Information Security Issues Appendix
931
I
932
933
934
Objectives, Scope, and Methodology
935
Our overall objective was to identify information-sharing
936
practices that federal organizations and others can adopt to
937
improve their ability to understand, anticipate, and address
938
computer-based vulnerabilities and incidents. Our specific
939
objectives were to identify (1) critical success factors in
940
building information-sharing relationships and (2) related
941
challenges and how to address them.
942
To meet these objectives, we studied 11 federal and nonfederal
943
entities experienced in developing relationships and procedures for
944
information sharing. We identified these organizations by
945
soliciting suggestions from a variety of sources, including our
946
analysts familiar with information-sharing organizations and
947
members of our Executive Council on Information Management and
948
Technology, which is a group of executives with extensive
949
experience in information technology management who advise us on
950
major information management issues affecting federal agencies.
951
These sources recommended over 30 public and private organizations.
952
After initial discussions and further research, we narrowed our
953
focus to 11 organizations that most closely met our criteria of
954
being a recognized, competent information-sharing entity, primarily
955
sharing sensitive or timecritical information pertaining to
956
computer-based vulnerabilities and incidents.
957
These 11 organizations included among their membership
958
representatives from federal, state, and local governments; private
959
companies of varying sizes; and the academic community. The
960
individuals who were involved in the organizations had various
961
technical and business backgrounds-such as information security
962
specialists, computer scientists, engineers, auditors, lawyers, law
963
enforcement officers, and medical professionals. Each of the 11
964
organizations covered by our review is described in Appendix
965
II.
966
To identify common critical success factors, we researched each
967
organization, analyzed relevant documents, interviewed pertinent
968
organization officials and knowledgeable members, observed meetings
969
and other operations, and compared their experiences for
970
similarities. To identify challenges associated with successful
971
information sharing, we obtained the views of officials and members
972
of each organization and reviewed supporting documentation, when it
973
was available.
974
We solicited comments from each of the eleven organizations that
975
we studied. Additional supporting points and examples were
976
incorporated as
977
Appendix I Objectives, Scope, and Methodology
978
appropriate. We conducted our study from May 2001 through
979
October 2001 in accordance with generally accepted government
980
auditing standards.
981
Appendix II
982
983
984
The 11 Organizations That Participated in
985
GAO's Study of Information Sharing
986
The Agora
987
The Agora is a Seattle-based regional network of over 600
988
professionals representing a variety of fields, including
989
information systems security; law enforcement; local, state, and
990
federal governments; engineering; information technology;
991
academics; and other specialties. The participants represent over
992
150 commercial firms and 140 government entities located in 20 U.S.
993
States and 5 Canadian Provinces.
994
Founded in 1995, the Agora formed to address the enormous
995
security challenges brought about by new computer, network, and
996
Internet technologies. The Agora's objectives are to
997
998
999
1000
establish confidential ways for organizations to share
1001
sensitive information about common problems and best practices for
1002
dealing with security threats,
1003
1004
1005
1006
develop and share knowledge about how to protect
1007
electronic infrastructures,
1008
1009
1010
1011
establish shared services that enhance participants'
1012
ability to successfully perform their daily jobs,
1013
1014
1015
1016
prompt more research specific to electronic information
1017
systems security,
1018
1019
1020
1021
share educational opportunities, and
1022
1023
1024
1025
enjoy the benefits of the fostered
1026
relationships.
1027
1028
1029
Information sharing occurs primarily through quarterly meetings
1030
that typically include 175 Agora members. In addition to the
1031
quarterly meetings, informal meetings and teleconferences are held
1032
among members on an ad hoc basis to discuss issues as they arise,
1033
such as assisting entities under attack.
1034
1035
1036
Centers for Disease Control and
1037
Prevention
1038
The Centers for Disease Control and Prevention (CDC), which is
1039
an agency of the Department of Health and Human Services, is
1040
recognized as the lead federal agency for protecting the health and
1041
safety of people at home and abroad. CDC seeks to accomplish its
1042
mission by working with partners throughout the nation and world to
1043
monitor health, detect and investigate health problems, conduct
1044
research to enhance the prevention of disease,
1045
Page 24 GAO-02-24 Information Sharing Practices
1046
Appendix II The 11 Organizations That Participated in GAO's
1047
Study of Information Sharing
1048
PulseNet
1049
Epidemic Information Exchange
1050
The Data Web
1051
foster safe and healthful environments, and provide leadership
1052
and training.
1053
CDC uses several information-sharing computer systems to help
1054
accomplish its mission, three of which were covered by our review
1055
and are described below.
1056
In 1998, CDC officially announced the establishment of PulseNet,
1057
a national network of public health laboratories that helps
1058
epidemiologists rapidly identify clusters of foodborne illness and
1059
alerts others in the surrounding geographic area and throughout the
1060
country regarding a possible outbreak. By sharing information on
1061
outbreaks quickly through computer systems connected to the
1062
Internet, PulseNet allows CDC to very quickly notify public health
1063
officials and food regulators of the health threat and assist
1064
investigators in identifying and removing the food source of the
1065
outbreak from distribution channels, thus mitigating the health
1066
risks associated with such outbreaks.
1067
In November 2000, the Epidemic Information Exchange system was
1068
implemented as an interactive, secure, Internet-based network that
1069
provides information on epidemic outbreaks, toxic exposures, and
1070
other health events as they occur. Epidemic Intelligence Service
1071
officers at CDC, state and local laboratory personnel, and other
1072
public health officials use the system to securely conduct on-line
1073
discussions about posted events, communicate with public health
1074
officials, and request both financial and nonfinancial assistance.
1075
Because of the sensitivity of the system's information, both users
1076
and providers of the information must be granted access to the
1077
system. In addition, before the information is made available to
1078
the system's users, editors and a medical director, who is a
1079
physician, review the information to ensure accurate information
1080
exchange.
1081
The Data Web, jointly developed by CDC and the U.S. Census
1082
Bureau, is a newly implemented system for cataloging and sharing
1083
social science data across the Internet. In this regard, the Data
1084
Web brings together demographic, economic, environmental, health,
1085
and other data maintained on different systems by different
1086
organizations wishing to make available their
1087
social-science-related data to a wide audience using a variety of
1088
systems.
1089
The primary users of the Data Web are scientists, researchers,
1090
academicians, business personnel, and professionals who need
1091
real-time
1092
Appendix II The 11 Organizations That Participated in GAO's
1093
Study of Information Sharing
1094
1095
1096
CERT® Coordination Center
1097
access to government and scientific data originating from
1098
diverse systems and disciplines. While most data are widely
1099
accessible, the system provides a means for data providers to
1100
restrict access to sensitive information.
1101
The CERT® Coordination Center (CERT/CC) was established in 1988
1102
by the Defense Advanced Research Projects Agency. The center is
1103
charged with
1104
1105
1106
(1)
1107
establishing a capability to quickly and effectively
1108
coordinate communication among experts to limit the damage
1109
associated with, and respond to, computer-based incidents; (2)
1110
conducting research into the prevention of security incidents; and
1111
(3) building awareness of security issues across the Internet
1112
community. In this role, CERT/CC (1) receives from and provides to
1113
system and network administrators, technology managers, and policy
1114
makers Internet security-related information and
1115
1116
1117
(2)
1118
provides guidance and coordination for responding to
1119
major Internet security events, such as the Melissa virus and Year
1120
2000 conversion challenge. The center attempts to be an unbiased
1121
and trusted source of information, in part by providing trend and
1122
composite information only, by deleting information that would
1123
allow victims to be identified, and by coordinating the response
1124
information it provides with academic, government, and corporate
1125
experts. Through this collaboration, CERT/CC has developed a
1126
distributed model for incident response teams. It also provides
1127
leadership in the response team community by assisting
1128
organizations in developing their own emergency response
1129
capabilities.
1130
1131
1132
1133
1134
Federal Computer Incident Response
1135
Center
1136
The Federal Computer Incident Response Center (FedCIRC) is the
1137
focal point for dealing with computer-related incidents affecting
1138
federal civilian agencies. Originally established in 1996 by the
1139
National Institute of Standards and Technology, the center has been
1140
administered by the General Services Administration since October
1141
1998.
1142
FedCIRC's primary purposes are to provide a means for federal
1143
civilian agencies to work together to handle security incidents,
1144
share related information, and solve common security problems. In
1145
this regard, FedCIRC
1146
1147
1148
1149
provides federal civilian agencies with technical
1150
information, tools, methods, assistance, and guidance;
1151
1152
1153
1154
provides coordination and analytical support;
1155
1156
1157
Appendix II The 11 Organizations That Participated in GAO's
1158
Study of Information Sharing
1159
1160
1161
International Information Integrity
1162
Institute
1163
1164
1165
1166
encourages development of quality security products and
1167
services through collaborative relationships with federal agencies,
1168
academia, and private industry;
1169
1170
1171
1172
promotes incident response and handling procedural
1173
awareness within the federal government;
1174
1175
1176
1177
fosters cooperation among federal agencies for
1178
effectively preventing, detecting, handling, and recovering from
1179
computer security incidents;
1180
1181
1182
1183
communicates alert and advisory information regarding
1184
potential threats and emerging incident situations; and
1185
1186
1187
1188
augments the incident response capabilities of federal
1189
agencies.
1190
1191
1192
In accomplishing these efforts, FedCIRC draws on expertise from
1193
the Department of Defense, the intelligence community, academia,
1194
and federal civilian agencies. In addition, FedCIRC collaborates
1195
with the Federal Bureau of Investigation's (FBI) National
1196
Infrastructure Protection Center in planning for and dealing with
1197
criminal activities that pose a threat to the critical information
1198
infrastructure.
1199
The International Information Integrity Institute (I-4) is
1200
sponsored by AtomicTangerine, a provider of information security
1201
consulting services whose clients include major global
1202
corporations. I-4 is a forum for sharing information among its
1203
member companies on developing and sustaining effective information
1204
security programs to support their global business environments.
1205
Its membership is limited to 75 of Business Week's Global 1000
1206
companies. In addition, I-4 maintains alliances with leading
1207
research organizations, such as SRI International and Kent Ridge
1208
Digital Labs, to stay abreast of the latest technical,
1209
communications, legal, and economic developments. AtomicTangerine
1210
also maintains a number of alliance partnerships with companies
1211
that specialize in various areas of emerging technology and
1212
architecture, which help provide information to I-4 members.
1213
I-4 members communicate primarily through forums, regional
1214
meetings, and a secure Web site that allows for member queries and
1215
distribution of analytical reports. I-4 forums are held three times
1216
a year, allowing representatives from all 75 I-4 member companies
1217
an opportunity to establish and maintain personal contacts, make
1218
formal presentations with
1219
Appendix II The 11 Organizations That Participated in GAO's
1220
Study of Information Sharing
1221
follow-on discussions, and hold informal discussions about
1222
information protection and risk-management issues. Each member
1223
company is encouraged to send two representatives. Regional
1224
meetings, held five to six times a year, are generally shorter and
1225
targeted at members in a specific geographic region, such as the
1226
United States, Europe, or Asia. During these meetings, selected
1227
topics are discussed in greater depth than at forums. Throughout
1228
the year, members continuously carry on dialogs through queries on
1229
information security policy, procedure, and technology management
1230
issues, moderated by the I-4 staff.
1231
The National InfraGard Program began as a
1232
pilot project in 1996 in the
1233
1234
1235
InfraGard
1236
Cleveland FBI Field Office to build a better relationship
1237
between the FBI and the private sector in addressing cyber and
1238
physical threats. The National Infrastructure Protection Center,
1239
which is an interagency center housed at the FBI, in conjunction
1240
with representatives from private industry, the academic community,
1241
and government, has worked to expand InfraGard by encouraging
1242
development of local chapters associated with each of the FBI's 56
1243
field offices. As of October 2001, InfraGard had over 2,000 members
1244
and 65 chapters.
1245
InfraGard chapters establish direct contact between law
1246
enforcement and infrastructure owners and operators, such as
1247
utility companies and health care organizations, through periodic
1248
meetings and a secure Web site. These communication mechanisms
1249
allow the InfraGard to
1250
1251
1252
1253
gather information on cyber threats, vulnerabilities, and
1254
intrusions and distribute it to members,
1255
1256
1257
1258
educate the public and members on infrastructure
1259
protection,
1260
1261
1262
1263
disseminate sensitive information to members who have
1264
signed a secure access agreement, and
1265
1266
1267
1268
distribute analytical products on information received
1269
from InfraGard members.
1270
1271
1272
In June 2001, InfraGard members elected a National Executive
1273
Board to govern the national InfraGard program and draft new
1274
policies and procedures to enhance the program's effectiveness.
1275
Appendix II The 11 Organizations That Participated in GAO's
1276
Study of Information Sharing
1277
1278
1279
Joint Task Force- Computer Network
1280
Operations
1281
The Joint Task Force-Computer Network Operations (JTF-CNO)
1282
(formerly the Joint Task Force-Computer Network Defense) is the
1283
primary Department of Defense entity for coordinating and directing
1284
internal activities to detect computer-based attacks, contain
1285
damage, and restore computer functionality when disruptions occur.
1286
The unit was established in 1998 to serve as one organization with
1287
overall authority for directing defensive actions against
1288
computer-based attacks across the entire Department. As such,
1289
JTF-CNO is supported by the Departments of the Army, Navy, and Air
1290
Force and the Marine Corps computer emergencyresponse teams and
1291
other Defense components.
1292
In April 2001, the JTF-CNO's scope of responsibility was
1293
expanded to include a new operational mission: computer network
1294
attack. In addition to expanding mission responsibilities, the
1295
JTF-CNO is growing in size and depth to better meet increased
1296
network defense responsibilities. The JTF-CNO expansion
1297
significantly increases its ability to perform the following:
1298
(1) preventive activities, such as conducting security reviews
1299
and issuing vulnerability alerts; (2) coordination and monitoring
1300
detection activities performed by components, including monitoring
1301
automated intrusiondetection systems; (3) investigative and
1302
diagnostic activities; and (4) event handling and response
1303
activities, which involve disseminating information and providing
1304
technical assistance to system administrators so that they can
1305
appropriately respond to cyber attacks.
1306
JTF-CNO maintains a close relationship with the CERT/CC, the
1307
NIPC, and FedCIRC by participating in joint technical exchanges,
1308
working groups, and countermeasure development teams.
1309
In 1983, the National Coordinating Center
1310
for Telecommunications (NCC),
1311
1312
1313
National Coordinating
1314
1315
which is operated by the National
1316
Communications System1 and staffed by government employees and
1317
representatives from major Telecommunications telecommunications
1318
service providers, was created by Executive Order
1319
12472 as a joint industry and government organization to handle
1320
emergency
1321
1In 1982, the National Communications System was established by
1322
executive order as a federal interagency group responsible for the
1323
national security and emergency preparedness telecommunications.
1324
These responsibilities include planning for, developing, and
1325
implementing enhancements to the national telecommunications
1326
infrastructure, which includes the Internet, to achieve
1327
effectiveness in managing and using national telecommunication
1328
resources to support the federal government during any
1329
emergency.
1330
Page 29 GAO-02-24 Information Sharing Practices
1331
Appendix II The 11 Organizations That Participated in GAO's
1332
Study of Information Sharing
1333
1334
1335
Network Security Information
1336
Exchanges
1337
requests related to the physical telecommunications network. The
1338
NCC's industry and government representatives' specific functions
1339
include
1340
1341
1342
1343
advising executives and senior officials,
1344
1345
1346
1347
maintaining points of contact with the parent
1348
organizations,
1349
1350
1351
1352
coordinating and directing prompt restoration of
1353
telecommunications services in support of national security and
1354
emergency preparedness needs during crises such as natural
1355
disasters or war, and
1356
1357
1358
1359
producing emergency response plans and procedures as a
1360
result of lessons learned during actual events.
1361
1362
1363
In January 2000, the NCC was recognized by the President's
1364
National Security Council as the information sharing and analysis
1365
center (ISAC) for the telecommunications sector. As such, the NCC
1366
is responsible for facilitating the exchange of information among
1367
government and industry participants regarding computer-based
1368
vulnerability, threat, and intrusion information affecting the
1369
telecommunications infrastructure. Also, it analyzes data received
1370
from telecommunications industry members, government, and other
1371
sources to avoid or lessen the impact of a crisis affecting the
1372
telecommunications infrastructure.
1373
Since its recognition as an ISAC, NCC's membership has expanded
1374
beyond traditional telecommunications entities, such as telephone
1375
companies, to include other technology companies involved in the
1376
telecommunications infrastructure.
1377
In 1991, government and industry Network Security Information
1378
Exchanges (NSIEs) were established by the National Communications
1379
System and the President's National Security Telecommunications
1380
Advisory Committee (NSTAC)2 to identify, research, and share
1381
information about computer-based incidents that could negatively
1382
affect national security and emergency preparedness
1383
telecommunications. The goal of the
1384
2In 1982, the National Security Telecommunications Advisory
1385
Committee, which is composed of presidentially appointed senior
1386
executives from 30 major U.S. corporations in the
1387
telecommunications and financial services industries, was
1388
established to advise the President on national security and
1389
emergency preparedness telecommunications issues.
1390
Page 30 GAO-02-24 Information Sharing Practices
1391
Appendix II The 11 Organizations That Participated in GAO's
1392
Study of Information Sharing
1393
1394
1395
New York Electronic Crimes Task Force
1396
NSIEs is to exchange information about the security of the
1397
public telecommunications network, including the Internet, to
1398
improve the overall reliability and security of the entire network.
1399
In addition, the NSIEs strive to improve each member's total
1400
knowledge and understanding of the risks to the nation's
1401
telecommunications.
1402
Although the two NSIEs are managed separately, their activities
1403
are closely coordinated, and they meet jointly every 2 months to
1404
exchange information and views about current threats,
1405
vulnerabilities, incidents, and solutions. As of August 2001, the
1406
government and industry NSIEs collectively had over 50 members from
1407
federal agencies and NSTAC member corporations, as well as a
1408
limited number of invited experts. Federal government members
1409
represent agencies that have functions related to
1410
telecommunications research, standards, regulation, law
1411
enforcement, or intelligence or are major telecommunications users.
1412
Industry NSIE members include representatives from
1413
telecommunications service providers, equipment vendors, systems
1414
integrators, and the financial services industry-a major
1415
telecommunications user.
1416
In 1995, the New York Electronic Crimes Task Force was formed by
1417
the United States Secret Service to investigate electronic crimes
1418
associated with computer-generated counterfeit currency,
1419
counterfeit checks, credit card fraud, telecommunications fraud,
1420
and access device fraud, to name a few. In addition, the task force
1421
has
1422
1423
1424
1425
developed educational and training programs for children
1426
and parents to protect children from being exploited through the
1427
Internet,
1428
1429
1430
1431
encouraged research and development of tools and
1432
methodologies to prevent crime,
1433
1434
1435
1436
supported law enforcement education, and
1437
1438
1439
1440
promoted development of trusted relationships between the
1441
public and the private sector.
1442
1443
1444
The task force has over 400 individual members drawn from 50
1445
different federal, state, and local law enforcement agencies; 100
1446
private companies; and 6 universities. The Secret Service has also
1447
assigned eight agents who have received specialized training in all
1448
areas of electronic crimes through its Electronic Crimes Special
1449
Agent Program. The task force has created
1450
Appendix II The 11 Organizations That Participated in GAO's
1451
Study of Information Sharing
1452
1453
1454
North American Electric Reliability
1455
Council
1456
this alliance to pool the expertise, authorities, and technical
1457
resources required to address electronic crimes-an effort that has
1458
been recognized by communities across the country and
1459
internationally as a model for local interagency cooperation and
1460
private/public partnership. South Carolina has recently implemented
1461
a similar model.
1462
The North American Electric Reliability Council (NERC) was
1463
formed in 1968 after a 1965 power outage crippled much of the
1464
northeastern United States. The council is a voluntary organization
1465
of organizations involved in bulk power production and distribution
1466
to promote standards and procedures and improve the reliability of
1467
the electric power supply. Due to the interconnectivity and
1468
interdependency of the electric power grid, information sharing is
1469
a necessity for (1) maintaining the reliability of the power supply
1470
and (2) conducting business transactions in a deregulated
1471
environment. NERC depends on reciprocity, peer pressure, and the
1472
mutual self-interest of its members to prevent any future
1473
occurrence like the 1965 incident. It also serves as an officially
1474
recognized ISAC for combating computer-based attacks on the
1475
electric power industry. In this capacity, it cooperates with the
1476
federal National Infrastructure Protection Center to identify
1477
threat trends and vulnerabilities and disseminate assessments,
1478
advisories, and alerts to its members.
1479
NERC membership consists of representatives from each of the 10
1480
regional councils that represent geographic regions encompassing
1481
the entire United States and Canada and a small part of Mexico.
1482
Because any organization that is part of the power grid can
1483
potentially affect the operation and stability of the entire grid,
1484
members of these regional councils come from all segments of the
1485
electric industry: investor-owned utilities; federal power
1486
agencies; rural electric power cooperatives; state, municipal, and
1487
provincial utilities; independent power producers; power marketers;
1488
and other interested parties.
1489
The council primarily uses various databases accessible through
1490
secure Web sites for disseminating and collecting shared
1491
information on many aspects of energy generation and transfer. In
1492
addition, NERC allows members to create committees designed to
1493
solve particular problems or support ongoing efforts, such as
1494
standards setting and critical infrastructure protection.
1495
1496
1497
GAO's Mission
1498
The General Accounting Office, the investigative arm of
1499
Congress, exists to support Congress in meeting its constitutional
1500
responsibilities and to help improve the performance and
1501
accountability of the federal government for the American people.
1502
GAO examines the use of public funds; evaluates federal programs
1503
and policies; and provides analyses, recommendations, and other
1504
assistance to help Congress make informed oversight, policy, and
1505
funding decisions. GAO's commitment to good government is reflected
1506
in its core values of accountability, integrity, and
1507
reliability.
1508
1509
1510
Obtaining Copies of GAO Reports and Testimony
1511
The fastest and easiest way to obtain copies of GAO documents is
1512
through the Internet. GAO's Web site (www.gao.gov) contains
1513
abstracts and full-text files of current reports and testimony and
1514
an expanding archive of older products. The Web site features a
1515
search engine to help you locate documents using key words and
1516
phrases. You can print these documents in their entirety, including
1517
charts and other graphics.
1518
Each day, GAO issues a list of newly released reports,
1519
testimony, and correspondence. GAO posts this list, known as
1520
"Today's Reports," on its Web site daily. The list contains links
1521
to the full-text document files. To have GAO E-mail this list to
1522
you every afternoon, go to our home page and complete the
1523
easy-to-use electronic order form found under "To Order GAO
1524
Products."
1525
1526
Order by Mail or Phone
1527
The first copy of each printed report is free. Additional copies
1528
are $2 each. A check or money order should be made out to the
1529
Superintendent of Documents. GAO also accepts VISA and Mastercard.
1530
Orders for 100 or more copies mailed to a single address are
1531
discounted 25 percent. Orders should be sent to:
1532
U.S. General Accounting Office
1533
P.O. Box 37050 Washington, D.C. 20013
1534
To order by Phone: Voice: (202) 512-6000 TDD: (301) 413-0006
1535
Fax: (202) 258-4066
1536
GAO Building
1537
1538
1539
Visit GAO's Document
1540
Room 1100, 700 4th Street, NW (corner of 4th and G Streets, NW)
1541
Distribution Center Washington, D.C. 20013
1542
Contact:
1543
To Report Fraud,
1544
1545
1546
1547
Waste, and Abuse in Federal Programs
1548
1549
Web site: www.gao.gov/fraudnet/fraudnet.htm,E-mail:
1550
[email protected], or1-800-424-5454 (automated
1551
answering system).
1552
1553
Jeff Nelligan, Managing Director, [email protected] (202)
1554
512-4800
1555
1556
1557
1558
Public Affairs
1559
U.S. General Accounting Office, 441 G. Street NW, Room 7149,
1560
Washington, D.C. 20548
1561
1562
Presorted Standard Postage & Fees Paid GAO Permit No.
1563
GI00
1564
United States General Accounting Office Washington, D.C.
1565
20548-0001
1566
Official Business Penalty for Private Use $300
1567
Address Correction Requested
1568
1569
1570
1571
1572
1573