Database security

You may need to do a quick third-party registration to access certain ones.

  • Ten hacker tricks to exploit SQL Server systems
  • Do you need to harden SQL Server 2008 R2? (formerly published at
  • Meet compliance requirements with improved database security practices (formerly published at
  • Common oversights with SQL Server audits (formerly published at
  • The ultimate SQL Server security faux pas: Overlooked systems (formerly published at
  • Password cracking tools for SQL Server (formerly published at
  • The true value of transparent data encryption (formerly published at
  • The fine line between not encrypting your databases and breach notification (formerly published at
  • New security features in SQL Server 2008 leave some work for you (formerly published at
  • How insiders hack SQL databases with free tools and a little luck (formerly published at
  • Integrating source code analysis into your database security measures (formerly published at
  • SQL Server 2008 security and compliance features reduce security risks (formerly published at
  • Get your SQL Server security goals in order (formerly published at
  • How secure is your SQL Server network design? (formerly published at
  • Basic SQL Server security principles you can’t afford to miss (formerly published at
  • Why store sensitive data if you don’t have to? (formerly published at
  • Database security testing terms: Setting the record straight (formerly published at
  • SQL Server patching pros and cons (formerly published at
  • Six risky assumptions about SQL Server passwords (formerly published at
  • Database threats include unruly insiders (formerly published at
  • Protecting your database: Who’s looking at your sensitive data? (formerly published at
  • Software security tools to improve your skills in a single day (formerly published at
  • Enhance your SQL Server security skills with five quick steps (formerly published at
  • Database-related security policies to think about (formerly published at
  • Meet compliance with improved database security practices (formerly published at
  • Logging for security compliance in SQL Server (formerly published at
  • Step-by-Step Guide: Test for a Trojan horse on your SQL Server (formerly published at
  • Database security options to protect data in SQL Server (formerly published at
  • Harden code to prevent SQL injection (formerly published at
  • Ten IIS tips to lock down SQL Server (formerly published at
  • Encryption enhancements in SQL Server 2005 (formerly published at
  • Tool to configure and lock down SQL Server 2005 services (formerly published at
  • Automate SQL injection testing (formerly published at
  • Checklist: How to test SQL Server security (formerly published at
  • Not upgrading? Keep SQL Server 2000 Secure (formerly published at
  • SQL Server’s emerging rootkit threat (formerly published at

Client Testimonials

“A business associate referred our company to Principle Logic when we were seeking a resource to perform vulnerability /penetration testing for our external and internal networks. We found Kevin Beaver to be professional, well informed, and easy to work with. His testing did not disrupt our networks, and his progress updates were timely.

His final report was very thorough and included security recommendations for our network environment. The executive leadership was so impressed with Kevin’s security expertise, they have extended their agreement to continue to perform periodic testing. We highly recommend Kevin Beaver and Principle Logic as a resource for network security testing.”

(IT managed services firm)


I’ve written/co-written 12 books on information security including: