title: Securing IDs on Ajax Driven Applications
body: <p>In building out applications that have majority of the UI events driven
  by Ajax calls we create a better UX but there is additional security risk 
  involved as there is more information exposed to the user browser then
  stored on the server. Specifically, identifying values. </p>
  
  <p>Aside from additional back end validation - I'm curious what other "best 
  practices" exist out there when passing IDs around on the client. I've
  seen things like hashing or encrypting the id before it goes out to the client but didn't know if any other options existed.</p>