Voice of the DBA

Tag: security

  • In Case of Breach


    What would you do if you received a phone call in the middle of the night saying that one of your databases had been hacked and data released? Do you know what to do as a first responder? There’s a report from Dark Reading that talks about some of the things you might want to consider.

    Crisis situations, and this is definitely one, require some planning and thought ahead of time. You ought to have some sort of “run book” similar to the one you have for disaster recovery, that helps you decide how to handle the situation. Unlike many troubleshooting situations, rebooting a server might be the worst thing you can do.

    I used to think that database people were more insulated from responding to these types of crisis situations. It seemed early in my career that we would be backups for the system administrators, and not necessarily need to respond to a midnight call. However the last 5 years have shown that this type of call is more and more likely for all data professionals.

    As we store more and more data, of great importance to the organization, we should be more prepared to respond to these types of incidents. Financial, identity, medical, and other types of data are becoming mixed in with all sorts of business data. As we build warehouses and transfer data among more systems, the likelihood we have data needing strong protections increases.

    At the very least, we must educate ourselves on our legal responsibilities as the data profession moves forward. More and more laws are being passed and regulations applied to data, and a good data professional in the future needs to be aware of their responsibilities in this area.

    Steve Jones

  • Getting a Dedicated Admin Connection

    Did you know you can easily get a Dedicated Admin Connection (DAC) in SSMS? I didn’t assuming that I’d need to use a command line and SQLCMD. However while studying for the MCM, I learned that there’s an easy way.

    I tested this on a SQL Server 2008 instance, having a normal connection, as seen in the lower status bar:

    admin_connection2

    Right click in the query window, and select “Change Connection”. In the dialog, not add “Admin:” before the server name, as shown below.

    admin_connection

    When you connect, you’ll have an admin connection, which you can see in the status bar.

    admin_connection1 

    Pretty cool.

  • Elections

    In the last few elections in the US, there has been concern over the validity of votes. As more and more electronic machines are being used to record votes, and often being built with very little security, how can we be sure that the data is being collected, tabulated, and securely stored for our elections? It’s an issue that most countries face, and will continue to face as they deal with larger and larger elections.

    Developing a secure way to collect, store, and verify data is hard. We struggle with that on a regular basis, and I think we often tend to ping across both ends of the spectrum on how to handle this. We tightly control all access and storage of data,  keeping access as limited as possible, and we still have regular problems with data loss and breaches. Or we may open up our systems to large groups of users, essentially ignoring security. Is there any hope for voting data?

    I came across this idea from David Bismark that explains a fairly simple, and reliable method of both allowing access to data, while also keeping the secrecy necessary for each person’s vote.  It’s in a TED Talk that discusses the idea in a few minutes, and it’s rather amazing.

    I don’t know if there’s something we can learn here to apply to other data issues, but I would guess that any area that needs to distribute data while protecting privacy could use something similar.

    Steve Jones

  • Security by Obscurity

    This is an editorial reprint from Aug 23, 2005

    I wrote awhile back about security through chaos, and that piece provoked some interesting responses. While I’m not sure I’d recommend it for every company, in some places it makes sense. I saw this Info World article on Security by Obscurity and it reminded me of what I’d written.

    The article talks about some basic things you can do to that don’t seem like much, but the suggestions obscure things and ensure that not much on your system is as it would be expected. One simple thing they talk about is not installing to the default locations. That doesn’t sound like it would help much as there are always ways to read the registry or use environmental variables to find installations.

    However it does work. How many pieces of software, including some SQL Server Service Packs, expect things to be installed on c:? How often have you been bitten by a “bug” in some software because you’d renamed or moved something?

    Computer software depends on patterns in many cases to work. And we all use patterns to shorten development time. We reuse code, we cut and past way too much, and we often forget to make simple checks for things being moved around.

    The same goes for virus and worm writers. The people who develop the technology might not be fooled, but so many script kiddies that use kits of modify some piece of code aren’t as savvy and don’t necessarily make these checks. I know that the administrator account has a particular SID that you can scan for, but I’d be willing to bet that most people would write a worm looking for “administrator”. Just think how much less of a problem SQL Slammer would have been if most people had moved SQL Server to some non-default port.

    Simple obfuscating changes aren’t the answer to security issues, but they provide another layer of protection.