ACM Home Page
Please provide us with feedback. Feedback
Applying an open application security process to a clinical information system: a case study
Full text PdfPdf (808 KB)
Source ACM International Conference Proceeding Series; Vol. 290 archive
Proceedings of the 2008 C3S2E conference table of contents
Montreal, Quebec, Canada
SESSION: Software engineering table of contents
Pages 89-98  
Year of Publication: 2008
ISBN:978-1-60558-101-9
Authors
Michael Pfähler  Ulm University of Applied Sciences, Ulm, Germany
Jens H. Weber-Jahnke  University of Victoria, Canada, B. C.
Sponsors
: ACM International Conference Proceedings Series
Concordia University : Concordia University
: BytePress
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 34,   Downloads (12 Months): 136,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1370256.1370269
What is a DOI?

ABSTRACT

Security is an important quality goal of software engineering. Incidents of data theft, data loss, and unavailability may lead to frustration of users, contravention of laws, or financial loss. Especially in critical domains like health care, every effort must be made to minimize security related problems. The optimum method for establishing software security is to consider it during all stages of the software process. For legacy systems, however, this is not possible. In order to provide a high level of confidence in the security of existing systems, a security analysis must be conducted. In this paper, we perform a security analysis of an existing clinical decision support system called EGADSS. The major motivation for conducting the security analysis is that the operational context of EGADSS is being changed from an intranet to the Internet. This means that in addition to general considerations associated with a security analysis, particular attention must be paid to the threats and risks introduced by the new environment of EGADSS. In order to conduct the analysis, we perform a process developed and published within the open content community, called CLASP (Comprehensive Lightweight Application Security Process). We report on our experiences with applying this community maintained process and reflect on its effectiveness in modeling threats to the system and identifying appropriate countermeasures.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Systems security engineering capability maturity model (SSE-CMM), 2006. Standard ISO/IEC 21827.
 
2
Build security in, 2007. https://buildsecurityin.us-cert.gov/
 
3
C. S. Reber. Certification Commission for Healthcare Information Technology (CCHIT) Approach to Assuring the Security of Electronic Health Record Systems. CCHIT.233 N. Michigan Avenue, Chicago, IL 60601
 
4
 
5
 
6
 
7
CLASP website: http://www.owasp.org/index.php/OWASP_CLASP_Project
8
 
9
 
10
A. Allas. Canada Health Infoway: EHRS Blueprint. Health Canada Infoway. 2006.
 
11
R. Dolin, L. Alschuler, C. Beebe, P. Biron, S. Boyer, D. Essin, E. Kimber, T. Lincoln, and J. Mattison. The HL 7 Clinical Document Architecture. Journal of the American Medical Informatics Association, 8(6):552, 2001.
 
12
M. Pfaehler. Performing a security analysis of a clinical decision support system for the migration from an intranet to the Internet. Bachelorarbeit an der Hochschule Ulm, Fakultät Informatik, Ulm, Germany, 2007
 
13
Bundesamt fuer Sicherheit in der Informationstechnik. Tomcat security assessment http://www.bsi.de/literat/studien/tomcat/index.htm
 
14
Bruce Schneier, "Attack Trees - Modeling security threats", Dr. Dobb's Journal, July 22, 2001
 
15
G. Sindre and A. L. Opdahl, Templates for Misuse Case Description, Proceedings of the 7 International Workshop on Requirements Engineering, Foundation for Software Quality (REFSQ'2001), Switzerland, June 4--5, 2001
 
16
T. Pryor and G. Hripcsak. The arden syntax for medical logic modules. Journal of Clinical Monitoring and Computing, 10(4):215--224, 1993.
 
17
 
18
RFC 4732, Internet Denial-of-Service Considerations, http://www.jetf.org/rfc/rfc4732.txt

Collaborative Colleagues:
Michael Pfähler: colleagues
Jens H. Weber-Jahnke: colleagues