PCI compliance scanning with Juniper network=s application acceleration Platform (VPN)

We have to do compliance scanning now going forward every quarter and w do have 3 users that have the juniper vpn  installed on their local computer.  This is causing us to fail along with the following other problems.   Any advice to clear these failures would be appreciated:
1. We have an ASA 5505 and we are getting the following problem, that I think is being caused by the lack of a ssl certificate on the ASA??Not sure.  but the failure description is:  An SSL cert associates an entity (person ,ORG, host, etc) with a public Key.  In and SSL connection Client Autheticates the server's cert and extracts the public Key in the cert to establish the secure connection.  
So the question is where do they want a cert?.  I can't put it on the ASA and it doesn't make sense to put it on the 3 users computers that use the Juniper VPN.   Is this happening because the Juniper VPN is not the latest version?

2.  Anothewr failure is labled Pre-shared key off-line bruteforcing using IKE aggressive Mode (CVE-2002-1623)

3. Lst problem is  again related the the Juniper VPN and port 500/udp.  IDE is used during Phase 1 and Phase 2 of the establishing connection.  Phse 1 the two ISAKMP peers establish a secure authenticated channel which to communicate.  Every participant in the IKE must possess a key that my be rather pre-shared or Publickey.  There are inherent risks to configurations that use pre-shared keys which ar exaggerated when aggressive mode is used.
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

btanConnect With a Mentor Exec ConsultantCommented:
1. Should be setting up certificate check for the vpn client with the ASA. See example

2/3. IKE can use Main mode or Aggressive mode. If you get your devices to use Main mode rather than Aggressive mode you mitigate the issue. Some simply disable the aggresive mode inbound with the command "crypto ikev1 am-disable" on cisco ASA platform.

Also the vulnerability is the length and strength of your key. From 8-16 characters alphanumeric is a fairly strong key. If you are concerned and want to better mitigate the vulnerability then increase the length of the key and/or improve the strength of the key.

See this

barl009Author Commented:
this sounds good, have to analyze each white paper.  Have to get help to implement.  So for 1.  Just to clarify, you want me to put a $300 cert on the three workstations that use this Juniper client?  or just a self created cert in the ASA?  
I am sending this off to my consultant company as they had not a good answer for this.  these articles seem very explicit and valuable.
Thank you.
btanExec ConsultantCommented:
I dont suggest self sign certificate but it is up to your company business decision. Having cert that is issued by CA will be of higher assurance than self signed. Furthermore self signed cert are not in the list of trusted CA though you can still manually import to get pass with trust chain check and warning.
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

barl009Author Commented:
So can a issued CA be put on the CISCO ASA?  And if so where can I find the steps?
btanExec ConsultantCommented:
No problem - see my last post URL
Configure a trusted identity certificate on your ASA. It is important that you use an identity certificate from a trusted CA source for your ASA. An ASA identity certificate is the certificate that the ASA will hand out to the sslvpn clients that connect to it. In order for everything to work correctly the certificate must match the ASA hostname/IP address. Also, the end-users client must trust the CA that generated the ASA's identity certificate. A self-signed or other non-trusted CA cert is fine for testing but not for production.

Within ASDM you can sign up for a special promo certificate from Entrust if you'd like but any trusted public CA will do the trick. To configure the identity certificate on your ASA do the following:

1)      First obtain your identity certificate. Make sure it is in PKCS12 format. Also, be sure it includes the complete certificate chain.

2)      Go to Configuration > Remote Access VPN > Certificate Management > Identity Certificates. Click Add.

3)      If your ASA will be in DNS then you can use the FQDN as the identifier in the certificate. If it will not be in DNS (only during testing, for production it must be in DNS) then be sure to use the IP address as the identifier.

4)      That's it your done! However, if you need to do it the hard way by using a certificate signing request then proceed to setups 5 through end below.

5)      If you need to generate a certificate signing request from the ASA then instead of doing step 2 do the below instead.
barl009Author Commented:
barl009Author Commented:
Thank you
All Courses

From novice to tech pro — start learning today.