Merge pull request #240 from drozer/master

new talks by Frank Breeijk and Wes Mason

site/content/events/2013-amsterdam/proposals/FrankBreedijk_HelpmySecurityOfficerdoesnttrustme/index.txt

@@ -0,0 +1,37 @@
+---
+extension: html
+filter:
+- erb
+- markdown
+dirty: true
+proposal: true
+talk: true
+selected: false
+layout: event
+author: Frank Breedijk
+title: "Help, my Security Officer doesn’t trust me"
+---
+
+**Abstract:**
+
+In many companies, devops and security officers don’t make for a happy couple. The first impulse for a security officer is to think ‘devops is along memory lane back to the eighties, when engineers changed directly in PROD and no OTAP streets ….’.Too bad that they are not happy couple because they are far less incompatible than it seems at a first glance. In this presentation by Frank, a hardcore security officer himself, he will explain how his colleagues seduced him to become a devops-supporter. Moreover, how he became to appreciate the possibility of ten releases a day. Perhaps, he will even explain why and how Security might benefit from devops.
+
+**Speaker:**
+
+Frank Breedijk
+
+Frank Breedijk CISSP B ICT is employed as a Security Engineer at Schuberg
+Philis since 2006. He is responsible for the technical information security of
+Schuberg Philis Mission Critical outsourcing services. This includes, but is
+not limited to Security Awareness, Vulnerability management, Internal security consultancy, Internal technical audits, AutoNessus development.
+
+Frank Breedijk has been active in IT Security for over 10 years. Before
+joining Schuberg Philis he worked as a Security Consultant for INS/BT and
+Security Officer for Interxion. He managed the European Security Operations
+Center (SOC) for Unisys' managed security services. During this period Gartner
+labeled Unisys leader in the magic quadrant for Managed Security Services in
+Europe.
+
+Besides his day job Frank Breedijk is an active on Twitter and writes blog
+entries for CupFighter.net. He has also written magazine articles about
+Seccubus and security awareness.

site/content/events/2013-amsterdam/proposals/WesMason_HowwebuiltanddeployedtheHonshuway/index.txt

@@ -0,0 +1,26 @@
+---
+extension: html
+filter:
+- erb
+- markdown
+dirty: true
+proposal: true
+talk: true
+selected: false
+layout: event
+author: Wes Mason
+title: "Island Life: How we built and deployed the Honshū way"
+---
+
+**Abstract:**
+
+Honshū, or Honshuu, is the largest island of Japan.
+It is also the codename for the complete rewrite of Server Density that has been over a year in the making, embracing a service orientated architecture similar to those popularised by Amazon and Netflix.
+At the heart of Honshuu is the idea that every service is an island. Any island can talk to another, using strict traditions and customs, and almost any island can communicate freely with the wider world via intermediaries and guardians of custom.
+
+Each island *is* the main land, looking after it's own concerns, only caring that other islands *can* communicate with it, but not what goes on outside.
+This is a *cultural shift* away from other ways of working more than technological. Knowing when to spin out a new "island" and making sure it can be communicated with in the same fashion as it's neighbours, from common build strategies regardless of base technology, to involving ops as a guiding principle from the very first steps as to how an island should be built.
+
+**Speaker:**
+
+Wes Mason

site/content/events/2013-amsterdam/proposals/WesMason_TwoPointOhMyReleaseengineeringforeveryone/index.txt

@@ -0,0 +1,29 @@
+---
+extension: html
+filter:
+- erb
+- markdown
+dirty: true
+proposal: true
+talk: true
+selected: false
+layout: event
+author: Wes Mason
+title: "Two Point Oh My! Release engineering for everyone"
+---
+
+**Abstract:**
+
+With continuous integration, continuous deployment and packaging systems that just install all the latest shiny for us, we don't need to worry about releases any more..do we?
+
+Release engineering is an important aspect of any projects development and deployment cycle. From testing to building, packaging and releasing,  a version number is not just an arbitrary string and relying on one person to understand how your product makes it to customers is a recipe for disaster.
+
+Walk this way and we'll explore methodologies and tooling for managing releases and solutions to common problems such as:
+
+ * Documenting builds and release processes for both devs and ops. 
+ * Understanding when to automate..and when not.
+ * Dependency tracking and avoiding stale dependencies or security issues without breaking builds. 
+
+**Speaker:**
+
+Wes Mason