How Can I Ensure My Argent TCP/IP Connection Is Secure?

Remember, Argent is the choice of Intelink – Google ‘Intelink’ to see just who these bad boys are.

Argent has a Built-in Encryption Algorithm

The CRC-64 built in the packet prevents any external data manipulation

Using the built-in encryption mechanism further prevents external data peeking

Argent provides ECB and OFB algorithms

The encryption seed changes from packet to packet

The encryption is initiated by the client, which allows you to set a different encryption level for different remote sites

Of course the encryption adds some CPU overhead

For links that are already secured through VPN, or trusted sites, you might consider using no encryption, but we don’t recommend it

(It may be secure today, but that might all change after a Service Pack…)

The default setting is no encryption, which can be adjusted in the registry path

Argent AT 3.1A-1501-C and above:

32-bit: HKEY_LOCAL_MACHINE\Software\Argent\COMMON\TCP_ENCRYPT_LEVEL

64-bit: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Argent\COMMON\TCP_ENCRYPT_LEVEL

Prior to Argent AT 3.1A-1501-C:

32-bit: HKEY_LOCAL_MACHINE\Software\Argent\{Argent Product}\TCP_ENCRYPT_LEVEL

64-bit: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Argent\{Argent Product}\TCP_ENCRYPT_LEVEL

0 is for no encryption

1 is for ECB

2 is for OFB

The {Argent Product} in Argent AT versions prior to 3.1A-1501-C are as follows:

Product Registry Leaf Name

Argent for Compliance

ARGENT_FOR_COMPLIANCE

Argent Defender

ARGENT_DEFENDER

Argent for Exchange

ARGENT_FOR_EXCHANGE

Argent Guardian Ultra

ARGENT_GUARDIAN_ULTRA

Argent for Oracle

ARGENT_FOR_ORACLE

Argent Sentry Ultra

ARGENT_SENTRY_ULTRA

Argent for SNMP

ARGENT_FOR_SNMP

Argent for SQL Server

ARGENT_FOR_SQL_SERVER

Argent for Active Directory

ARGENT_FOR_ACTIVE_DIRECTORY

Argent for XenServer

ARGENT_FOR_XENSERVER

Argent for VMware

ARGENT_FOR_VMWARE

Argent for Security

ARGENT_FOR_SECURITY

Argent for SharePoint

ARGENT_FOR_SHAREPOINT