You have a new SQL Server. What do you need to set up from a security perspective? What should be audited? What are the things you need to consider when building that initial security profile?
In this session we’ll look at the bare bones minimum things you need to secure and audit. Then we’ll look at the right questions to ask to determine where you go from there. Are there any regulations you’ll need to adhere to? Has your compliance officer specified other controls you must implement? What about, “Because it’s the right thing to do?” In response to these questions we’ll look at what some typical answers are with respect to security and auditing.
K. Brian Kelley is a Microsoft SQL Server author, columnist, and Microsoft Most Valuable Professional (MVP) focusing primarily on SQL Server and Windows security. In addition to being a database administrator, he has served as an infrastructure and security architect encompassing solutions with Citrix, virtualization, and Active Directory. Brian is also a Certified Information Systems Auditor (CISA) and has been the head of a financial organization’s computer incident response team. Brian is active in the IT community having spoken at DevConnections, SQL Saturdays, code camps, and user groups. He is also the President of the Midlands PASS Chapter and of a Professional Association for SQL Server Chapter in Columbia, SC.
Topics: Database Compliance, Database Security Products: SQL Compliance Manager