2005-05-19
1,084 reads
2005-05-19
1,084 reads
2005-05-06
1,057 reads
As every developer knows by now, Microsoft has focused renewed attention on security in recent product releases. One of the important concepts in this effort is surface area. Roughly speaking, a piece of software has a smaller surface area if there are fewer ways to attack it: fewer open ports, fewer APIs, fewer protocols, and so on. OSQL Server 2005 takes this concept to the next level by letting you explicitly manage the software's surface area.
2005-04-21
3,226 reads
2005-04-18
1,269 reads
In this article, we will conclude our coverage of security related changes in SQL Server 2005 Beta 2 (although we will continue discussion of improvements in other functionality areas throughout the reminder of this series). The topics we will focus on here are code and module signing, modifications of SQL Server Agent and SQL Profiler operations, as well as monitoring and auditing changes.
2005-03-23
2,123 reads
2005-03-22
1,468 reads
We have described, so far, authorization based on a predefined fixed server (determining a set of SQL server-wide privileges) and database (applying to database objects and activities) roles. We have also discussed application roles, which makes the level of permissions independent of those assigned to a SQL Server login or a database user account. Now it is time to look into permissions from the point of view of database objects. There are two main factors that play a role in determining how access rights to them are evaluated - their ownership and custom permissions. We will discuss the first one of these topics in this article and will continue with the other one in the next installment of this series.
2005-03-22
2,349 reads
SQL Server does many things very well, but securing itself is not one of them. While securing your server requires some effort, there is an area that many people forget. Securing your backups! Brian Kelley, our resident security expert, brings some advice and ideas for ensuring your data will not be stolen.
2005-03-21
9,065 reads
2005-03-09
1,257 reads
After discussing authentication and authorization behavior of SQL Server 2005 Beta 2 in the previous two articles of this series, it is time to look into other security-related changes. In particular, we will focus on the freshly introduced native database encryption capabilities. While some encryption functionality existed in the previous versions (e.g. involving column encryption APIs within User Defined Functions or PWDENCRYPT password one-way hash function), it was relatively limited and rarely used. SQL Server 2005 provides significant improvements in this area.
2005-03-09
3,566 reads
By Steve Jones
After my session at VSLive last week, I had a few questions from the...
Referrals have never been more important in the job market. They’re no longer nice...
By Steve Jones
dorgone– adj. wondering if you could slip away from an event or group conversation...
I have about 100 Tables that are all suffixed with _Modify. These tables record...
Comments posted to this topic are about the item Make It Routine
Comments posted to this topic are about the item Finding Gaps in Sequential Data...
If I want to know whether a number of negative, positive, or zero, what is the easiest way to get this in T-SQL?
See possible answers