By Pritam Kandel, Applications Engineer
 
Network timing in the enterprise world is often overlooked, and that is a mistake. Network architects or engineers often default to an Internet-based timing architecture for their ultimate source of time. In today’s world of frequent cyberattacks, regulatory compliance requirements and demand for highly stable and accurate network timing, is that the best we can do? Here is another approach: the hierarchy (layering) of timing topology.
By Pritam Kandel, Applications Engineer
 
Network time service is not something many businesses think about as a key component of their critical infrastructures. In fact, it is often overlooked entirely, and in error. As a result, the network architect or engineer often defaults to an easy alternative: using a server or network switch as the source of the network clock and synchronizing these sources to Internet time servers using Network Time Protocol (NTP). This white paper discusses the risks of, and alternative solutions to, "NTP Over the Internet."