Challenging software developers: dialectic as a foundation for security assurance techniques
release_lcujnyfisfgrzlngwtfxa7px5m
by
Charles Weir, Awais Rashid, James Noble
Abstract
<jats:title>Abstract</jats:title>
Development teams are increasingly expected to deliver secure code, but how can they best achieve this? Traditional security practice, which emphasizes 'telling developers what to do' using checklists, processes and errors to avoid, has proved difficult to introduce. From analysis of industry interviews with a dozen experts in app development security, we find that secure development requires 'dialectic': a challenging dialog between the developers and a range of counterparties, continued throughout the development cycle. Analysing a further survey of 16 industry developer security advocates, we identify the six assurance techniques that are most effective at achieving this dialectic in existing development teams, and conclude that the introduction of these techniques is best driven by the developers themselves. Concentrating on these six assurance techniques, and the dialectical interactions they involve, has the potential to increase the security of development activities and thus improve software security for everyone.
In application/xml+jats
format
Archived Files and Locations
application/pdf 1.2 MB
file_a2htmfumkvajzlhkdeu5jmzpki
|
watermark.silverchair.com (publisher) web.archive.org (webarchive) |
access all versions, variants, and formats of this works (eg, pre-prints)
Crossref Metadata (via API)
Worldcat
SHERPA/RoMEO (journal policies)
wikidata.org
CORE.ac.uk
Semantic Scholar
Google Scholar