Defender 5.11 - Administration Guide

RADIUS Payload tab

This tab allows you to view the current and assign a new RADIUS payload to the Defender Security Server object.

On this tab, you can use the following elements:

• Payload  Shows the RADIUS payload that is currently assigned to the Defender Security Server object. When there is no RADIUS payload assigned to the Defender Security Server object, this option displays <undefined>.
• Select  Allows you to select a RADIUS payload to assign to the Defender Security Server object.
• Clear  Unassigns the current RADIUS payload from the Defender Security Server object.
• Effective  Click this button to view the RADIUS payload that will apply to a specific user for a particular Defender Security Server/Access Node combination. The windows that opens looks similar to the following:

Creating a RADIUS payload object

Remote Access Dial in User Service (RADIUS) is an access-control protocol that verifies and authenticates users based on challenge-response method. This protocol allows a computer to verify your identity, find out what you are allowed to access, and then tell you all of this.

The RADIUS protocol is built around the AAA concept, which stands for authentication (the process of verifying identity), authorization (the process of defining what you are allowed to do), and accounting (the process of monitoring logging statistics and usage information).

The purpose of RADIUS payload is to have the Defender Security Server send information back to the NAS device for reasons such as extra security or for accounting or other reasons specific to the NAS.

To create a RADIUS payload object

1. On the computer where the Defender Administration Console is installed, open the Active Directory Users and Computers tool (dsa.msc).
2. In the left pane (console tree), expand the appropriate domain node, and then expand the Defender container.
3. Right-click the RADIUS Payload container, point to New, and then click Defender RADIUS Payload.

A wizard starts.

4. In the Enter a name and description for this RADIUS Payload step, type a name and description for the payload being created. Click Next.
5. On the Select the attributes to return when access is approved step, use the Add button to add the attributes you want the RADIUS payload to return, and assign values to those attributes. For more information, see RADIUS payload attributes.

RADIUS payload attributes

The next table lists the attributes you can assign to a RADIUS payload. The RADIUS payload will return these attributes after user’s access to the resource has been approved. For instructions on how to create a RADIUS payload, see Creating a RADIUS payload object.

Configuring security tokens

For users to authenticate and access resources protected with Defender, you need to configure and assign security tokens supported by Defender to them. Defender can work with a number of security tokens, which include native Defender tokens and third-party tokens.

The native Defender tokens include the following:

• Defender Soft Token Can be installed and used in various environments and operating systems, such as Android, Java Runtime Environment, iOS, and Windows.
• E-mail token  Allows users to authenticate by using one-time passwords sent to their e-mail address.
• GrIDsure token  Allows users to authenticate by using a GrIDsure Personal Identification Pattern (PIP).
• SMS token  Allows users to authenticate by using one-time passwords sent to their SMS-capable device.

Third-party security tokens supported by Defender include Authy, DIGIPASS GO, Google Authenticator, Symantec VIP credentials, and YubiKey.

• Configuring Defender Soft Token
• Configuring GrIDsure token
• Enabling the use of Google Authenticator
• Configuring SMS token
• Configuring e-mail token
• Configuring VIP credentials
• Configuring YubiKey
• Defender Token Programming Wizard reference