Audit
Focus
Focus
Strata Logging Service

Audit

Table of Contents

Audit

Audit logs are written to
Strata Logging Service
by specific products, applications, or services. These are used to record changes made to the service writing the logs.
The products, applications, or services that write audit logs are:
  • Prisma Access Integration with Cisco Meraki SD-WAN
See the following for information related to supported log formats:
AUDIT Field
(Display Name)
Description
event_category
(EVENT CATEGORY)
The category of the event.
  • Prisma Access Integration with Cisco Meraki SD-WAN
    : The HTTP method that Prisma Access used to modify a Meraki resource.
    Example:
    GET
    if Prisma Access made a GET call.
CEF field name: Event Category
EMAIL field name: Event Category
HTTPS field name: Event Category
LEEF field name: Event Category
event_description
(EVENT DESCRIPTION)
A description of the event.
  • Prisma Access Integration with Cisco Meraki SD-WAN
    : The modification that Prisma Access made to the Meraki resource.
    Example:
    Update Non Meraki VPN Peer N_354359432522
CEF field name: Event Description
EMAIL field name: Event Description
HTTPS field name: Event Description
LEEF field name: Event Description
event_dest_url
(EVENT DESTINATION URL)
The URL related to the destination.
CEF field name: Event Destination URL
EMAIL field name: Event Destination URL
HTTPS field name: Event Destination URL
LEEF field name: Event Destination URL
event_dest_vendor
(DESTINATION VENDOR)
Name of the service that sent the log to
Strata Logging Service
.
CEF field name: Destination Vendor
EMAIL field name: Destination Vendor
HTTPS field name: Destination Vendor
LEEF field name: Destination Vendor
event_detail
(EVENT DETAILS)
Details about the event.
  • Prisma Access Integration with Cisco Meraki SD-WAN
    : The Event Category followed by details about the kind of change made and the ID of the object receiving the change. Example:
    UPDATE performed on API set appliance and objectID 1274905
CEF field name: Event Details
EMAIL field name: Event Details
HTTPS field name: Event Details
LEEF field name: Event Details
event_name
(EVENT NAME)
The name associated with an event
  • Prisma Access Integration with Cisco Meraki SD-WAN
    : The Meraki resource that Prisma Access acted on.
    Example:
    updateDevice
    if Prisma Access made an API call to update a device.
CEF field name: Event Name
EMAIL field name: Event Name
HTTPS field name: Event Name
LEEF field name: Event Name
event_result
(EVENT RESULT)
The result of an event.
  • Prisma Access Integration with Cisco Meraki SD-WAN
    : The response code returned from a Meraki API.
    Example:
    200
    if the request was successful.
CEF field name: Event Result
EMAIL field name: Event Result
HTTPS field name: Event Result
LEEF field name: Event Result
event_time
(EVENT TIME)
Time when the log was generated.
  • Prisma Access Integration with Cisco Meraki SD-WAN
    : The time, in UTC, when Prisma Access invoked the Meraki API. Example:
    2023-03-26 16:52:19
CEF field name: Event Time
EMAIL field name: Event Time
HTTPS field name: Event Time
LEEF field name: Event Time
log_source
(LOG SOURCE)
Identifies the origin of the data. That is, the system that produced the data.
CEF field name: Log Source
EMAIL field name: Log Source
HTTPS field name: Log Source
LEEF field name: Log Source
log_source_group_id
(LOG SOURCE GROUP ID)
ID that uniquely identifies the logSourceGroupId of the log. That is, the log source Id of the group.
CEF field name: LogSourceGroupID
EMAIL field name: LogSourceGroupID
HTTPS field name: LogSourceGroupID
LEEF field name: LogSourceGroupID
log_source_id
(LOG SOURCE ID)
Unique identifier of the log source. For example, if a firewall generated the log, this would be the serial number of the firewall.
CEF field name: Log Source ID
EMAIL field name: Log Source ID
HTTPS field name: Log Source ID
LEEF field name: Log Source ID
log_time
(LOG TIME)
Time the log was received in Cortex Data Lake. This is populated by the platform.
CEF field name: Log Time
EMAIL field name: Log Time
HTTPS field name: Log Time
LEEF field name: Log Time
log_type.​value
(LOG TYPE)
Identifies the log type.
CEF field name: Log Type
EMAIL field name: Log Type
HTTPS field name: Log Type
LEEF field name: Log Type
platform_type
(PLATFORM TYPE)
The platform type (Valid types are VM, PA, NGFW, CNGFW).
CEF field name: PlatformType
EMAIL field name: PlatformType
HTTPS field name: PlatformType
LEEF field name: PlatformType
sub_type.​value
(SUBTYPE)
Identifies the log subtype.
CEF field name: Subtype
EMAIL field name: Subtype
HTTPS field name: Subtype
LEEF field name: Subtype
vendor_name
(VENDOR NAME)
Identifies the vendor that produced the data.
CEF field name: Vendor Name
EMAIL field name: Vendor Name
HTTPS field name: Vendor Name
LEEF field name: Vendor Name
vendor_severity.​value
(VENDOR SEVERITY)
Severity associated with the event.
CEF field name: Vendor Severity
EMAIL field name: Vendor Severity
HTTPS field name: Vendor Severity
LEEF field name: Vendor Severity

Recommended For You