Contents
Why developers should not have access to production?
3 Answers. Developers should never have direct access to the production environment. From an audit perspective this is a big no-no as this poses fraud risks. Also if one developer makes a mistake he can take down your critical systems which could have a high impact on your business.
Should developers have read only access to production?
No. Developers should not have access to production database systems for the following reasons: Availability and Performance: Having read-only rights to a database is not harmless.
How does a developer get access to a production server?
The process for giving a developer access the production server goes something like this: 1. Developer says “I need access to a production server.” 2. Server guys say “okay, you’re logged on (as an admin by the way).” 3. Developer does whatever. The same applies on moving code.
Why do some companies not allow developer Access?
Some companies have well structured SOP’s in place and simply do not allow developer access at all. Many people (specially in IT departments) don’t like this approach because they somehow feel threatened by it, not because the machines are exposed to developers, but because they feel they loose control over things.
Is it dangerous to have a developer in production?
If the view is that developers are somehow more “dangerous” because they have knowledge of the inner workings of the application and database guess what: keeping them out of production doesn’t change that. If you don’t trust your developer fire him.
How does everyone else handle programmer access to production boxes?
Their argument is they can get the users working faster without having to work with IT support to make the needed changes, but IT support is concerned with changes being made to production without their knowledge or ownership since IT is ultimately responsible for server uptime. How does everyone else handle programmer access to production boxes?