Remote Connectivity - Cisco CISCOWORKS COMMON SERVICES 3.0 User Manual

Appendix A Understanding CiscoWorks Security

Remote Connectivity

78-16571-01
Windows—CiscoWorks back-end processes are executed with permissions
•
set to the user casuser. Some of the special CiscoWorks Server processes are
run as a service under the localsystem user ID.
These processes include:
– Daemon manager
Web server
–
Servlet engine
–
Rcp/rsh service
–
Tftp service
–
Corba service
–
Database engine
–
CiscoWorks foreground processes (typically cgi-bin programs or servlets) are
executed under the control of the web server and the servlet engine which all
run as the user localsystem.
The local system user has special permissions on the local system but does
not have network permissions.
CiscoWorks provides several services for RCP, TFTP communication with
devices. These services are targeted for use by CiscoWorks applications, but
can be used for purposes other than network management.
The CiscoWorks Server uses the at command to run software update jobs for
the Resource Manager Essentials Software Image Manager application. Jobs
run by the at command run with system level privileges.
The remote connectivity details for Windows and Solaris are:
UNIX Systems—The CiscoWorks daemon manager only responds to
•
requests to start, stop, register, or show status for CiscoWorks back-end
processes from the CiscoWorks Server.
Windows Systems—The CiscoWorks daemon manager only responds to
•
requests to start, stop, register, or show status for CiscoWorks back-end
processes from the CiscoWorks Server.
User Guide for CiscoWorks Common Services
Server Security
A-5