title: Should developers be limited to certain software for development?
body: <p><em>Should developers be limited to certain applications for development use?</em></p>
  
  <p>For most, the answer would be as long as the development team agrees it shouldn't matter.</p>
  
  <p><strong>For a company that is audited for security certifications, is there a method that balances the risk of the company and the flexibility, performance of the developers?</strong></p>
  
  <p>Scope</p>
  
  <ol>
  <li>coding/development software</li>
  <li>build system software</li>
  <li>3rd party software included with distribution (libraries, utilities)</li>
  <li><em>(Additional)</em> Remaining software on workstation</li>
  </ol>
  
  <p>Possible solutions</p>
  
  <ol>
  <li><p>Create white-list of approved software where developer must ask for approval for desired software before he/she can use it.  Approval would be based on business purpose/security risk.</p></li>
  <li><p>Create black-list for software.  Developers list all software used.  Review board periodically goes over list.</p></li>
  </ol>
  
  <p>Has anyone had to work at a company that restricted developer tools beyond the team setting? How did they handle the situation?</p>
  
  <p><strong>Edit</strong></p>
  
  <p>Cleaned up question.  Attempted to make less argumentative.</p>