Hp Secure Key Manager Instrukcja Użytkownika Pobierz pdf (Strona 223)

For example, the ﬁlename audit.log.1.2002-04-04_160146.demo would identify this ﬁle as:

• An Audit Log.

• The ﬁrst log ﬁle in the log index.

• A ﬁle created on 2002-04-04 at 16:01:46.

• A log from the SKM with the hostname ’demo’.

This naming convention allows you to transfer log ﬁlesfrommultipleSKMstothesameremotelogserver

while avoiding the problem of overwriting log ﬁles due to naming conﬂicts. These ﬁle names are not

visible from the CLI or the Management Console.

Syslog

The syslog pr

otocol is used to transmit event notiﬁcation messages across networks. Messages that are

recorded in

any of the logs can also be sent to an external server that is conﬁgured to receive messages

via the sysl

og protocol. You can conﬁgure one or two syslog servers. When you conﬁgure two syslog

servers, the SKM sends syslog messages to both.

Youshouldbeawareofthefollowingbeforeconﬁguring syslog on SKM.

For more information on rotating log ﬁles off of the SKM, see the section titled Log Rotation.

• By default, the SKM transmits messages using syslog facility “local1;” however, this is conﬁgurable

on a per–log–basis. Refer to RFC 3164, “The BSD syslog Protocol,” for details about syslog.

• Syslog is

not a secure protocol. Event notiﬁcation messages that are sent to an external server

are not en

crypted or signed. As such, it is not the recommended method for transferring logs

from the

SKM.

• Regardless of whether syslog is enabled or disabled for any particular log, all log messages

continue to be saved to the normal log ﬁles on the SKM, and all logs still use the traditional

rotation/transfer mechanism.

• Changes to the syslog conﬁguration take effect immediately for all logs except the Audit Log.

With re

gard to the Audit Log, all existing CLI sessions continue to abide by the syslog settings that

were i

n effect when the CLI session began. Once a user ends a CLI session and logs back in, the

new sy

slog settings take effect for that session.

Syslog message format

When messages on the SKM are syslogged, they appear at the remote syslog server with an additional

preﬁxof:

where <LogName> might be “System,” “Audit,” or “Activity,” depending on which log the message

is from. The format of the timestamp and origin host/IP are determined by the remote syslog server

software. Sometimes, the origin host/IP will be repeated twice in the message preﬁx. The message body

(the part after “<LogName>”) is the same as the entry in the local log ﬁle.

An example from the System Log is shown here:

original log message:

---------------------

2005-09-12 10:23:47 irwin.company.com KMS Server: Starting KMS Server

log message at syslog server (displays on one line):

-------------------------------------------------------

Sep 12 10:23:48 irwin.company.com demo System: 2005-09-12 10:23:47 irwin.company.com KMS

Server: Starting KMS Server

Secure Key Manager

223

1 2 ... 218 219 220 221 222 223 224 225 226 227 228 ... 326 327

Komentarze do niniejszej Instrukcji

Brak uwag

Hp Secure Key Manager Instrukcja Użytkownika Strona 223

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Przechowywanie Hp Secure Key Manager