Writing provisioner audit log in CEF
You can write provisioner audit logs in Common Event Format (CEF) for PingFederate. PingFederate provides an option of writing elements from the audit log and the provisioner audit log at runtime to a syslog receiver for parsing and analysis using ArcSight from Micro Focus.
Steps
-
Edit
<pf_install>/pingfederate/server/default/conf/log4j2.xml. -
Uncomment one of the preset appender configurations:
-
OutboundProvisionerEventToCEFSyslog(aSocketappender under theOutbound provisioner audit log : CEF Formatted syslog appendersection)This
Socketappender is followed by two related appenders,PingFailoverandRollingFile. Together, they create a runningprovisioner-audit-cef-syslog-failover.logfile in the log directory in the event that CEF logging fails for any reason. Both appenders must also be enabled (uncommented). -
OutboundProvisionerEventToCEFFile(aRollingFileappender under theOutbound provisioner audit log for CEFFilesection)Review inline comments and notes in the
log4j2.xmlfile for more information about each appender.
-
-
If you are configuring the
OutboundProvisionerEventToCEFSyslogSocketappender, replace the placeholder parameter values for the syslog host. -
If you are configuring the
OutboundProvisionerEventToCEFSyslogSocketappender, uncomment thePingFailoverappender reference (<appender-ref ref="OutboundProvisionerEventToCEFSyslog-FAILOVER"/>) from theProvisionerAuditLoggerLoggerelements located under theSet up the Outbound provisioner audit loggersection.As indicated in the IMPORTANT comments for the loggers, you must also remove some of the existing appender references.