Requirements definition for survivable network systems

Linger, Richard C.; Mead, Nancy R.; Lipson, Howard F.

doi:10.1109/icre.1998.667804

Cited by 40 publications

(25 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Finally, a recently published survey on self-healing software systems [4] similarly points out that these systems originate both from research on fault-tolerant [25], selfstabilising [90] and survivable [91] systems, as well as in autonomic computing [52] and self-adaptive [35] systems. A lot of importance is given to feedback loops in self-healing systems, which can be implemented in various ways and at various levels, as well as to the system behaviours being guided by adaptable policies.…”

Section: Surveymentioning

confidence: 99%

Self-healing and self-repairing technologies

Frei

McWilliam

Derrick

et al. 2013

Int J Adv Manuf Technol

View full text Add to dashboard Cite

This article reviews the existing work in selfhealing and self-repairing technologies, including work in software engineering, materials, mechanics, electronics, MEMS, self-reconfigurable robotics, and others. It suggests a terminology and taxonomy for self-healing and selfrepair, and discusses the various related types of other self-* properties. The mechanisms and methods leading to selfhealing are reviewed, and common elements across disciplines are identified.

show abstract

Section: Surveymentioning

confidence: 99%

Self-healing and self-repairing technologies

Frei

McWilliam

Derrick

et al. 2013

Int J Adv Manuf Technol

View full text Add to dashboard Cite

show abstract

“…The concepts of damage and probability are also included. Furthermore, a networked survivable system [30] was specified which was used widely in real world. Vickie investigated some previous definitions [33] about survivability and then proposed his own definition, in which some features should be involved in the survivable system, such as threat, adaptability and continuity of service.…”

Section: Related Workmentioning

confidence: 99%

Investigating System Survivability from a Probabilistic Perspective

Zhao

Huang

Qin

et al. 2014

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARYSurvivability is an essential requirement of the networked information systems analogous to the dependability. The definition of survivability proposed by Knight in [16] provides a rigorous way to define the concept. However, the Knight's specification does not provide a behavior model of the system as well as a verification framework for determining the survivability of a system satisfying a given specification. This paper proposes a complete formal framework for specifying and verifying the concept of system survivability on the basis of Knight's research. A computable probabilistic model is proposed to specify the functions and services of a networked information system. A quantified survivability specification is proposed to indicate the requirement of the survivability. A probabilistic refinement relation is defined to determine the survivability of the system. The framework is then demonstrated with three case studies: the restaurant system (RES), the Warship Command and Control system (LWC) and the Command-and-Control (C2) system.

show abstract

“…Survivability properties can also be integrated into the requirements definition for new or evolving systems [9]. Figure 3 depicts an iterative model for defining survivable system requirements.…”

Section: Adding Survivability To System Requirementsmentioning

confidence: 99%

“…The purpose of the SSE-CMM pilot program [9], conducted during 1996, was to validate the model and appraisal method, focusing on the Security Engineering Process Areas (PAs). The pilots were performed under nondisclosure agreements with the host organizations, covering proprietary process information and assessment results.…”

Section: Crosstalk the Journal Of Defense Software Engineeringmentioning

confidence: 99%

“…To determine appropriate improvement actions, the organization must decide what capability they desire in each of the process areas, and address any deficiencies. An appraisal methodology, termed the System Security Appraisal Method (SSAM), was defined [8].The purpose of the SSE-CMM pilot program [9], conducted during 1996, was to validate the model and appraisal method, focusing on the Security Engineering Process Areas (PAs). The pilots were performed under nondisclosure agreements with the host organizations, covering proprietary process information and assessment results.…”

mentioning

confidence: 99%

See 1 more Smart Citation

Crosstalk: The Journal of Defense Software Engineering, Volume 13, No. 10

UT¹

2000

View full text Add to dashboard Cite

From the Publisher 4SpYou Cannot Pass the Buck on Reliable Network Security w.ho has the responsibility within your organization to ensure that the network everyone has come to rely upon stays operational? Typically, you may respond: "Oh, that is taken care of by our network administrator. They stay on top of that. That is why we pay them the big bucks!" Unfortunately, as we learn from Moira West-Brown in Avoiding the Trial-by Fire Approach to Security Incidents, "Most organizations do not even think of how to respond to a computer security incident until after they have experienced a significant one." Most of us probably do not care to know what is being done to keep our networks up until we are affected personally. How many of us were not impacted in some way by the recent Love Letter e-mail virus attack? West-Brown also points out that insurance coverage for security losses will likely be changing. Some insurance companies offer financial protection for third-party damages resulting from security breaches. However, she says, "It is only a matter of time before insurance companies begin to request more information about network security, and begin to raise the cost of general insurance coverage for companies that are ill prepared to detect and respond to computer-security incidents."Networks have become indispensable for conducting business everywhere-in government, industry, and your organization. Networked systems allow access to needed information rapidly, improving communications while reducing costs. This reduction in costs, however, could be easily overshadowed by the cost of security breaches as indicated in Improving the Security of Networked Systems, by Julia Allen, et al. They note that security breaches are on the rise, and the cost is increasing. Financial losses for reporting organizations have doubled to more than $265 million according to a recent survey. Is your organization at risk? How would you know? Read this article and discover that the goal of OCTAVE SM [1] is "to improve how well information assets are protected, putting organizations in a better position to achieve their missions." OCTAVE enables organizations to develop appropriate protection strategies by considering policy, management, administration, and other organizational issues, as well as technologies, to form a comprehensive view of the information security state ofthat organization. Another method providing a systematic means to assess and improve system survivability for risk reduction is described in The Survivability Imperative: Protecting Critical Systems by several authors of the Software Engineering Institute. Our modern society is increasingly dependent upon complex network environments. Complex systems may improve efficiency, but they also introduce additional intrusion risks by unknown parties with destructive motivations. These risks can be mitigated by incorporating survivability capabilities, according to the authors. "Survivability analysis is a prudent risk management technique in a world that increasingly dep...

show abstract

Requirements definition for survivable network systems

Cited by 40 publications

References 11 publications

Self-healing and self-repairing technologies

Self-healing and self-repairing technologies

Investigating System Survivability from a Probabilistic Perspective

Crosstalk: The Journal of Defense Software Engineering, Volume 13, No. 10

Contact Info

Product

Resources

About