Corba: Crowdsourcing to Obtain Requirements from Regulations and Breaches
Context: Modern software systems are deployed in sociotechnical settings, combining social entities (humans and organizations) with technical entities (software and devices). In such settings, on top of technical controls that implement security features of software, regulations specify how users should behave in security-critical situations. No matter how carefully the software is designed and how well regulations are enforced, such systems are subject to breaches due to social (user misuse) and technical (vulnerabilities in software) factors. Breach reports, often legally mandated, describe what went wrong during a breach and how the breach was remedied. However, breach reports are not formally investigated in current practice, leading to valuable lessons being lost regarding past failures.
Objective: Our research aim is to aid security analysts and software developers in obtaining a set of legal, security, and privacy requirements, by developing a crowdsourcing methodology to extract knowledge from regulations and breach reports.
Method: We present Corba, a methodology that leverages human intelligence via crowdsourcing, and extracts requirements from textual artifacts in the form of regulatory norms. We evaluate Corba on the US healthcare regulations from the Health Insurance Portability and Accountability Act (HIPAA) and breach reports published by the US Department of Health and Human Services (HHS). Following this methodology, we have conducted a pilot and a final study on the Amazon Mechanical Turk crowdsourcing platform.
Results: Corba yields high quality responses from crowd workers, which we analyze to identify requirements for the purpose of complementing HIPAA regulations. We publish a curated dataset of the worker responses and identified requirements.
Conclusions: The results show that the instructions and question formats presented to the crowd workers significantly affect the response quality regarding the identification of requirements. We have observed significant improvement from the pilot to the final study by revising the instructions and question formats. Other factors, such as worker types, breach types, or length of reports, do not have notable effect on the workers’ performance. Moreover, we discuss other potential improvements such as breach report restructuring and text highlighting with automated methods.
Fri 10 Jul Times are displayed in time zone: (UTC) Coordinated Universal Time change
|16:05 - 16:17|
|16:17 - 16:25|
David AmellerUniversitat Politècnica de Catalunya, Xavier FranchUniversitat Politècnica de Catalunya, Cristina GómezUniversitat Politècnica de Catalunya, Silverio Martínez-FernándezUPC-BarcelonaTech, João AraújoUniversidade Nova de Lisboa, Stefan BifflVienna University of Technology, Jordi CabotICREA - UOC, Vittorio CortellesaUniversity of L’Aquila, Daniel MendezTechnische Universität München, Ana MoreiraFCT / Universidade Nova de Lisboa, Henry MucciniUniversity of L'Aquila, Italy, Antonio VallecilloUniversity of Málaga, Spain, Manuel WimmerJohannes Kepler University Linz, Vasco AmaralUniversidade Nova de Lisboa, Wolfang BöhmTechnische Universität München, Hugo BrunelièreInria, Mines Nantes & LINA, Loli BurgueñoUniversidad de Malaga, Miguel GoulaoNOVA-LINCS, FCT/UNL, Sabine TeuflFortiss GmbH, Luca BerardinelliJohannes Kepler University Linz
|16:25 - 16:33|
|16:33 - 16:41|
Stefan WagnerUniversity of StuttgartLink to publication DOI Pre-print
|16:41 - 16:49|
|16:49 - 16:55|
Steffen HerboldUniversity of GöttingenPre-print