What are the CEF field mappings for syslog messages from SecureAuth IdP

Follow

SecureAuth IdP Version affected:  All

 

Description:  

What are the CEF (Common Event Format) field mappings for syslog messages from SecureAuth IdP? 

 

Answer: 

CEF:0|SecureAuth|IdP|{keyvalue(Version)}|{eventid}|{keyvalue(EventName)}|{severity}|cn1={priority} cn1Label=Priority cfp1={keyvalue(AE.IP.RiskScore)} cfp1Label=IPRiskScore cs1={keyvalue(BrowserSession)} cs1Label=BrowserSession cs2={keyvalue(AEResult)} cs2Label=AnalyzeEngineResult cs3={keyvalue(Company)} cs3Label=ComapnyName cs4={keyvalue(RequestID)} cs4Label=RequestID cs5={keyvalue(RequestDuration)} cs5Label=RequestDuration cs6={keyvalue(UserCountryCode)} cs6Label=UserCountryCode cat={category} deviceCustomDate1={timestamp(FixedFormatMilliEpochFormat)} deviceCustomDate1Label=DeviceUTCTime outcome={keyvalue(Succeed)} deviceFacility=authpriv sourceServiceName={keyvalue(Realm)} dst={keyvalue(HostName)} dvc={keyvalue(HostName)} spid={processId} msg={message} requestClientApplication={keyvalue(UserAgent)} src={keyvalue(UserHostAddress)} suser={keyvalue(UserID)}{dictionary( {key}={value})}

 

 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.