SQLServerCentral / Editorials / SQLServerCentral.com / Responsibility for Security / Latest Posts

RE: Responsibility for Security

JimBama08 — Tue, 08 May 2012 12:35:36 GMT

The editorial mentions that "we haven't yet built a good, easy to understand framework that provides good monitoring and auditing in a way the majority of DBAs can understand and implement". I think that last bit is a fallacy. As a DBA and a manager, I know that I cannot be the person to implement monitoring/auditing of database security. I have a lot of responsibility for managing security at the database layer, but I will always have the "keys to the kingdom". As such, auditing has to happen from some other angle to prevent "inside jobs", which represent a large percentage of data breaches to begin with.I've implemented an appliance-based approach that does packet-sniffing in a previous company and I think that was a good approach. I'd be curious to know how others are tackling database auditing.

RE: Responsibility for Security

RwCC — Tue, 08 May 2012 02:37:00 GMT

As a developer and not a SQL professional *ducks for cover* I take security very seriously, my problem in my current office is that security is rarely a considered feature. It generally tends to be nothing more than making sure a user is a member of an Active Directory group...

RE: Responsibility for Security

David.Poole — Mon, 07 May 2012 09:41:18 GMT

[quote]"Most developers are reluctant to take the responsibility in security and assume that this is the job of web administrators and network engineers."[/quote]I think it is a case of the feat that responsibility = blame. With very few exceptions the developers I have worked with have taken security very seriously but have been hampered by lack of knowledge.Like most subjects you can read up on basic things such as preventing SQL Injection Attacks and Least Privilege Permissions but going beyond that what do you do? Do the non-technical parts of your company realise that it takes time to design a robust system?Do they realise that they have a very big role to play in helping with security?Security, like quality has to be part of the DNA of your internal systems. Everyone is responsible.There also needs to be a clear chain of command so if a hole is found everyone knows who to escalate it to in order to get it fixed.

RE: Responsibility for Security

bitbucket-25253 — Mon, 07 May 2012 07:58:36 GMT

Responsibility for security starts at the top (CEO - Chief Executive Officer) and carries down the chain of command to IT Managers, System Administrators, DBAs, Developers, and last but not the least users. There should be in place a training program, (and budget monies) for new employees joining the company at any level (with a requirement for the program to be successfully completed before attempting to perform any job duties).Further there also must be periodic reviews to analyze any security breaches, and a plan developed to close those "loop holes", with specific assignments at each level of command including a time table for completion of the corrective action required.I believe it must be a cooperative effort, whole heartedly supported by every individual that has access to data, in any form what so ever, either at the DB level, or handling of say printed management reports.

RE: Responsibility for Security

chrisn-585491 — Mon, 07 May 2012 07:02:14 GMT

If management makes security a priority and makes sure there are proper resources and training in place, then applications and systems would be more secure. As developer, I have [i]X[/i] amount of time and budget and [i]Y[/i] amount of projects and responsibilities. Guess what is a lower priority than functionality?

RE: Responsibility for Security

IceDread — Mon, 07 May 2012 00:21:14 GMT

Hehe good one Jeff Moden.Interesting editorial, thou I'd like to see some real statistics.I know there are developers that are ignorant in nature as well as there are those who are not. "Most developers are reluctant to take the responsibility in security and assume that this is the job of web administrators and network engineers."I do not want to believe that and I do not believe that. All thou maybe we have a better morale in Sweden? I don't really believe that ether thou.

RE: Responsibility for Security

Jeff Moden — Sun, 06 May 2012 20:18:35 GMT

I've found that the real reason why there are security holes in systems is because companies have been talked into having them. "Oh... the developers need to have DBO or SA privs in production." "Oh... we have super users that need to be able to see everything." "Oh... it takes too long to write/rollout secure code."Oh oh oh-oh oh!

Responsibility for Security

Steve Jones - SSC Editor — Sun, 06 May 2012 13:39:46 GMT

Comments posted to this topic are about the item [B]Responsibility for Security[/B]