Rights statement: ©2022 IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.
Accepted author manuscript, 1.92 MB, PDF document
Available under license: CC BY: Creative Commons Attribution 4.0 International License
Final published version
Research output: Contribution to Journal/Magazine › Journal article › peer-review
| <mark>Journal publication date</mark> | 31/01/2023 |
|---|---|
| <mark>Journal</mark> | IEEE Security and Privacy Magazine |
| Issue number | 1 |
| Volume | 21 |
| Number of pages | 10 |
| Pages (from-to) | 27-36 |
| Publication Status | Published |
| Early online date | 30/11/22 |
| <mark>Original language</mark> | English |
Teams developing software for health-related applications often have little professional security support. To work effectively with them, we should accept the complexity of their decision making, create stories as a basis for discussion, and use different jargon from cyberprofessionals.