Writing Effective Security Abuse Cases

Thitima Srivratanakul; John Andrew Clark; Fiona Polack

Writing Effective Security Abuse Cases

Thitima Srivratanakul, John Andrew Clark, Fiona Polack

Computer Science

Research output: Book/Report › Other report

Abstract

We grow increasingly dependent on the appropriate operation of computer-based systems. One aspect of such systems is security. As systems become more complex current means of analysis will probably prove ineffective. In the safety domain a variety of analysis techniques has emerged over many years. These have proved surprisingly effective. Since the safety and security domains share many similarities, various authors have suggested that safety techniques might usefully find application in security. This report takes one such technique, HAZOPs, and applies it to one widely used informal design component – UML’s use cases.

Original language	English
Publisher	Department of Computer Science, University of York
Number of pages	52
Publication status	Published - 2004

Publication series

Name	York Computer Science Technical Report
Publisher	Department of Computer Science, University of York
No.	YCS-2004-375
Volume	YCS

Keywords

UML Use Cases
HAZOPS
Threat Model

Access to Document

YCS 2004 375
Freely available from York.
Final published version, 1.11 MB

Cite this

@book{2870fe32b0bf4b8c80284cb94551506e,

title = "Writing Effective Security Abuse Cases",

abstract = "We grow increasingly dependent on the appropriate operation of computer-based systems. One aspect of such systems is security. As systems become more complex current means of analysis will probably prove ineffective. In the safety domain a variety of analysis techniques has emerged over many years. These have proved surprisingly effective. Since the safety and security domains share many similarities, various authors have suggested that safety techniques might usefully find application in security. This report takes one such technique, HAZOPs, and applies it to one widely used informal design component – UML{\textquoteright}s use cases.",

keywords = "UML Use Cases, HAZOPS, Threat Model",

author = "Thitima Srivratanakul and Clark, {John Andrew} and Fiona Polack",

year = "2004",

language = "English",

series = "York Computer Science Technical Report",

publisher = "Department of Computer Science, University of York",

number = "YCS-2004-375",

}

TY - BOOK

T1 - Writing Effective Security Abuse Cases

AU - Srivratanakul, Thitima

AU - Clark, John Andrew

AU - Polack, Fiona

PY - 2004

Y1 - 2004

N2 - We grow increasingly dependent on the appropriate operation of computer-based systems. One aspect of such systems is security. As systems become more complex current means of analysis will probably prove ineffective. In the safety domain a variety of analysis techniques has emerged over many years. These have proved surprisingly effective. Since the safety and security domains share many similarities, various authors have suggested that safety techniques might usefully find application in security. This report takes one such technique, HAZOPs, and applies it to one widely used informal design component – UML’s use cases.

AB - We grow increasingly dependent on the appropriate operation of computer-based systems. One aspect of such systems is security. As systems become more complex current means of analysis will probably prove ineffective. In the safety domain a variety of analysis techniques has emerged over many years. These have proved surprisingly effective. Since the safety and security domains share many similarities, various authors have suggested that safety techniques might usefully find application in security. This report takes one such technique, HAZOPs, and applies it to one widely used informal design component – UML’s use cases.

KW - UML Use Cases

KW - HAZOPS

KW - Threat Model

M3 - Other report

T3 - York Computer Science Technical Report

BT - Writing Effective Security Abuse Cases

PB - Department of Computer Science, University of York

ER -