
RELEASE PHASE OF THE
SECURE SOFTWARE DEVELOPMENT LIFE CYCLE

WITH US TODAY
THE RELEASE PHASE
OF THE SECURE SDLC
THE RELEASE PHASE
• confirming that the software works as optimally in the production environment as it did in the development environment • obtaining feedback from end-users in order to make appropriate tweaks • conducting maintenance and support tasks • confirming that the software in production meets customer and user needs according to the initial requirements.

CONTINUOUS MONITORING
AND LOGGING OF THE SOFTWARE
STAY AHEAD OF CYBER-CRIMINALS
• Login events (successes and failures) • Authorization events (successes and failures) • 4xx errors (client errors) • 5xx errors (server errors) • Database syntax errors • Access control exceptions • Validation errors • CSRF token validation errors
It is important for developers, operations admins and security engineers to collaborate during the entire development process, including during the release and post-production phase, in order for all members of the software development team to be better equipped to mitigate high-level software failures which often occur due to a lack of collaboration and involvement from software engineers. In the release phase of the SSDLC development engineers are responsible for ensuring that critical application processes and events are logged, and consequently work closely with operations admins and security engineers.

USING MONITORING TOOLS TO WATCH FOR SECURITY EVENTS
AND TRENDS FOR ATTACK SIGNATURES
USING MONITORING TOOLS

CORRELATION BETWEEN THE LOGS AND THE TRAFFIC INFORMATION AVAILABLE
