лаба_10 / лаб_10_15_2

3.2.3Cold/Frost/Snow - AFE: 5.00

The various incident classes associated with this threat are shown in the following table:

62,500 Disclosure, Databases

Dollars

Figure 14.3 Cold/Frost/Snow - ALE's

12,500 Disclosure, Databases

Dollars

Figure 16.3 Cold/Frost/Snow - SLE's

3.2.4Data Destruction - AFE: 20.00

The various incident classes associated with this threat are shown in the following table:

Figure 13.4

5,000,000 Disclosure, Databases

Dollars

55,027 Direct, Dat abases

Dollars

Figure 14.4 Data Destruction - ALE's

Direct, Dat abases (1.1%)

Disclosure, Databases (98.9%)

Figure 15.4 Data Destruction - ALE's

250,000 Disclosure, Databases

Dollars

2,751 Direct, Dat abases

Dollars

Figure 16.4 Data Destruction - SLE's

3.2.5Data Disclosure - AFE: 3.00

The various incident classes associated with this threat are shown in the following table:

5,813 Disclosure, Databases

Dollars

Figure 14.5 Data Disclosure - ALE's

1,938 Disclosure, Databases

Dollars

Figure 16.5 Data Disclosure - SLE's

3.2.6Data Integrity Loss - AFE: 3.00

The various incident classes associated with this threat are shown in the following table:

Figure 13.6

16,576

Direct, Accts Rec

16,523

Direct, Applicatns

13,500

Disclosure, Personnel

8,171

Direct, Comms S/W

2,451

Direct, System S/W

1,921

Direct, Dat abases

443

Direct, Accts Pay

Dollars

Figure 14.6 Data Integrity Loss - ALE's

Disclosure, Personnel (22.7%)

Direct, Applicatns (27.7%)

Figure 15.6 Data Integrity Loss - ALE's

5,526

Direct, Accts Rec

5,507

Direct, Applicatns

4,500

Disclosure, Personnel

2,723

Direct, Comms S/W

817

Direct, System S/W

640

Direct, Dat abases

147

Direct, Accts Pay

3.2.7Flooding/Water Damage - AFE: 0.01

The various incident classes associated with this threat are shown in the following table:

Figure 13.7

100 Direct, Comms H/W

Dollars

6

Direct, Off Equip

3

Disclosure, Databases

Dollars

Figure 14.7 Flooding/Water Damage - ALE's

Disclosure, Databases (2.8%)

Direct, Off Equip (5.5%)

Direct, Comms H/W (91.7%)

Figure 15.7 Flooding/Water Damage - ALE's

10,001 Direct, Comms H/W

Dollars

625

Direct, Off Equip

250

Disclosure, Databases

Dollars

Figure 16.7 Flooding/Water Damage - SLE's

3.2.8Hardware Failure - AFE: 70.00

The various incident classes associated with this threat are shown in the following table:

Figure 13.8

26,250,000 Direct, Hardware

Dollars

Figure 14.8 Hardware Failure - ALE's

375,000 Direct, Hardware

Dollars

Figure 16.8 Hardware Failure - SLE's

3.2.9Pirating Key Personnel - AFE: 1.00

The various incident classes associated with this threat are shown in the following table:

There are no incidents associated with this threat.

The section below looks at each safeguard and indicates, for each threat, the ALE before and after the safeguard is implemented. The overall ALE for a threat is the sum of the ALEs for each of the associated incidents. The percentage by which the ALE is reduced by the safeguard is also indicated.

The next section contains a table indicating, for each safeguard, the ALE before (Original ALE) and after the safeguard is implemented.

The following is a table indicating, for each safeguard, the ALE before (Original ALE) and after the safeguard is implemented (ALE with Safeguard). This table also indicates the difference between the two ALE values.

Also shown is a barchart that provides a visual presentation of the difference in ALE for each safeguard.

2,545,362

Data Encryption

505,503

Application Cont rols

267,409

Security Policy

347

Life Cycle Management

85

Personnel Control

73

Passwords/Aut henticaion

Dollars

Instructions for preparing Final Reports.

In Phase 4, there are many different reports that can be generated. To facilitate the assembly of these smaller specialized reports into a single "Final Report" for submission to management, provision is made to attach the name of each selected report file (each is a .WRI file) to a list that is made available to the analyst at the end of the reporting phase, Phase 4.

A couple of points must be kept in mind when the final report is assembled; it is assumed that a word processor will be used to prepare the Final Report and the following are tasks and ideas that are within the purview of most word processors:

1. On the parameter screen in Phase 1, you indicated that the sensitivity level of the system being analyzed is 1. Because reports that deal with a system must bear markings that indicated that the report is of a similar level of sensitivity, you are warned that the word processor used in the assembly process must also be used to indicate, as both Headers and Footers, this level of sensitivity on EVERY page;

2.There is no provision in the RiskWatch system for the title page or pages that come before paragraphs, sections, or diagrams. The analyst wishing these must provide them himself using the facilities of the word processor employed;

3.The ordering of sections is left to the discretion of the analyst - some people prefer to have the Executive Summary as the very first section, even preceding the Table of Contents, while others may wish to

have their Table of Contents immediately following the Cover page;

4.Because of the strong possibility that different enterprises will opt to assemble different pieces (sub-reports) into their respective Final Reports, the Table of Contents for the Final Report is left to the analyst, using the power of a modern word processor.

5.In the text provided by RiskWatch as part of the reports that embody the results of the analysis and the initial data, there are several sections that are enclosed in triple square brackets (that is, [[[ and

]]] ). All text that is between these braces is given SOLELY as a guide to suggested text to surround the numbers that form the basis of the reports. The text serves no other purpose. Please replace this text with

other text that is more appropriate to your enterprise.