Policy 7230A - Department of Administration

Policy 7230A - Department of Administration Policy 7230A - Department of Administration

10.10.2014 Views

5.4. Application Protection The following are the Non-Mandatory Baselines that support the Application Protection section of the Default Security Requirements: 5.4.1. Apply Security Principles to Code Development To ensure that information systems offer the appropriate level of security with the greatest level of efficiency, Agencies should engineer controls into the solution during development: 5.4.1.a Standard Development Practices • Development processes should start with the creation and documentation of a secure Concept of Operations (ConOps). • Development processes should make use of documented and repeatable standards and processes. • Security training should be provided for the development team. • Quality management should be performed throughout the development process. • Code should be developed in a dedicated and secured environment. • Code should be stored in securely maintained repositories. 5.4.1.b Development Training Recommendations • Development training should address all standard development practices. 5.4.1.c Development Training Scheduling and Frequency • Secure code development training should be provided for all developers within 30 days of initial assignment of the individual to the development team. • Secure code development training should be provided thereafter for all developers on an at least annual basis. Where possible, team members will be trained together as a group. 5.4.1.d Quality Assurance • Code development quality assurance practices should focus on the following: o Cross-site scripting vulnerabilities. o Buffer overflows. o Race conditions. o Object model violations. o Poor user input validation. o Poor error handling. o Exposed security parameters. 14

o Passwords in the clear. o Violations of the stated security policy. 5.5. Maintain Records Agencies should capture documentation appropriate to all systems configuration processes: • Create and maintain a systems component and configuration inventory. • Document and retain copies of SDLC requirements. • Document and retain copies of all system implementation plans. 15

5.4. Application Protection<br />

The following are the Non-Mandatory Baselines that support the Application<br />

Protection section <strong>of</strong> the Default Security Requirements:<br />

5.4.1. Apply Security Principles to Code Development<br />

To ensure that information systems <strong>of</strong>fer the appropriate level <strong>of</strong> security with<br />

the greatest level <strong>of</strong> efficiency, Agencies should engineer controls into the<br />

solution during development:<br />

5.4.1.a Standard Development Practices<br />

• Development processes should start with the creation and<br />

documentation <strong>of</strong> a secure Concept <strong>of</strong> Operations (ConOps).<br />

• Development processes should make use <strong>of</strong> documented and<br />

repeatable standards and processes.<br />

• Security training should be provided for the development<br />

team.<br />

• Quality management should be performed throughout the<br />

development process.<br />

• Code should be developed in a dedicated and secured<br />

environment.<br />

• Code should be stored in securely maintained repositories.<br />

5.4.1.b Development Training Recommendations<br />

• Development training should address all standard<br />

development practices.<br />

5.4.1.c Development Training Scheduling and Frequency<br />

• Secure code development training should be provided for all<br />

developers within 30 days <strong>of</strong> initial assignment <strong>of</strong> the<br />

individual to the development team.<br />

• Secure code development training should be provided<br />

thereafter for all developers on an at least annual basis.<br />

Where possible, team members will be trained together as a<br />

group.<br />

5.4.1.d Quality Assurance<br />

• Code development quality assurance practices should focus<br />

on the following:<br />

o Cross-site scripting vulnerabilities.<br />

o Buffer overflows.<br />

o Race conditions.<br />

o Object model violations.<br />

o Poor user input validation.<br />

o Poor error handling.<br />

o Exposed security parameters.<br />

14

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!