@@ -0,0 +1,26 @@
|
|||||||
|
---
|
||||||
|
id: "APP-SRC-004"
|
||||||
|
category: "application-security/source-code"
|
||||||
|
revision-version: 1
|
||||||
|
revision-date: "2024-01-08"
|
||||||
|
estimate-time: "1h"
|
||||||
|
frameworks:
|
||||||
|
- name: "soc2"
|
||||||
|
sections: ["CC1.4", "CC5.2", "CC8.1"]
|
||||||
|
---
|
||||||
|
|
||||||
|
## Purpose
|
||||||
|
|
||||||
|
Formalizing a proper development lifecycle helps your engineer in
|
||||||
|
their jobs and helps you to scale your team. It reduces the chances of
|
||||||
|
human error.
|
||||||
|
|
||||||
|
## Implementation
|
||||||
|
|
||||||
|
Write a document with your development lifecycle. It should include:
|
||||||
|
planning, analysis, design, coding, testing, and maintenance. Don’t
|
||||||
|
forget secure coding practices (eg code review) and quality.
|
||||||
|
|
||||||
|
## Evidence
|
||||||
|
|
||||||
|
- System development lifecycle document
|
||||||
Reference in New Issue
Block a user