No Results Found
The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.
PadJack U.S. Patent #7,530,824, U.S. Patent #8,449,309
Additional Patents and International Patent PendingPadJack, Inc. is a corporation located in Ocala, Florida, and established in 2005. PadJack was developed by a senior IT engineer who recognized the critical need for physical network security when he was simply trying to access the internet while visiting a relative in the hospital. After plugging in a standard network cable into an open RJ45 wall jack, he inadvertently gained access to the internal hospital network. It was then he realized how vulnerable hospitals and medical facilities were if someone with malicious intentions wanted to access their private networks.
As the concept of the PadJack RJ45 lock and block began development, it was foreseen that many facilities were at risk for a physical network security breach. Government and military facilities, hospitals and medical facilities, financial institutions, and nuclear and energy-generating facilities all have areas where jacks or open ports are exposed. Organizations traditionally focus on security at the firewall or system level of their network, but there are exposed network jacks and open ports on the back of VoIP phones in lobbies, conference rooms, unoccupied offices and hallways, critically placing an organization at high risk for an internal security breach. Hence, the creation of the PadJack RJ45 lock, which physically restricts an unauthorized user with an endpoint device access to the network through unsecured RJ45 ports.
Learn MoreThere are three versions of PadJack RJ45 locks. All three versions, PadJack SVE, PadJack SV and PadJack LV, provide the same RJ45 locking and blocking functionality and each type offers organizations a different level of network security based on the purpose of the application.
Determine where your organization needs a layer of physical network security and at what level. For example:
The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.