2006-07-05
1,048 reads
2006-07-05
1,048 reads
Security was a major focus of SQL Server 2005 during its development, both in terms of making the product secure as well as enhancing the options. Security expert Brian Kelley brings us a look at how the paradigm of logins has changed and what you need to look for in SQL Server 2005.
2008-04-11 (first published: 2006-07-05)
118,220 reads
2006-06-15
1,059 reads
2006-06-13
1,210 reads
2006-06-08
1,330 reads
2006-06-05
1,381 reads
2006-05-17
1,346 reads
If you're performing a penetration test or higher-level security audit of your SQL Server systems, there's one test you must not miss. It seems obvious, but many people overlook it: SQL Server password testing. Given the inherent weaknesses compared with more secure Windows authentication, you should especially test for password flaws if you're using SQL Server authentication in mixed mode. Password testing will help you determine how easily others can break into your database and help you ensure SQL Server users are being responsible with their accounts.
2006-05-16
4,339 reads
2006-05-08
1,271 reads
2006-05-01
1,167 reads
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
By Brian Kelley
On Patch Tuesday, in addition to OS and Office security patches, Microsoft also released...
When mirroring was first released for Azure SQL Database, it used Change Data Capture...
We have two "identical" instances of an ASP.NET web service (or so I have...
Comments posted to this topic are about the item OPENQUERY Flexibility
Comments posted to this topic are about the item A Full Shutdown
Which of these are valid OPENQUERY() uses?
See possible answers