Configuring Security Attributes
The attributes in this section specify certain security settings for the group:
Step 1 Specify whether to let users store their login passwords on the client system, using the password-storage command with the enable keyword in group-policy configuration mode. To disable password storage, use the password-storage command with the disable keyword.
hostname(config-group-policy)# password-storage {enable | disable} hostname(config-group-policy)#
For security reasons, password storage is disabled by default. Enable password storage only on systems that you know to be in secure sites.
To remove the password-storage attribute from the running configuration, enter the no form of this command:
hostname(config-group-policy)# no password-storage hostname(config-group-policy)#
Specifying the no form enables inheritance of a value for password-storage from another group policy.
This command does not apply to interactive hardware client authentication or individual user authentication for hardware clients.
The following example shows how to enable password storage for the group policy named FirstGroup:
hostname(config)# group-policy FirstGroup attributes hostname(config-group-policy)# password-storage enable hostname(config-group-policy)#
Step 2 Specify whether to enable IP compression, which is disabled by default.
hostname(config-group-policy)# ip-comp {enable | disable} hostname(config-group-policy)#
To enable LZS IP compression, enter the ip-comp command with the enable keyword in group-policy configuration mode. To disable IP compression, enter the ip-comp command with the disable keyword.
To remove the ip-comp attribute from the running configuration, enter the no form of this command. This enables inheritance of a value from another group policy.
hostname(config-group-policy)# no ip-comp hostname(config-group-policy)#
Enabling data compression might speed up data transmission rates for remote dial-in users connecting with modems.
Caution Data compression increases the memory requirement and CPU usage for each user session and consequently decreases the overall throughput of the security appliance. For this reason, we recommend that you enable data compression only for remote users connecting with a modem. Design a group policy specific to modem users, and enable compression only for them.
Step 3 Specify whether to require that users reauthenticate on IKE rekey by using the re-xauth command with the enable keyword in group-policy configuration mode. If you enable reauthentication on IKE rekey, the security appliance prompts the user to enter a username and password during initial Phase 1 IKE negotiation and also prompts for user authentication whenever an IKE rekey occurs. Reauthentication provides additional security.
If the configured rekey interval is very short, users might find the repeated authorization requests inconvenient. To avoid repeated authorization requests, disable reauthentication. To check the configured rekey interval, in monitoring mode, enter the show crypto ipsec sa command to view the security association lifetime in seconds and lifetime in kilobytes of data. To disable user reauthentication on IKE rekey, enter the disable keyword. Reauthentication on IKE rekey is disabled by default.
hostname(config-group-policy)# re-xauth {enable | disable} hostname(config-group-policy)#
To enable inheritance of a value for reauthentication on IKE rekey from another group policy, remove the re-xauth attribute from the running configuration by entering the no form of this command.
hostname(config-group-policy)# no re-xauth hostname(config-group-policy)#
Note Reauthentication fails if there is no user at the other end of the connection.
Step 4 Specify whether to restrict remote users to access only through the tunnel group, using the group-lock command in group-policy configuration mode.
hostname(config-group-policy)# group-lock {value tunnel-grp-name | none} hostname(config-group-policy)# no group-lock hostname(config-group-policy)#
The tunnel-grp-name variable specifies the name of an existing tunnel group that the security appliance requires for the user to connect. Group-lock restricts users by checking if the group configured in the VPN client is the same as the tunnel group to which the user is assigned. If it is not, the security appliance prevents the user from connecting. If you do not configure group-lock, the security appliance authenticates users without regard to the assigned group. Group locking is disabled by default.
To remove the group-lock attribute from the running configuration, enter the no form of this command. This option allows inheritance of a value from another group policy.
To disable group-lock, enter the group-lock command with the none keyword. The none keyword sets group-lock to a null value, thereby allowing no group-lock restriction. It also prevents inheriting a group-lock value from a default or specified group policy
Step 5 Specify whether to enable perfect forward secrecy. In IPSec negotiations, perfect forward secrecy ensures that each new cryptographic key is unrelated to any previous key. A group policy can inherit a value for perfect forward secrecy from another group policy. Perfect forward secrecy is disabled by default. To enable perfect forward secrecy, use the pfs command with the enable keyword in group-policy configuration mode.
hostname(config-group-policy)# pfs {enable | disable} hostname(config-group-policy)#
To disable perfect forward secrecy, enter the pfs command with the disable keyword.
To remove the perfect forward secrecy attribute from the running configuration and prevent inheriting a value, enter the no form of this command.
hostname(config-group-policy)# no pfs hostname(config-group-policy)#
Continue reading here: Configuring Firewall Policies
Was this article helpful?