The University of Arizona
  Dashboard > Web Application Best Practices > Web Application Best Practices
Web Application Best Practices Log In   View a printable version of the current page.
Web Application Best Practices

Added by Duffy Gillman , last edited by Ed Murphy on May 12, 2009  (view change)
Labels: 
(None)

In response to growing concerns on the UA campus relating to computer security this guide is under development to establish best practices for web application development. This guide is being developed by a cross-departmental team of software managers and engineers.


Web Application Development is a large topic with many best practices being connected to the specific technology platform being utilized. For instance, PHP/Apache/MySQL development has some specific best practices that are not applicable to .Net/IIS/MS SQL-Server development.  This guide contains sections for specific web application best practices related to .Net, Java, PHP and ColdFusion.
 
Security itself is large topic that covers many areas including, but not limited to: the server, the network, application code, data source (database), and the client (browser).  The security section of this guide focuses on application code.  It briefly discusses the data source and the server.  Securing the network and server is best left to Network and Systems Administrators and is beyond the scope of this document.
 

This guide covers:

Team Contacts
Ed Murphy (team lead)
Assistant Director
Enterprise Applications, UITS
email
Brett Bendickson
Support Systems Analyst, Principal
Enterprise Applications, UITS
email
Duffy Gillman
Enterprise Systems Architect
Infrastructure Services, UITS
email
Powered by Atlassian Confluence 2.7.2, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators