SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 224 of 365 Next >

Computer security has become a hot topic these days. It's in many technical and business journals, on the news, and the major newspapers. In fact, I just watched a two-hour program regarding identity theft on PBS; in that program, the speaker went into some detail on computer security. Its lapse has been highlighted in articles and reports on terrorism, which uses stolen identities and other data for illegal activities.

Database security is part of the package, but complete security isn't just about strong passwords or knowing who your users are. Those are certainly good elements to include in your security plan, but even before you consider them, you should evaluate what access each account needs. In addition, it's best to make a complete security review of all of your platforms, including SQL Server. It seems that lots of documentation is necessary for an adequate security plan.

So why don't we do that? I mean we, as in the Technical Professionals charged with protecting such things? There are two answers that I get most often when I ask about documenting security information.

The first answer I hear is, "I just don't have that much time. I know it's important, but I have so many other things to work on, security doesn't get the attention it deserves." The second answer I get goes something like this: "I can't possibly keep track of all the objects, users, groups, and security requirements. It changes way too often, and I don't know what the requirements are, anyway."

Well, I've got good news for you. Using SQL Server DMO programming, you can create security documentation quickly and easily. You can create a full matrix on the current security, and by monitoring the output, you can track when changes occur.

I've covered SQL Server security in depth before, but let's take a quick look at the basics once again, so that we have a reference for this article.

SQL Server security has two areas. The first area involves access, and the second involve rights. Let's take a look at the access part first.

The best way I've found to describe SQL Server security is like a building. To get into most modern office buildings, you need a card with a code for building access, and another code on the card to access a particular room.

Using this analogy, SQL Server is like the building, and a Server Login is the code for the front door. Each database is like the rooms in the building, and the databases require a Database Logon. So the login gets you in the front door (SQL Server) but not into a room, and the logon gets you into the room (a particular database).

SQL Server security can tie in to a Windows account, or you can create an account for SQL Server that doesn't use an operating system account at all. That's a bit different from operating system security, which deals with a single account all the time.

Either way, these accounts allow access to two things: the server and its database objects. As I've covered in other articles, each database then contains other objects, such as tables, views, and stored procedures.

These objects have two kinds of security: object and statement permissions. The object permissions allow access to an object, and statement permissions allow the account to create or alter an object. Let's focus on the statement permissions here.

Statement permissions allow a user account to perform such actions as SELECT, INSERT, and DELETE (The UPDATE command is actually an implied DELETE and then INSERT). For stored procedures, they include EXECUTE permissions. These permissions exist separately on each object, unless the parent object (such as a stored procedure) was created by the same user as the underlying object (such as the table the stored procedure uses). In that case, the administrator only has to grant the EXECUTE permission on the stored procedure, greatly simplifying what you have to track.

It's best to have a listing of the security for each user, per object, per statement. That's a lot of tracking! You can use SQL Server DMO programming to make that effort a lot easier.

The following code travels down a particular database for all non-system groups, and shows all the object permissions for each of those groups.

' Get and set a SQL DMO server object, and connect
' to the local server instance
Set oServer = CreateObject("SQLDMO.SQLServer")
oServer.LoginSecure = True
oServer.Connect "(local)"

' Get and set a database object
Set oDatabase = oServer.Databases("pubs")

' Get and set a database role object
Set oDatabaseRole = oDatabase.DatabaseRoles

' Here is the outer loop for the roles
For Each oDatabaseRole in oDatabase.DatabaseRoles 
	' Exclude the system roles
	If oDatabaseRole.IsFixedRole = False Then
		' Get and set a permissions object
		Set oRolePermission = oDatabaserole.ListObjectPermissions(SQLDMOPriv_AllObjectPrivs)
		' Inner loop for the permission, by object and group
		For Each oRolePermission in oDatabaserole.ListObjectPermissions(SQLDMOPriv_AllObjectPrivs) 
			strMsgText = strMsgText & oRolePermission.PrivilegeTypeName + ", " + oRolePermission.ObjectOwner + "." + oRolePermission.ObjectName + ", " + oRolePermission.Grantee & vbcrlf
		Next 
	End If

Next	

' Display. You could also send this to a file
MsgBox strMsgText,,"Permission, Object, Group" 

'Clean up
Set oRolePermission = Nothing
Set oDatabase = Nothing
Set oServer = Nothing

Let's deconstruct this code a bit. In the first section, I connect to the server and the database in which I'm interested. You can use a collection to iterate through all your servers and/or databases to make this part of the code more extensible.

In the lines:

' Get and set a database role object
Set oDatabaseRole = oDatabase.DatabaseRoles

I'm using a new property on the Database collection, called DatabaseRoles. This property provides access to the roles defined in the database.

This code uses two loops: one for the roles in the database, and the other for the permissions the role owns. Notice that the permission is iterated through the role – not through the object. That's an important distinction.

Within the outer loop I've used an If statement to exclude the system roles – which should never change anyway.

The next few lines show the full complexity of displaying security. You can see that I've set a line to fill the oRolePermission object with the list of object permissions:

Set oRolePermission = oDatabaserole.ListObjectPermissions(SQLDMOPriv_AllObjectPrivs)

Now that these objects are available, the inner loop uses them to access properties like oRolePermission.PrivilegeTypeName.

I captured the information from these roles into a text variable and then displayed that in a message box, but you can also send the results to a file to create a matrix. You can then parse that file to create a history of security changes.

In this article, I've only shown the documentation of the security on a few objects. You can use these same techniques on all of the SQL Server objects that have security, and you can also use them to change that security. You can add users and groups using DMO programming. For more information on these processes, check out the references at the end of this article.

In the next tutorial, I'll finish up this section on DMO with a discussion on another useful function: scripting.

Online Resources

The full documentation for the SQL Server Object Library can be found here.

You can read more on SQL Server Security from Microsoft here. This site has a lot of good resources and a few good downloads.

InformIT Tutorials and Sample Chapters

If you're looking for a preview of how security will change in SQL 2005, check out this article.

Service Packs are the main source of security updates for SQL Server. Roberta Bragg covers more in this free sample chapter from her book on becoming an MCSE.

< Back Page 224 of 365 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address