Administering Microsoft SQL Server 2012 Databases Jumpstart-Mod 5 - Final
Administering Microsoft SQL Server 2012 Databases Jumpstart-Mod 5 - Final
05 | Security Implementation
George Squillace | Senior Technical Trainer – New Horizons
Great Lakes
Richard Currey | Senior Technical Trainer – New Horizons
United
Module 5 Overview
• Scope-specific
permissions exist
• Permission
statements
– GRANT
– REVOKE
– DENY
Authentication Modes
• Two modes
• SQL logins are protected
better by using password
policies
• Set during installation and
they can be changed later
• Switching requires a service
restart
• Functionally only a registry
key change
Login Objects
• Purpose
• Derived from
– Windows
• Domain
• Machine local
– SQL logins
• Administration tools
– SSMS
– CREATE / ALTER / DROP LOGIN
– Options
Server Roles and Server-level Permissions
• Database users
– Derived from logins
• Types of database-level roles
– Fixed
– User defined
• Application roles
• Database-scoped permissions
Database-level Roles
• Applicable principals
– Windows user
– Windows group
– SQL login
DEMO
Creating Users for a Specific Database
(Contained Database)
Topic: Implementing
Permissions
Topic: Implementing Permissions
• Object Permissions
• Code and Module Permissions
• Applying Permissions
• Permission Management Strategies
• SSMS
– Begin with a principal
– Begin with a securable
• T-SQL statements
– GRANT
– REVOKE
– DENY
• Security model anomaly (prior to SQL Server 2012)
– Column-level GRANT override Table-level DENY
Permission Management Strategies
• Various strategies
– Aim for “double
abstraction”
• Leverage roles
– Roles can be nested
• Leverage schemas
DEMO
Implementing a Permission Strategy by
Assigning a Role Permission to a Schema
©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered trademarks and/or trademarks in the
U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft
must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after
the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.