Implementing Separation of Duties (SoD) in SQL Server Vijay Natarajan | Senior Product Planner, SQL Server

Meet Vijay Natarajan Senior Product Planner for SQL Server Over 10 years of experience at Microsoft Own product/business strategy & roadmap investments for SQL Server across on-premises and cloud Previously owned product planning for SharePoint enterprise platform and various engineering roles at Microsoft

Course Topics Implementing SoD in SQL Server 01 | Business Need 02 | Principles & Concepts 03 | Implementing SoD in SQL Server 04 | Summary

Business Need No one user or role should have complete control over a business process or software Minimize the possibility of error and fraud Laws & Regulations specific to industry

Enumerating and classifying duties by role Duty Limited To Role Installs SQL Server, Service Packs Upgrades to newer versions Software Installer Adds new logins/users Instance Identity Manager Assign permissions to logins Instance Security Admin Controls, Troubleshoot & Respond to outages Maintains Master/MSDB/utility databases Backs up and restores databases Checks data consistency Highest DBA Installs new applications and upgrades existing ones Application Installer (could be DBA or App DBA) Adds new users/login to an application database with different permission levels Database Identity Manager Owns databases and schemas within databases Application Developer Ensures user data is not compromised Ensures compliance with regulations Auditor Insert/Extract data from instances Linked servers to access external data BULK INSERT DBA/App DBA/ App developer