title: Direct Table Access Security with Entity Framework
body: <p>Greetings!</p>
  
  <p>I have recently built out a template for one of my clients that includes a lot of new features, not the least of which is EF/WCF RIA. </p>
  
  <p>Deployment time is greatly reduced when I can connect via EF directly to a table. No more CRUD SPROCs for all 50 tables. I've read that EF, by default, doesn't allow for standard SQL Injections, but I am wondering if anyone can provide me with a comprehensive security overview, or at least enough data where I can sit down with the senior DBA/Security guy here, and convince him that writing all of the CRUD SPROC's aren't necessary. </p>
  
  <p>I've read <a href="http://msdn.microsoft.com/en-us/library/cc716760.aspx" rel="nofollow">MSDN Security Considerations (Entity Framework)</a>, <a href="http://msdn.microsoft.com/en-us/library/ff626373%28v=vs.91%29.aspx" rel="nofollow">Security for WCF RIA Services</a>, and a slew of other articles, but I thought I'd give SO a try and ask for some real world implementations &amp; hard evidence in terms of security &amp; EF.</p>
  
  <p>Your thoughts are greatly apprecaited</p>
  
  <p>The senior DBA/Security guy here had a lot of questions about how </p>