2005-02-25
1,127 reads
2005-02-25
1,127 reads
2005-02-01
1,256 reads
In this installment of our series covering new and improved functionality of SQL Server 2005 Beta 2, we will focus on the topic of security, which has been becoming increasingly prominent among the issues on every database and system administrator's agenda. A new approach to software development started with the Trustworthy Computing initiative launched in early 2002, necessitated by the growing number of exploits directed at the Microsoft operating system and applications, resulted in a "secure by default" product with highly customizable security features further increasing the degree of protection. We will start with the features related to authentication (the process of identifying logins connecting to the SQL Server and users accessing databases), and continue with authorization (determining the level of permissions granted once the initial connection is established) and encryption in the future articles. In particular, we will cover here, password policy implementation and management as
2005-02-01
5,709 reads
Databases are being stolen. Customer data, credit card data, taxpayer data - they're all vulnerable. Scary? Yes - but wait, there's more. It's not just "their" data that's vulnerable - it's ours too!
2005-01-21
2,107 reads
The SQL Server 2000 security model is not the best one of all the RDBMS platforms and requires some work to secure properly. One of the practices that is recommended is removing the builtin/administrators group from accessing the SQL Server. New author Kathi Kellenberger shows us some of the pitfalls she encountered when removing this group from her servers.
2007-08-10 (first published: 2005-01-12)
30,126 reads
If you are running Microsoft SQL Server databases to support critical enterprise applications, you are part of a growing trend.
2005-01-06
1,972 reads
Focuses on advanced techniques that can be used in an attack on an application utilizing Microsoft SQL Server as a backend. These techniques demonstrate how an attacker could use a SQL Injection vulnerability to retrieve the database content from behind a firewall and penetrate the internal network. Also provided are recommendations on how to prevent such attacks.
2005-01-05
2,626 reads
2005-01-03
301 reads
2004-12-21
1,639 reads
The key to effective security is embracing it as an ongoing process rather than a one time event. This document examines how database security can be enhanced with a proactive security lifecycle approach.
2004-12-13
1,564 reads
By Vinay Thakur
This blog series on Audit/Compliance/Security, this is first blog where we would discuss about...
In the previous post, we've built a SQL Server 2025 sandbox in an OrbStack...
By Steve Jones
Thanks to everyone for attending my talk today at Day of data Baton Rouge...
Via, WhatsApp+62 821-8200-174 Jl. Jenderal Sudirman No.21, RT.10/RW.1, Kuningan, Karet Kuningan, Kecamatan Setiabudi, Kota...
Via WhatsApp+62 821-8200-174 Cyber 2, Gedung Menara Karya, Jl. H. R. Rasuna Said Jl....
Via WhatsApp+62 821-8200-174 Gedung C3 Lt. 1-3 Komplek, Jl. Puri Indah Raya No.1-3 Blk...
Which of these is not true for certificates used for SQL Server connections?
See possible answers