Chat now with support
Chat with Support

Defender 5.8 - Administrator Guide

Getting started Managing Defender objects in Active Directory Configuring security tokens Securing VPN access Securing Web sites Securing Windows-based computers Securing PAM-enabled services Defender Management Portal (Web interface) Delegating Defender roles, tasks, and functions Automating administrative tasks Administrative templates Integration with Active Roles Integration with Cloud Access Manager Appendices
Appendix A: Enabling diagnostic logging Appendix B: Troubleshooting common authentication issues Appendix C: Troubleshooting DIGIPASS token issues Appendix D: Defender classes and attributes in Active Directory Appendix E: Defender Event Log messages Appendix F: Defender Client SDK Appendix G: Defender Web Service API

Default Defender Security Policy

Managing Access Nodes

Creating an Access Node

Right-click the Access Nodes container, point to New, and then click Defender Access Node.

New Object - Defender Access Node Wizard reference

Name  Type a name for the Access Node being created.
Description  Type a description for the Access Node being created.
Node Type  Use this list to select a type for the Access Node being created. The following node types are available:
Radius Agent  Allows a NAS device to connect to Defender using the RADIUS protocol. RADIUS is transmitted over UDP and uses port 1812 by default. This is the default setting and is supported by most access devices.
Radius Proxy  Allows RADIUS requests received from a RADIUS Agent access node to be forwarded to another RADIUS Server.
Radius Proxy (to non-negotiating server)  Allows Defender to issue the response request on behalf of the RADIUS Server. This node type is typically used when migrating from RSA to Defender. In some cases, the user ID included in the request sent from the Access Node and proxied by the Defender Security Server to the RADIUS Server cannot be processed by the RADIUS Server, unless accompanied by a password.
Defender Agent  Allows Defender agents to connect and process authentication requests. Typically, this node type is required for use with legacy Cisco ACS devices. Defender agents use a proprietary protocol to transmit data and use TCP (default port number 2626), instead of the UDP of RADIUS.
NetScreen Agent  Select this node type if your Access Node is a NetScreen VPN.
NC-PASS Radius Agent  Select this node type if you are using the NC-Pass two-factor authentication software.
Nortel VPN Agent  Select this node type if you plan to authenticate using an SNK token in synchronous mode.
User ID  Use this list to select the required user ID type. This is the user ID that will be used to locate the user in Active Directory. The available options are SAM Account Name, Defender ID, User Principal Name, Proper Name, and E-mail Address.
If you select E-mail Address, the e-mail address specified on the General tab of the user Properties dialog box is used.
IP Address or DNS Name  Type the IP address or Network ID (IP address or DNS name) from which the Defender Security Server will accept authentication requests.
Port  Type the port number of the Defender Security Server.
Subnet Mask  Type the subnet mask you want to use for the Access Node.
Shared Secret  Type the shared secret you want to use. The shared secret configured on the access device must match the shared secret specified for the Access Node. The shared secret can be up to 256 alphanumeric characters. (For a Defender Agent Access Node, the shared secret can be 16 hex or 24 octal digits).
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating