{"id":584,"date":"2021-03-14T17:05:57","date_gmt":"2021-03-14T21:05:57","guid":{"rendered":"https:\/\/www.gybernov.com\/new\/?p=584"},"modified":"2021-03-28T21:27:05","modified_gmt":"2021-03-29T01:27:05","slug":"ssdlc","status":"publish","type":"post","link":"https:\/\/www.gybernov.com\/new\/ssdlc\/","title":{"rendered":"Secure Software Development Life Cycle (SSDLC)"},"content":{"rendered":"
\"Sprial\"
spiral<\/figcaption><\/figure>\n
\"V-shaped\"
v-shaped<\/figcaption><\/figure>\n
\"Waterfall\"
waterfall<\/figcaption><\/figure>\n
\"Agile\"
agile<\/figcaption><\/figure>\n
\"Iterative\"
iterative<\/figcaption><\/figure>\n

The most important principle of SSDLC (Secure Software Development Life Cycle) is to offer a secure development process thus minimizing the risk of vulnerabilities in our solution that we develop, Organisations that implement that style of development will significantly reduce the weaknesses and threats of exploitation<\/p>\n

It also brings a layer of quality during our\u00a0 QA stage.<\/p>\n

QA vs Security\u00a0<\/b><\/p>\n

Quality assurance allows to verify and validate that a given application works as desired by the user and by “business owners”. and It concerns the application reliability.<\/p>\n

A secure development adds quality to software, but the opposite is not always true<\/p>\n

Having the security functions does not mean that the application is enough secure. Indeed, these security functions can be disabled by default and can be poorly implemented or poorly designed and include security vulnerabilities.<\/p>\n

all security activities are stated here, we will explain each step in next week to give you better picture and help you to take advantage on the process
\njust keep in mind the follwing standards :<\/p>\n