Ms. de Sousa. The watering hole analogy is interesting and I think you have identified some major problems that can be addressed using agile, autonomous, and resilient technologies; but I would like to consider the idea that the Watering hole has already poisoned when we get to it to take our drink - for example, the NVD currently lists over 61,000 known vulnerabilties in the commercial products that we employ to build our "network infrastructure" and a vulnerability growth rate that is generally between 10 and 20 new vulnerabilities per day (i.e., imo, it is getting worse not better).

How can "programmable infrastructure" address the problem that the watering hole is already poisoned before we even get to it to drink?