June Webinar: SQL Server Security 201

Wednesday, June 22 (UPDATED)
2 p.m Eastern
Microsoft Teams

SQL Server Security …  basic 101 stuff?

Sure, you’ve mastered the foundational areas (i.e., logins, users, permissions, etc.), but there is much more to security than permissions to database objects. In this webinar, we will dig into some areas that are often overlooked, starting with the SQL Server services and best practices for the service accounts, including utilizing Group Managed Service Accounts (gMSA), permissions needed at the operating system level, and the overall surface area configuration of the services.

We will then go deeper into Service Principal Names (SPNs) and Kerberos and why these are important for DBAs to understand. If you’ve ever had to troubleshoot the dreaded and oh-so-helpful error message “Could not generate SSPI context,” or struggled to get Windows Authentication to work for a web application or linked server, we will answer those questions and more.

Go deeper into SQL Server Security with SSG Founder and Principal Consultant Randy Knight. Randy will discuss aspects of security that you may not have ever heard before. Join us in June and expand your knowledge!

Randy founded SQL Solutions Group in October 2010, after more than 20 years in the technology industry. Randy has a passion for solving what can seem to others to be insurmountable problems. His prowess with SQL Server earned him the label “database whisperer” from one satisfied customer.

He is a Microsoft Certified Solutions Master in SQL Server 2008. In 2020 he completed certification for Azure Fundamentals. In addition, he has numerous Novell, Microsoft, and Cisco legacy certifications. Prior to founding SSG, he spent many years as a Database Administrator in a variety of industries, including financial services, telecommunications, and with well-known dot com properties.

As a data professional, Randy says he has done lots of fun stuff, encountering most interesting data during his time as database architect for match.com (and no, he didn’t meet his wife while working there).