Netscape Certificate Management System 6.1, Руководство администратора

Страница: 39 / 840

How Certificate Management System Works
Chapter 1 Overview 39
• End-Entity Services Interface—The end-entity interface is a customizable
HTML interface that can be used for end-entities to enroll in your PKI, renew
certificates, revoke their own certificates, and pick up issued certificates. It
contains forms for different types of enrollments, and for the enrollment
different types of end-entities. The Certificate Manager and the Registration
Manager have an end-entity services interface, the Data Recovery Manager
and OSCP Manger do not.
Logs
Each subsystem produces extensive system and error logs that record various
events and system errors so that you can monitor and debug the system. All log
records are stored in your local file system for quick and easy retrieval.
CMS allows you to sign log files digitally before archiving them or distributing
them for audit purposes. This feature enables you to check whether the log files
were tampered with after being signed.
The log feature is configurable allowing you to select logging levels as well as what
is logged. You can also create custom logs so that events can be separated by the
categories you choose. See “Logs,” on page 263 for complete details.
Auditing
CMS maintains audit trails for all events—certificate requests and issuance,
revocation requests, CRL publication, and so on. These audit records enable you to
detect any unauthorized access or activity.
CMS allows you to set up special users called Auditors who have exclusive access
to these logs, allowing independent auditing of your PKI.
You can customize audit logs to include the information you want to include in the
audit log. See “Signed Audit Log,” on page 277 for complete details.
Internal Database
Each subsystem has its own internal database where it stores such things as issued
certificates, certificate requests, and so on. The internal database is an instance of
Netscape Directory Server that is used exclusively as the internal database for this
subsystem. See “The Internal Database,” on page 290 for complete details.
Authorization
CMS is preconfigured with four types of users who have various access to the
system:
• Administrators who can perform any administrative or configuration task.