Policy Acceptance Template

Explore

Live Policies

Secure Development Policy

Overview

Purpose:

The purpose of this policy is to establish guidelines and best practices for secure software development within our organization. This policy applies to all software development activities, including in-house development, outsourced development, and third-party software acquisition.

Policy:

Security shall be integrated into the software development process from the outset.

A security review shall be conducted at every stage of the software development life cycle (SDLC), including design, coding, testing, and deployment.

All software shall be designed and developed with security in mind. Security requirements shall be explicitly defined and documented in the requirements specification.

All software shall be tested for security vulnerabilities, including but not limited to:

a. Buffer overflows

b. Injection flaws

c. Cross-site scripting (XSS)

d. Broken authentication and session management

e. Insufficient logging and monitoring

Security testing shall be conducted using both manual and automated methods.

Any security vulnerabilities identified during testing shall be remediated prior to deployment.

Revision History

Date of Change

Policy

Notes

1/31/2022

Secure Development Policy

Create Secure Development Policy.

No results from filter

⁠

Accept

Secure Development Policy 1.1

By clicking this button I acknowledge that I have read the above policy and agree to comply with the policy

❌

No results from filter

⁠

Revision and acceptance filter:

Secure Development Policy

⁠

DO NOT CHANGE

Overview

Revision History

Gallery

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.