User's Guide Part 1

Chapter 3: System planning Security planning
Web-based security management allows an operator to configure users, security levels, privacy
and authentication protocols, and passphrases using the PTP 700 web-based management
interface. The capabilities supported are somewhat less flexible than those supported using the
MIB-based security management, but will be sufficient in many applications. Selection of web-
based management for SNMPv3 security disables the MIB-based security management. PTP
700 does not support concurrent use of MIB-based and web-based management of SNMPv3
security.
Web-based management of SNMPv3 security
Initial configuration of SNMPv3 security is available only to HTTP or HTTPS/TLS user accounts
with security role of Security Officer.
Identify the minimum security role of HTTP or HTTPS/TLS user accounts that will be permitted
access for web-based management of SNMPv3 security. The following roles are available:
• System Administrator
• Security Officer
Identify the format used for SNMP Engine ID. The following formats are available:
• MAC address (default)
• IPv4 address
• Text string
• IPv6 address
If SNMP Engine ID will be based on a text string, identify the text string required by the
network management system. This is often based on some identifier that survives replacement
of the PTP hardware.
Identify the user names and security roles of initial SNMPv3 users. Two security roles are
available:
• Read Only
• System Administrator
Identify the security level for each of the security roles. Three security levels are available: (a)
No authentication, no privacy; (b) Authentication, no privacy; (c) Authentication, privacy.
If authentication is required, identify the protocol. Two authentication protocols are available:
MD5 or SHA.
If privacy will be used, identify the protocol. Two privacy protocols are available: DES or AES
(an AES 128-bit or 256-bit capability upgrade must be purchased).
If authentication or authentication and privacy protocols are required, identify passphrases for
each protocol for each SNMP user. It is considered good practice to use different passphrases
for authentication and privacy. Passphrases must have length between 8 and 32 characters,
and may contain any of the characters listed in Table 60.
Page 3-53