Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Responsibility for Security Expand / Collapse
Author
Message
Posted Sunday, May 6, 2012 1:39 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 7:43 PM
Points: 33,046, Visits: 15,152
Comments posted to this topic are about the item Responsibility for Security






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1295720
Posted Sunday, May 6, 2012 8:18 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 11:30 PM
Points: 36,706, Visits: 31,156
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!


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1295758
Posted Monday, May 7, 2012 12:21 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, June 3, 2014 8:16 AM
Points: 295, Visits: 1,011
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.
Post #1295790
Posted Monday, May 7, 2012 7:02 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Yesterday @ 12:35 PM
Points: 622, Visits: 1,571
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 X amount of time and budget and Y amount of projects and responsibilities. Guess what is a lower priority than functionality?

Post #1295900
Posted Monday, May 7, 2012 7:58 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 4:25 PM
Points: 5,563, Visits: 24,684
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.





If everything seems to be going well, you have obviously overlooked something.

Ron

Please help us, help you -before posting a question please read

Before posting a performance problem please read
Post #1295918
Posted Monday, May 7, 2012 9:41 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, July 18, 2014 9:15 AM
Points: 2,889, Visits: 1,778
"Most developers are reluctant to take the responsibility in security and assume that this is the job of web administrators and network engineers."


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.


LinkedIn Profile
Newbie on www.simple-talk.com
Post #1295970
Posted Tuesday, May 8, 2012 2:37 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, May 9, 2012 1:51 AM
Points: 52, Visits: 52
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...
Post #1296289
Posted Tuesday, May 8, 2012 12:35 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, February 8, 2013 10:21 AM
Points: 22, Visits: 195
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.


~~ Everything in moderation, including moderation. ~~
Post #1296678
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse