![](/images/new-backgrounds/1213396/213396365x1.webp)
Using Security Features
Access to HP Jetdirect configuration parameters can be controlled through combined use of the available security features. Table 7.2 provides examples of various settings and the associated level of access control.
Table 7.2 | Settings for Access Control (1 of 2) | |||
|
|
| ||
Settings |
| Level of Access Control | ||
|
|
| ||
● | Accessible through HTTP | Low | ||
| (embedded Web server), | Best suited for trusted environments. | ||
| SNMP v1/v2c applications, or | Any system can access the HP Jetdirect | ||
| Telnet |
| ||
|
| configuration parameters through the embedded | ||
|
|
| ||
● | Administrator password | Web server, Telnet, or SNMP management | ||
| not set |
| software. Passwords are not required. | |
● | Default SNMP v1/v2c |
| ||
| community names used |
| ||
● | No authentication or |
| ||
| encryption |
|
| |
● Access control list empty |
| |||
|
|
| ||
● | Administrator password set | Medium | ||
● | Limited security for | |||
| Set Community Name set | If the Administrator password and SNMP v1/v2c | ||
● The Access Control List | Set Community Name are known, access is | |||
limited to: | ||||
| contains host entries and | |||
| ● systems listed in the Access Control List, and | |||
| checks HTTP connections | |||
● Telnet and other | ● SNMP v1/v2c management applications | |||
| protocols disabled. |
| ||
|
|
|
|
ENWW | Security Features 183 |