Today Yogi might have said: "You can learn a lot from Discovery."

Yogi Berra supposedly advised: "When you come to a fork in the road, take it." 

I prefer to take the most efficient, safest, fastest, least expensive, least intrusive, and least-risky road. I will pass on the expensive route that is slower, adding risk exposure, and is not reliable. If you are in the passenger seat giving me directions - please choose route one.

In API security, NightVision offers API Discovery/Documentation using static analysis.  The software finds your inactive, zombie, or shadow APIs. These endpoints, poorly taken care of, could allow hackers access. NightVision solves for this, in literally seconds - almost like a "spell check for API Security".

Estimates suggest over 80% of code written today are APIs. Developers rush to get their APIs released. While Yogi did catch a perfect game in the world series, not many APIs go out perfectly. Discovery/documentation is essential. 

Yogi is also famous for: "You can observe a lot by watching." Perhaps more importantly in software security, Yogi noted: "We made too many wrong mistakes." NightVision can observe, but it can also help you avoid mistakes before deployment, and before you get in trouble.

There are two roads for API Security. The prevailing route today is to monitor APIs after they go into production in what is described as "traffic". Alternatively, NightVision uses static analysis to discover/document APIs before deployment. The benefits are speed, huge labor savings, completeness, confirmation, and risk abatement.

With the "traffic approach", many shortcomings/risks arise:

a. infrastructure changes

b. agent installation

c. sharing/exposure of your sensitive data

d. expensive data ingestion and processing

In addition, you will never know if all of your inactive/zombie APIs are found and secure because they "may not come to the ballpark" for a while, or maybe never. As Yogi said, "if people don't come out to the ballpark, nobody's going to stop them".

Think of the traffic approach like a Toll booth.

a.  As with the likely infrastructure change, a toll plaza must be built which impacts the route/costs

b.  Like an agent that will add latency, a cashier has to operate the toll booth

c.  Data has to be provided, and a need to share sensitive data outside your firewalls

d.  Data ingestion and processing for large amount of API traffic is expensive

Most noteworthy, you won't know what you don't know. Like with a toll booth, some commuters go through the toll daily. Some once per week. Some on occasion. Others in the countryside may never drive through the toll. You can't log what does not pass through. As Yogi says, "nobody goes there anymore, it's too crowded!"

The beauty of NightVision is that you know where you are going, what your costs are, how long it will take, and that you are safe. Another Yogi-ism:

"You've got to be very careful if you don't know where you are going, because you might not get there."