Abstract:
This document describes the strategy for developing the evidence that an extension of the Joint Maritime Command Information System (JMCIS) [22] satisfies its critical security requirements. The motivation for this work is the Multi-Level Security (MLS) Processing for Copernicus 6.3A Core Technology Program, the primary objective of which is to facilitate the development and implementation of the Copernicus architecture [35] by considering information security as a core element of the overall Copernicus design. The Copernicus concept can overcome many of the shortfalls of existing C 4 I support by eliminating wholesale message broadcast in favor of a smart push and warrior pull approach that permits maintaining a common tactical picture across a theater of operations. JMCIS provides a common operating environment for Naval tactical decision aids that supports this approach by replacing existing stovepipe systems with client-server architectures. Although JMCIS operation is currently limited to a local area, such as a facility on shore or aboard ship, it is an important step in providing an integrated, tailorable and flexible C 4
Citations
|
361
|
Statemate: A Working Environment for the Development of Complex Reactive Systems
– Harel, Lachover, et al.
- 1990
|
|
350
|
Literate Programming
– Knuth
- 1984
|
|
59
|
Software Testability: The New Verification
– Voas, Miller
- 1995
|
|
32
|
eves: An overview
– Craigen, Kromodimoeljo, et al.
- 1991
|
|
21
|
Weaving a Program: Literate Programming in
– Sewell
- 1989
|
|
18
|
Toward a Comprehensive INFOSEC Certification Methodology
– Payne, Froscher, et al.
- 1993
|
|
11
|
A practical approach to high assurance multilevel secure computing service
– Froscher, Kang, et al.
- 1994
|
|
8
|
On the Formal Semantics of Statecharts (Extended Abstract
– Harel, Pnueli, et al.
- 1987
|
|
7
|
Software testability: The new veri cation
– Voas, Miller
- 1995
|
|
4
|
The Safety Argument Manager: An Integrated Approach to the Engineering and Safety Assessment of Computer Based Systems
– Wilson, McDermid, et al.
- 1996
|
|
3
|
Increasing assurance with literate programming techniques
– Moore, Payne
- 1996
|
|
3
|
Toward a comprehensive INFOSEC certi cation methodology
– Payne, Froscher, et al.
- 1993
|
|
2
|
Uses of an argument framework; its data model and generic features
– Pygott, Wilson
- 1996
|
|
1
|
JMCIS database concept of operations
– Davis
- 1995
|
|
1
|
The Languages of Statemate
– Inc
- 1991
|
|
1
|
Statemate 5.0 Features
– Inc
- 1993
|
|
1
|
Statemate 6.0 Features
– Inc
- 1995
|
|
1
|
Copernicus architecture functional overview
– Inc
- 1994
|
|
1
|
Navy Tactical Command Systems - Afloat: Client Database Document (CBD) for version 2.1
– Inc
- 1994
|
|
1
|
NIPS 2.1 applications
– Inc
- 1994
|
|
1
|
A data Pump for communication. Sumbmitted for publication; also available as NRL
– Kang, Moskowitz
- 1994
|
|
1
|
Trusted Tactical Aircraft Mission Planning Systems guard concept of operations and requirements definition
– Laboratory
- 1995
|
|
1
|
ASAM-II: Concepts and process
– McDermid, Wilson, et al.
- 1996
|
|
1
|
A behavioral requirements model for the NRL
– Moore
- 1995
|
|
1
|
JMCIS Information Flow Improvement (JIFI) Statemate elements dictionary
– Moore, Rock
- 1995
|
|
1
|
Warfare Systems Command (PMW 171). Joint Maritime Command Information System version 2.1 (Sensitive Compartmented Information) security requirements document
– Space, Naval
- 1994
|
|
1
|
Warfare Systems Command. Software architecture guide for the Unified Build
– Space, Naval
- 1993
|
|
1
|
Naval Warfare Systems Command
– Space
- 1992
|
|
1
|
Navy Tactical Command Systems - A oat: Client Database Document (CBD) for version 2.1
– Inc
- 1994
|
|
1
|
Naval Warfare Systems Command. Navy Tactical Command System - A oat (NTCS-A) Database Concept of Operations
– Space
- 1992
|
|
