• Eric M Russell - Thursday, January 12, 2017 10:44 AM

    Security has to be baked into the infrastructure and development process rather than sprinkled on top of a deliverable like spice. For example, servers and databases in development should be provisioned by the DBA with default security in place, and developer should not have privilege to alter security settings or add logins without a change request. If the application and database objects are developed within those constraints, then the developers will soon learn what's "normal", how to code within the box, and the deliverable will deploy to production without issue.

    No, it's more likely that DBAs will not undertand why development needs certain things and will refuse change requests that, if granted, would allow the development to take place more rapidly and be more thorioughly tested during the course of development, because DBAs don't understand that developers need open access to mchines for experimentation.  Of course they also need some secured machines, since they have to ensure that their output works on properly configured and secured systems, but too many DBAs and SysAdmins fail to understand that. 
    Another point is that your environment is presumably a pretty unprofessional and unhappy one, as you recruit people who can't be trusted to use as your developers - or is that just something that isn't there but is made to appear to be there by a baselessly prejudiced "I'm a DBA and these plebeian developers are all too dim to understand" attitude that all too many DBAs and SysAdmins display, perhaps a consequence of the over-specialisation pushed by incompetent managers leading to class boundaries in the office?

    Tom