Software Security Guidelines
The following guidelines are intended to provide criteria to be used in evaluating the security of software for use at UF, and/or to guide purchase or development of software. These guidelines will be used as part of the Risk Assessment process when evaluating the risk of software.
General security features
- Authentication uses GatorLink accounts. Web applications use Shibboleth, workstation access uses UFAD.
- Use of the software does not interfere, preclude, or circumvent anti-virus controls of the end-user device, server or network.
- Does not require privileged access on end-user devices to function.
- Applies the principle of least privilege for access to data and application functionality.
- Role-based authorization, implemented preferably via ARS roles or university affiliations. Use of UFAD groups is acceptable if preferred methods are not available, but procedures must be in place to monitor and modify role assignments based on personnel and job duty changes.
- Capability to log activity per the UF Audit and Logging Policy and Standard.
Web application security features
- Follow OWASP guidelines. The OWASP 2016 top 10 proactive controls are:
- Verify for Security Early and Often
- Parameterize Queries
- Encode Data
- Validate all inputs
- Implement Identity and Authentication Controls
- Implement Access Controls
- Protect Data
- Implement login and intrusion detection
- Leverage security frameworks and libraries
- Error and exception handling
- Web applications should be reviewed and/or tested by someone other than the primary developer, to identify security concerns and faults.
- A developer should be retained to address security concerns and/or bugs as they are discovered.