veyepar: The delightful user experience of security

Author(s):	Casey Schaufler
Location	C3
Date	jan Tue 22	Days Raw Files
Start	13:30	First Raw Start	13:02
Duration	0:50:0	Offset	0:27:46
End	14:20	Last Raw End	14:32
Chapters	00:00 0:00:38 0:00:42 0:30:37 0:33:06
Total cuts_time	41 min.

https://2019.linux.conf.au/schedule/presentation/245/
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf The_delightful_user_experience_of_security.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

The delightful user experience of security – We all know that computer security is obtrusive, annoying and expensive. At every layer of software from wifi modem micro-code to web backgammon there are passwords, updates and restrictions that get in the way of doing the simple things we set out to accomplish. If you’re a developer, it’s even worse with CVE tracking, code scanners and named exploits sucking away precious schedule time. But what if it wasn’t that way? What would software be like if someone developed computer security with the explicit goal of creating something people will like? Casey Schaufler knows how dreadful the experience of security can be, having implemented everything from access control lists and release process to the ugliest login screen ever produced. In this talk he steps back from the traditional approach to computer security and investigates it from the viewpoint of providing a delightful user experience. The talk starts off with the basic premises of security and why they ought to make systems more usable, not less. It continues with the importance of creating security models that reflect what people want the software to do, and how to go about doing so. The process of building software to enforce those models and the mechanism for ensuring that both security and user experience are maintained throughout are described. Finally, the problem of keeping the user experience from deteriorating when faced with new and unexpected security challenges is addressed.

Comment:

production notes