Better security with code analytics and predictive maintenance

How well do you know your codebase? What opensource libraries are you using? What's out of date? How hard is it to update software? Who's going to fix something and are they are point of failure?

By leveraging git analytics and understanding the expertise of your developers, you can not only identify potential problem areas in your code but also minimise key person risk.

Do we need Artificial Intelligence to help? Or just better data to augment the intelligence of managers, developers and your security people?

During this talk, we'll discuss methods to answer:

• Are there indicators within your codebase that highlight hotspots? Can you easily identify the areas most prone to opensource library vulnerabilities?
• Do you have key person risk for your applications? Who holds the critical knowledge of the code, and how dispersed is that expertise across your team?
• When things break, who can fix your code? What happens when the person responsible for key modules is unavailable?
• Are we losing technical capabilities and knowledge with staff attrition?
• Are security vulnerabilities an indicator of development practices?