Security

Technical Article

Common Vulnerabilities in Database Security

  • Article

Creating an enterprise security plan is a complex endeavour. It involves evaluating multiple threats that gain access through many network paths to a hodgepodge of different applications and systems. With the focus on systems and paths, databases are frequently overlooked. Securing the database should be a fundamental tenet for any security practitioner when developing his or her security plan. The database is the source of data, the "crown jewels" in the information economy. Any security effort must start with this in mind and end with the strongest level of controls applied at the database layer.

2004-11-26

2,129 reads

External Article

SQL Server 2000 Security - Part 13 - SQL Injection attack

  • Article

Typically, access to data is provided via client applications, which increases the range of potential vulnerabilities and places an equal share of responsibility for data security on software developers. This is especially important since application flaws can have just as catastrophic implications as a misconfigured or unsecured SQL Server installation.

2004-10-19

2,337 reads

SQLServerCentral Article

SQL Server Auditing - Part 1

  • Article

Our SQL Server Security expert, Brian Kelley, brings us the first part of a new series on auditing. Most of the auditing articles we've had are based on how you audit changes to data. Brian looks at auditing from the server itself, explaining the different levels of auditing built into SQL Server 2000.

5 (3)

You rated this post out of 5. Change rating

2007-10-02 (first published: )

39,400 reads

SQLServerCentral Article

Review: NGSSquirrel

  • Article

NGS Software is in the security business and have been very successful in finding vulnerabilities in many products, notable SQL Server. They have used their expertise to build products to help you better secure your systems. Dale Corey looks at one of those products, NGSSquirrel, which does vulnerability assessment.

5 (1)

You rated this post out of 5. Change rating

2004-07-30

10,558 reads

SQLServerCentral Article

Save Your Password

  • Article

Storing passwords in SQL Server for authentication by your application is a common practice. But not always a good one. Someone with access could easily see all passwords and perhaps cause mischief inside your application. Imagine the office gossip getting access to your HR application as the HR director! Not a good thing. Dinesh Asanka has written a short piece on how you can use a built in function in SQL Server to encrypt these passwords and use them with a minimum of effort.

You rated this post out of 5. Change rating

2004-07-12

13,379 reads

Blogs

Redgate Summit Comes to the Windy City

By

I love Chicago. I went to visit three times in 2023: a Redgate event,...

Non-Functional Requirements

By

I have found that non-functional requirements (NFRs) can be hard to define for a...

Techorama 2024 – Slides

By

You can find the slidedeck for my Techorama session “Microsoft Fabric for Dummies” on...

Read the latest Blogs

Forums

Table partitioning best practice

By JasonO

I've inherited a couple of rather large databases from my ex-colleague when I join...

Identifying Customer Buying Pattern in Power BI - Part 2

By Farooq Aziz

Comments posted to this topic are about the item Identifying Customer Buying Pattern in...

Finding Marks

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Finding Marks

Visit the forum

Question of the Day

Finding Marks

I have marked a few transactions in my code. How can I find out which marks were stored in a transaction log?

See possible answers