This story was originally published on HackerNoon at: https://hackernoon.com/what-will-the-next-gen-of-security-tools-look-like.
Code generated by programs or in collaboration with programs should be tested, hacked, and fixed by other programs.
Check more stories related to machine-learning at: https://hackernoon.com/c/machine-learning. You can also check exclusive content about #ai, #cybersecurity, #technology, #security-tools, #next-gen-security, #future-of-cybersecurity, #tech-tools, #cybersecurity-ai, and more.

This story was written by: @mbalabash. Learn more about this writer by checking @mbalabash's about page, and for more stories, please visit hackernoon.com.

Software engineering faces many problems today, including the rapid escalation of security incidents (see data in the post). New tools could help improve the situation, and here is the list of essential characteristics they must have: - they are development tools with security features - they derive a functional description of the product from the code and provide a convenient UI/UX for working with this knowledge - they find inconsistencies, bugs and vulnerabilities - they generate tests to prove found bugs and vulnerabilities - they have a certain set of expert knowledge (for example, access to tons of write-ups on certain vulnerabilities, etc.) - they suggest patches to fix problems in the code and functionality of the product The core idea is simple: code generated by programs or in collaboration with programs should be tested, hacked, and fixed by other programs.

What Will the Next-Gen of Security Tools Look Like? 03:58 Share

Machine Learning Tech Brief By HackerNoon

Shownotes Transcript

What Will the Next-Gen of Security Tools Look Like?