This article explains the reasons and behavioral specification differences regarding why access logs cannot be extracted from a child Business Unit during the Data Extract of an Audit Trail. It also describes the correct extraction method to comprehensively retrieve audit logs across all Business Units.
When using the "Data Extract" activity in Automation Studio to retrieve Audit Trails, the behavior in a child Business Unit varies depending on the log type as follows:
■ Cause / Behavioral Specification Differences
This behavior occurs because the scope of recorded events varies depending on the log type.
Scope of Audit Trail Access Log (Access Log):
Recorded Content: "User authentication events" such as logins, logouts, and password changes.
Management Scope: Centrally managed at the Enterprise (parent Business Unit) level.
Restriction: Extractable only from the parent Business Unit.
Scope of Audit Trail Activity Log (Activity Log):
Recorded Content: "User operation and modification events" such as content editing, automation operations, and data extension imports/exports.
Management Scope: Events that occur within each individual Business Unit.
Feature: Extractable from a child Business Unit as well.
■ Detailed Solution Steps:
To comprehensively retrieve audit trails (especially access logs), please perform the data extraction from the parent Business Unit (Enterprise account).
■ Additional Information:
When extracting audit trails from the parent Business Unit (Enterprise level), it is possible to retrieve not only the logs of the parent Business Unit itself but also the logs of all child Business Units under it collectively. If centralized management is required for internal auditing or other purposes, it is recommended to build an automation to periodically extract logs from the parent Business Unit side, rather than individually within each child Business Unit.
005386961

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.