GITBOOK-935: change request with no subject merged in GitBook

departments-operations/security/playbooks/vulnerability-management-process.md

@@ -117,7 +117,7 @@ In this discussion, the Security Team will inform stakeholders (27) about the is
 
 Next, the Security Team will create action items (28), in the form of JIRA tickets, for each of the involved stakeholders.
 
-The Squad responsible for fixing the vulnerability will follow their normal development workflow (11). Once the fix is complete, the Squad will request the Security Team a security validation (12) to confirm if the vulnerability has been mitigated. If the fix doesn't mitigate the vulnerability, the Security Team will provide recommendations to the Squad on how to fix it and the Squad will repeat the development process (11). If the vulnerability is successfully resolved, the process will continue as usual to release the patched asset (22).
+The Squad responsible for fixing the vulnerability will follow their normal development workflow (11). As per the recent org change (where squads are working a more project-oriented approach) then a project with the vulnerabilities is submitted to request squad's help in fixing those vulnerabilities. Once the fix is complete, the Squad will request the Security Team a security validation (12) to confirm if the vulnerability has been mitigated. If the fix doesn't mitigate the vulnerability, the Security Team will provide recommendations to the Squad on how to fix it and the Squad will repeat the development process (11). If the vulnerability is successfully resolved, the process will continue as usual to release the patched asset (22).
 
 <figure><img src="../../../.gitbook/assets/process_7.png" alt=""><figcaption></figcaption></figure>