Systemic Bugs in Third Party Developed Code
Luke Rogerson software development training report writing client communication sdlc
It’s been a few weeks since we launched our report writing training course “The Art of Report Writing” and since then we’ve had some great conversations with folks on their challenges around reporting and client communication. One conversation that stood out was around a client using a third-party developer for several products. When a testing team assessed each product over a year it became apparent that not only were the vulnerabilities similar from product to product, but many instances of the same vulnerability were also present, indicating a systemic issue with both the code and the development team’s practices.