The second step to integrate web application security in Agile is to embed security activities into the existing Agile workflows and practices. This means that security becomes an integral part of the regular tasks, roles, and ceremonies of the Agile team. In order to do this, you should align security activities with the Agile phases such as planning, coding, testing, and deploying. Additionally, you should utilize security checklists, guidelines, and templates to ensure consistency and quality. Examples of security activities that can be embedded in Agile are security stories, which capture the security needs and expectations of users and stakeholders; security tasks, which are specific actions that need to be performed; security testing, which verifies that the web application meets requirements and does not contain any vulnerabilities; and security reviews, which evaluate and improve the security quality and maturity of the web application and team. These activities should be tracked and reported using the same tools and metrics as other tasks. Furthermore, they should be broken down into manageable units of work that are assigned to appropriate team members. In addition, automated and manual tools such as code analysis, scanning, fuzzing, ethical hacking should be used during security testing. Moreover, feedback from internal and external sources such as peers, experts, auditors, customers should be included in security reviews.