Yan Ke and Feng Deng stayed with Juniper after the acquisition but then left Juniperthe company in 2005 andto startedstart Northern Light Venture Capital, a China concept venture capital firm focused on early and growth stage opportunities in TMT, consumer, clean technologies, and life science industries.<ref>http://www.crunchbase.com/person/yan-ke</ref><ref>http://www.nlightvc.com/En/</ref>
Nir Zuk stayed with Juniper after the acquisition but then left in 2005 to start [[Palo Alto Networks]].<ref name = Nir/> Palo Alto Networks products are similar to OneSecure/NetScreen/Juniper's IPS technology as they share a common heritage.{{citation needed|date=January 2017}}
==2015 "unauthorized code" incident==
{{main article|ScreenOS}}
Analysis of the firmware code hasin also2015 shownshowed that there could exist a backdoor key could exist using [[Dual_EC_DRBG]]. enablingThis would enable whoever holdheld that key to passively decrypt traffic encrypted by ScreenOS. This is enabled by some very strange code in ScreenOS, which could possibly be a deliberate backdoor. This possible backdoor still exists in ScreenOS.<ref name="wired-secret-code-in-junipers-firewalls">{{cite web | url=https://www.wired.com/2015/12/juniper-networks-hidden-backdoors-show-the-risk-of-government-backdoors | title=Secret Code Found in Juniper's Firewalls Shows Risk of Government Backdoors | author=Kim Zetter | work=Wired | publisher=wired.com | language=English | date=2015-12-18 | accessdate=2017-01-05}}</ref>
In December 2015 Juniper Systems announced that they had discovered "unauthorized code" in the ScreenOS software that underlies their NetScreen devices, present from 2012 onwards. There were two vulnerabilities: One was a simple root password backdoor, and the other one was changing a point in Dual_EC_DRBG so that the attackers presumably had the key to use the preexisting (intentional or unintentional) [[kleptographic]] backdoor in ScreenOS to passively decrypt traffic.<ref>http://blog.cryptographyengineering.com/2015/12/on-juniper-backdoor.html</ref>
