Author(s):	Tom Eastman
Location	D4.303 Costa Theatre
Date	feb Thu 04	Days Raw Files
Start	16:35	First Raw Start	16:34
Duration	0:45:00	Offset	0:00:02
End	17:20	Last Raw End	17:19
Chapters	00:00
Total cuts_time	37 min.

https://linux.conf.au/schedule/30232/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

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

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
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:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	The unfortunate truth about networked applications is that an attacker only needs to know one thing you didn't know to get past your defenses. You need to know everything, they don't. The odds aren't in your favour. You're eventually going to get hacked. That's the bad news. But if you stop thinking about a security compromise as that thing you close your eyes and hope never happens", and instead start thinking about it as an inevitability, then you can start making better security decisions. "If they compromise my web servers, how do I protect my application servers?" "If they break my application server code, how can I prevent them from gaining a foothold on my infrastructure?" "If they poison my web-site with cross-site scripting, how do I find out before my users get hurt?" In short: "If I’m going to get hacked, how do I make it hurt less?" This is a talk about defense in depth. Building a secure system isn’t about luck, it’s about planning. markdown
Comment:	production notes