title: Restricting a public-facing demo site for an asp.net application?
body: <p>I'm convinced there has to be a dupe of this somewhere, but I couldn't find it easily:</p>
  
  <p><strong>Given an asp.net application that in itself uses Forms Authentication, what is the best practice for securing a public-facing demo site such that nobody who is not in the "in crowd" can see the site at all?</strong></p>
  
  <ul>
  <li>IP Filtering?</li>
  <li>Basic auth wrapped around the forms auth? I've banged my head on this one and can't seem to make it work :/</li>
  <li>VPN?</li>
  <li>"making a demo site public facing considered harmful" in the first place?</li>
  </ul>