PKCS#12 interface for private keys in soft certificates CSP for use of user certificates in Windows certificate store PIN policy.PKCS#11 interface for encryption tokens (USB and smartcards) smartcard operating systems: TCOS 1.2, 2.0 and 3.0 smart card reader interfaces: PC/SC, CT-API.IKE (Aggressive mode and Main Mode), Quick Mode XAUTH for extended user authentication IKE config mode for dynamic assignment of a virtual address from the internal address pool (private IP) PFS support of certificates in a PKI: Soft certificates, smartcards, and USB tokens: Multi Certificate Configurations Pre-shared secrets, one-time passwords, and challenge response systems RSA SecurID ready. Encryption Algorithms: AES with 128, 192 and 256 Bit or Triple DES.Hash Algorithms: SHA1, SHA 256, SHA 384, or SHA 512 Bit.DH Group: Group 2 or higher (DH starting from a length of 1024 Bit).FIPS compatibility is always given if the following algorithms are used for set up and encryption of the IPsec connection: The embedded cryptographic module incorporating these algorithms has been validated as conformant to FIPS 140-2 (certifi-cate #1051). The IPsec Client incorporates cryptographic algorithms conformant with the FIPS standard.
Symmetric processes: AES 128,192,256 bits Blowfish 128,448 bits Triple-DES 112,168 bits ĭynamic processes for key exchange: RSA to 2048 bits seamless rekeying (PFS)
IPsec (Layer 3 Tunneling),conform to RFC IPsec proposals can be determined through the IPsec gateway (IKE, IPsec Phase 2) Event log communication only in the tunnel MTU size fragmentation and reassembly, DPD, NAT-Traversal (NAT-T) IPsec tunnel mode The NCP Secure Client – Juniper Edition supports all IPsec standards in accordance with RFC Windows (64 Bit): Windows 8, Windows7, Windows Vista, Windows XP Windows (32 Bit): Windows 8, Windows7, Windows Vista, Windows XP, Technical Data: Secure Client – Juniper Edition for Windows 32/64 bit: Technical Data
0 kommentar(er)
