auth.secureauth
Introduction
The tags beginning with auth.secureauth
identify events generated by the SecureAuth authentication platform.
Valid tags and data tablesÂ
The full tag must have 3 levels. The first two are fixed as auth.secureauth
. The third level identifies the type of events sent.
These are the valid tags and corresponding data tables that will receive the parsers' data:
Product / Service | Tags | Data tables |
---|---|---|
SecureAuth identity platform  |
|
|
|
|
For more information, read more About Devo tags.
Table structure
These are the fields displayed in these tables:
auth.secureauth.events
Field | Type | Field transformation | Source field name | Extra fields |
---|---|---|---|---|
eventdate |
| Â | Â | Â |
hostname |
| split(hostchain, "=", 0) | hostchain | Â |
cefVersion |
| Â | Â | Â |
embDeviceVendor |
| Â | Â | Â |
embDeviceProduct |
| Â | Â | Â |
deviceVersion |
| Â | Â | Â |
signatureID |
| Â | Â | Â |
name |
| Â | Â | Â |
severity |
| Â | Â | Â |
cat |
| Â | Â | Â |
ipRiskScore |
| Â | Â | Â |
priority |
| Â | Â | Â |
browserSession |
| Â | Â | Â |
analyzeEngineResult |
| Â | Â | Â |
companyName |
| Â | Â | Â |
requestID |
| Â | Â | Â |
requestDuration |
| Â | Â | Â |
userCountryCode |
| Â | Â | Â |
deviceUTCTime |
| Â | Â | Â |
dst |
| Â | Â | Â |
dvc |
| Â | Â | Â |
deviceFacility |
| Â | Â | Â |
msg |
| Â | Â | Â |
outcome |
| Â | Â | Â |
requestClientApplication |
| Â | Â | Â |
sourceServiceName |
| Â | Â | Â |
spid |
| Â | Â | Â |
src |
| Â | Â | Â |
suser |
| Â | Â | Â |
secureAuthIdPAppliance |
| Â | Â | Â |
hostchain |
|  |  | ✓ |
tag |
|  |  | ✓ |
rawMessage |
|  |  | ✓ |
auth.secureauth.radius
Field | Type | Extra fields |
---|---|---|
eventdate |
| Â |
hostname |
| Â |
timestamp |
| Â |
server |
| Â |
product |
| Â |
logtype |
| Â |
process |
| Â |
transctionId |
| Â |
eventMessage |
| Â |
hostchain |
| ✓ |
tag |
| ✓ |
rawMessage |
| ✓ |