{"id":1429,"date":"2005-06-10T00:00:00","date_gmt":"2005-06-10T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/06\/10\/juniper-brings-best-of-ipsec-ssl-to-vpn-lineup\/"},"modified":"2021-12-30T11:39:22","modified_gmt":"2021-12-30T11:39:22","slug":"juniper-brings-best-of-ipsec-ssl-to-vpn-lineup","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/06\/10\/juniper-brings-best-of-ipsec-ssl-to-vpn-lineup\/","title":{"rendered":"Juniper Brings Best Of IPsec, SSL To VPN Lineup"},"content":{"rendered":"<p>Juniper Networks has added flexibility to its security lineup with an upgrade to its VPN family that combines the benefits of IPsec and SSL technology.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>With the 5.0 version of Instant Virtual Extranet, the platform Juniper&#8217;s SSL VPN family runs on, the vendor is adding a new dual-mode feature that can automatically switch between IPsec and SSL for transport.  This flexibility could help customers cut costs as they decrease their reliance on separate IPsec infrastructures, said Steve Fuller, president and CTO of solution provider Networks Group, Brighton, Mich.<\/p>\n<p>&#8220;I&#8217;ve had customers who deployed SSL but kept their IPsec infrastructure up and running, usually for a select subset of power users.&#8221;<\/p>\n<p>The upgrade also adds enhanced remediation capabilities to the Juniper Endpoint Defense Initiative (JEDI) that enable a network to propose fixes for devices that try to connect but do not meet security requirements, Ganitsky said.<\/p>\n<p>http:\/\/www.securitypipeline.com\/news\/164301972<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1429","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1429","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1429"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1429\/revisions"}],"predecessor-version":[{"id":3916,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1429\/revisions\/3916"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1429"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1429"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1429"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}