{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T04:31:49Z","timestamp":1750221109213,"version":"3.41.0"},"reference-count":25,"publisher":"Association for Computing Machinery (ACM)","issue":"4","license":[{"start":{"date-parts":[[2018,12,28]],"date-time":"2018-12-28T00:00:00Z","timestamp":1545955200000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["SIGSOFT Softw. Eng. Notes"],"published-print":{"date-parts":[[2018,12,28]]},"abstract":"<jats:p>This workshop focused on bringing software developers and legal professionals together to understand the shared challenges they face in promoting the development of secure software on the one hand, and software at all, on the other hand. This report sum- marizes current scienti c research on the topics and challenges discussed in the workshop breakout sessions. The insights from the workshop highlight a number of interesting directions for fur- ther research on the interplay between software warranties and cybersecurity.<\/jats:p>","DOI":"10.1145\/3282517.3302398","type":"journal-article","created":{"date-parts":[[2019,1,4]],"date-time":"2019-01-04T13:33:51Z","timestamp":1546608831000},"page":"31-35","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":1,"title":["The Effect of Software Warranties on Cybersecurity"],"prefix":"10.1145","volume":"43","author":[{"given":"Dirk","family":"van der Linden","sequence":"first","affiliation":[{"name":"University of Bristol, Bristol, United Kingdom"}]},{"given":"Awais","family":"Rashid","sequence":"additional","affiliation":[{"name":"University of Bristol, Bristol, United Kingdom"}]}],"member":"320","published-online":{"date-parts":[[2019,1,2]]},"reference":[{"key":"e_1_2_1_1_1","doi-asserted-by":"publisher","DOI":"10.1109\/TSE.2007.70746"},{"key":"e_1_2_1_2_1","first-page":"913","article-title":"Products liability and the internet of (insecure) things: Should manufacturers be liable for damage caused by hacked devices","volume":"50","author":"Butler Alan","year":"2016","unstructured":"Alan Butler. Products liability and the internet of (insecure) things: Should manufacturers be liable for damage caused by hacked devices. U. Mich. JL Reform, 50:913, 2016.","journal-title":"U. Mich. JL Reform"},{"key":"e_1_2_1_3_1","volume-title":"Contracting insecurity: Software license terms that undermine cybersecurity","author":"Chandler Jennifer A","year":"2006","unstructured":"Jennifer A Chandler. Contracting insecurity: Software license terms that undermine cybersecurity. 2006."},{"key":"e_1_2_1_4_1","unstructured":"Federal Trade Commission. Protecting consumer privacy in an era of rapid change. recommendations for businesses and policymakers. https:\/\/www:ftc:gov\/reports\/protecting- consumer-privacy-era-rapid-change-recommendations- businesses-policymakers 2018. Online; accessed 28 February 2018."},{"key":"e_1_2_1_5_1","unstructured":"Writing Secure Software Consortium. Why johnny doesn't write secure software? secure software development by the masses. http:\/\/writingsecuresoftware:org\/ 2018. Online; accessed 28 February 2018."},{"issue":"8","key":"e_1_2_1_6_1","first-page":"517","article-title":"what civil liability in case of cyber-attacks?","volume":"17","author":"de Werra Jacques","year":"2017","unstructured":"Jacques de Werra and Evelyne Studer. Regulating cybersecurity: what civil liability in case of cyber-attacks? Expert Focus, 17(8):511{517, 2017.","journal-title":"Expert Focus"},{"key":"e_1_2_1_7_1","doi-asserted-by":"publisher","DOI":"10.1145\/2736281"},{"key":"e_1_2_1_8_1","volume-title":"Building a european data economy","author":"EU Commission","year":"2017","unstructured":"EU Commission. Building a european data economy, 2017. EU Commission Communication n. 50."},{"key":"e_1_2_1_10_1","doi-asserted-by":"publisher","DOI":"10.1109\/MSP.2010.85"},{"key":"e_1_2_1_11_1","first-page":"464","volume-title":"Proceedings of the 17th International Digital Government Research Conference on Digital Government Research","author":"Li Zhen","unstructured":"Zhen Li and Qi Liao. An economic alternative to improve cybersecurity of e-government and smart cities. In Proceedings of the 17th International Digital Government Research Conference on Digital Government Research, pages 455{464. ACM, 2016."},{"key":"e_1_2_1_12_1","doi-asserted-by":"publisher","DOI":"10.1109\/CSAC.2004.41"},{"key":"e_1_2_1_13_1","doi-asserted-by":"publisher","DOI":"10.1109\/TSE.2014.2383374"},{"key":"e_1_2_1_14_1","doi-asserted-by":"publisher","DOI":"10.1016\/j.ijcip.2010.10.002"},{"key":"e_1_2_1_15_1","volume-title":"Cyber essentials. https:\/\/www:cyberessentials:ncsc:gov:uk","author":"National Cyber Security Centre (NCSC).","year":"2018","unstructured":"National Cyber Security Centre (NCSC). Cyber essentials. https:\/\/www:cyberessentials:ncsc:gov:uk, 2018. Online; accessed 28 February 2018."},{"key":"e_1_2_1_16_1","volume-title":"Secure by default. https:\/\/www:ncsc:gov:uk\/articles\/secure-default","author":"National Cyber Security Centre (NCSC).","year":"2018","unstructured":"National Cyber Security Centre (NCSC). Secure by default. https:\/\/www:ncsc:gov:uk\/articles\/secure-default, 2018. Online; accessed 26 February 2018."},{"key":"e_1_2_1_17_1","first-page":"43","article-title":"Putting blame where blame is due: Software manufacturer and customer liability for security-related software failure","volume":"13","author":"Pinkney Kevin R","year":"2002","unstructured":"Kevin R Pinkney. Putting blame where blame is due: Software manufacturer and customer liability for security-related software failure. Alb. LJ Sci. & Tech., 13:43, 2002.","journal-title":"Alb. LJ Sci. & Tech."},{"key":"e_1_2_1_18_1","first-page":"1099","article-title":"It is just unfair using trade laws to out security software vulnerabilities","volume":"48","author":"Riedy Marian K","year":"2016","unstructured":"Marian K Riedy and Bartlomiej Hanus. It is just unfair using trade laws to out security software vulnerabilities. Loy. U. Chi. LJ, 48:1099, 2016.","journal-title":"Loy. U. Chi. LJ"},{"issue":"1","key":"e_1_2_1_19_1","first-page":"72","article-title":"Two views on security software liability. let the legal system decide","volume":"99","author":"Ryan Daniel J","year":"2003","unstructured":"Daniel J Ryan and C Heckman. Two views on security software liability. let the legal system decide. IEEE Security & Privacy, 99(1):70{72, 2003.","journal-title":"IEEE Security & Privacy"},{"key":"e_1_2_1_20_1","volume-title":"Heise Security","author":"Schneier Bruce","year":"2003","unstructured":"Bruce Schneier. Liability changes everything. Heise Security, November, 2003."},{"key":"e_1_2_1_21_1","first-page":"425","article-title":"Tort liability for vendors of insecure software: Has the time nally come","volume":"67","author":"Scott Michael D","year":"2007","unstructured":"Michael D Scott. Tort liability for vendors of insecure software: Has the time nally come. Md. L. Rev., 67:425, 2007.","journal-title":"Md. L. Rev."},{"issue":"5","key":"e_1_2_1_22_1","first-page":"9","article-title":"Abolish software warranty disclaimers","volume":"58","author":"Sta CACM","year":"2015","unstructured":"CACM Sta . Abolish software warranty disclaimers. Communications of the ACM, 58(5):8{9, 2015.","journal-title":"Communications of the ACM"},{"key":"e_1_2_1_23_1","doi-asserted-by":"publisher","DOI":"10.1109\/MSECP.2003.1203229"},{"key":"e_1_2_1_24_1","doi-asserted-by":"publisher","DOI":"10.1109\/MSECP.2004.1281252"},{"key":"e_1_2_1_25_1","first-page":"1","article-title":"The liability of software manufacturers for defective products","volume":"1","author":"LIIS","year":"2014","unstructured":"LIIS VIHUL. The liability of software manufacturers for defective products. The Tallin Papers, 1:1{14, 2014.","journal-title":"The Tallin Papers"},{"key":"e_1_2_1_26_1","first-page":"65","article-title":"Solving the information security & privacy crisis by expanding the scope of top management personal liability","volume":"43","author":"Wood Charles Cresson","year":"2016","unstructured":"Charles Cresson Wood. Solving the information security & privacy crisis by expanding the scope of top management personal liability. J. Legis., 43:65, 2016.","journal-title":"J. Legis."}],"container-title":["ACM SIGSOFT Software Engineering Notes"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3282517.3302398","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/3282517.3302398","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T01:01:56Z","timestamp":1750208516000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3282517.3302398"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2018,12,28]]},"references-count":25,"journal-issue":{"issue":"4","published-print":{"date-parts":[[2018,12,28]]}},"alternative-id":["10.1145\/3282517.3302398"],"URL":"https:\/\/doi.org\/10.1145\/3282517.3302398","relation":{},"ISSN":["0163-5948"],"issn-type":[{"type":"print","value":"0163-5948"}],"subject":[],"published":{"date-parts":[[2018,12,28]]},"assertion":[{"value":"2019-01-02","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}