ページ1に含まれる内容の要旨
RSA SecurID Ready Implementation Guide
Last Modified November 29, 2001
1. Partner Information
Partner Name Stonesoft Corp.
Web Site www.stonesoft.com
Product Name StoneGate Firewall
Version & Platform
Version 1.6.3
Product Description
StoneGate is the first firewall and VPN solution offering
high security, high performance and availability. It features:
An embedded OS for increased security.
Multiple ISP and VPN load balancing to ensure continuous
network connectivity.
Advanc
ページ2に含まれる内容の要旨
3. Solution Summary Feature Details Authentication Methods Supported RADIUS, TACACS+. ACE/Agent Library Version N/A ACE 5 Locking N/A Replica ACE/Server Support N/A Secondary RADIUS/TACACS+ Yes (up to 10 supported) Server Support Location of Node Secret on Client None stored ACE/Server Agent Host Type UNIX Agent SecurID User Specification Designated users, all users, SecurID as default. SecurID Protection of No Administrators StoneGate system architecture. Authentication serve
ページ3に含まれる内容の要旨
4. Product Requirements • Hardware requirements Component Name: StoneGate Management system CPU make/speed required Pentium processor, suggested minimum processor speed 500 MHz Memory 128 MB minimum, 256 MB or more recommended HD space 4GB for evaluation (20 GB or more for production use). Component Name: StoneGate Firewall Engine CPU make/speed required Pentium processor, suggested minimum processor speed 300 MHz Memory 128 MB HD space 1 GB • Software requirements Component
ページ4に含まれる内容の要旨
5. Partner ACE/Agent configuration Supported authentication types with RSA SecurID product Client-initiated authentication Client initiated authentication means that the user starts the authentication process. It can be done with two tools: Authentication Client software (part of StoneGate VPN Client software) or using Telnet to connect to the firewall cluster on port 2543. It is possible to authorize the client's IP address for a period of time with client initiated authentication. It
ページ5に含まれる内容の要旨
StoneGate Firewall / RSA SecurID Configuration – User Authentication The following steps can be carried out using the Stonegate User Manager GUI: • Create an Authentication service (type can be Radius or Tacacs+). • Create Authentication Server/Servers with correct type. 5
ページ6に含まれる内容の要旨
• All Created Authentication Servers must be bound to the Authentication Service. Having created your Service(s) and Server(s), you must now create users within the StoneGate user Database. If you want to use ACE/Server authentication as your default Authentication Service for all users, create a special user with the UserName: *external* within the StoneGate user database and bind it to the previously created Authentication Service. 6
ページ7に含まれる内容の要旨
Using this generic method of authentication, *external* is the only user you will be required to create within the StoneGate user database. If there is a need to configure Authentication Services on a per user basis, it can be done by creating individual user records within the StoneGate user database and binding them to the appropriate Authentication Service. Using the Security Policy Manager, associate the appropriate access rules to the users or user group being authenticat
ページ8に含まれる内容の要旨
Example SecurID enabled login sequences Firewall initiated authentication with ACE/Server user account set to New PIN-mode. 8
ページ9に含まれる内容の要旨
9
ページ10に含まれる内容の要旨
6. Certification Checklist Date Tested: November 22, 2001 Product Tested Version ACE/Server 5.0.1 ACE/Agent N/A StoneGate firewall & VPN Client 1.6.3 Test ACE RADIUS st N/A N/A 1 time auth. (node secret creation) New PIN mode: System-generated Non-PINPAD token N/A P PINPAD token N/A P User-defined (4-8 alphanumeric) Non-PINPAD token N/A P Password N/A P User-defined (5-7 numeric) No
ページ11に含まれる内容の要旨
7. Known Issues • If a clustered StoneGate firewall solution is used with RSA SecurID then an Agent Host entry must be defined within the ACE/Server database for each firewall cluster member. • The Firewall cluster members share configured authentication service/server information. As a result of this when configuring Agents Hosts on the ACE/Server database, the same Shared Secret value must be used for each cluster member. 11
