The Agile methodology thrives on speed and iteration, but security can often be left behind in the race to deliver new features. Imagine a critical security vulnerability discovered after a much-anticipated feature launch. This scenario can trigger a domino effect – costly delays, brand damage, and potential data breaches. Traditional security testing, often conducted as a separate phase, struggles to keep pace with Agile’s iterative nature.This session will dive deep into a practical paradigm shift: embedding security practices seamlessly within the Agile workflow, from initial planning to ongoing monitoring.

We’ll be exploring practical techniques to build a secure foundation in software development:

• Planning: Proactive threat modelling for identifying potential vulnerabilities early on.
• Coding: Automated tools like pre-commit hooks and code reviews to catch security issues before code merges.
• Build: Dependency scans and static code analysis tools to identify vulnerabilities in libraries and custom code.
• Testing: Dynamic Application Security Testing (DAST), Penetration Testing, and a focus on data security to ensure a multi-layered defense.
• Deployment: Secure deployments by secure access controls and safeguarding secrets.
  
• Monitoring: Continuous monitoring of logs, alerts, and incident response ensures swift action against threats.