Retrofitting Engineering Information Systems (Eis) To Older Military Facilities In Saudia Arabia

LITERATURE REVIEW

Introduction

Security is an extremely important issue in the development of distributed systems.This applies in particular to Web-based systems, which communicate over an open network. Failures of security mechanisms may cause very high damage with financial and legal implications. Security concerns, both on the part of enterprises and consumers, are one of the major reasons why new technologies such as E-commerce or Egovernment are used very reluctantly (Anderson, 2001: 87).

Developing security-critical systems is very difficult. Security is a complex nonfunctional requirement affecting all parts of a system at all levels of detail. To secure a system, merely adding mechanisms such as cryptography in some places is not sufficient. Whether a system is secure depends crucially on the complex interplay of its components and the assumptions about its environment (Vetterling & Wimmel, 2002: 49). A single weakness can compromise the security of the entire system. Furthermore, many systems are developed initially without security in mind. Reasons for that are that they were designed for a secure environment such as a local network, that existing legacy systems are to be adapted, or because they were first developed as a functional prototype. Retrofitting security into an existing system is generally believed to be extremely hard to achieve, and it is in effect often advised against doing so at all. In this article we report on the experiences of a Java project where exactly this retrofitting was done after developing initial prototypes (Gong, 1999: 63).

The RAC system is an Internet information system based on the "push" principle: information is presented to the user on a client application ("pushlet") and updated when necessary, without the user having to explicitly check for such updates. The server regularly or on demand contacts the client for updates. The RAC system was initially developed as a prototype without security functionality as its focus was targeting to be production companies' internal information systems (Saltzer & Schroeder, 1975: 24).

In this paper, we describe a method to carry out a security analysis of an existing system and to introduce appropriate mechanisms to achieve high trustworthiness. Our method is demonstrated at the example of the RAC system. It is based on a combination of an evolutionary approach and method suggested in. We comment on experiences and difficulties in adding security to an existing system, in particular in the context of Web-based Java applications.

Related Work. The consideration of additional or changed requirements within the lifetime of a system is one of the main aims of iterative processes, such as Boehm's Spiral Model [4]. Few works are available on the integration of security aspects into the development process. In [1], Eckert suggests a top-down approach, which we used as a basis for our work (Harriman, 1990: 91). A mapping of ITSEC security requirements to development activities in the German V-Model 97 is given in [5]. [3] describes a lifecycle process based on the Evaluation Assurance Requirements of the Common Criteria for Security Evaluation, at ...