An audit pattern that records both the acting identity and the represented identity for sensitive actions. It is the cleanest way to preserve accountability during support access, because it avoids overwriting either party’s role. Good logs also capture session start, session end, and customer-visible evidence.
What On-Behalf-Of Audit Logging Captures
On-behalf-of audit logging preserves the full accountability chain for delegated action. It records who initiated the request, who was represented, and what sensitive operation occurred, so the record reflects both authority and accountability instead of collapsing them into a single actor.
This distinction matters most in support, administration, and exception handling workflows, where one person or system legitimately acts for another. A good log also includes session boundaries and user-visible evidence, so the event can be reconstructed without guessing which party actually performed the action.
Why It Matters for Accountability and Review
Without on-behalf-of logging, audit trails often become ambiguous during incident review, compliance review, and customer dispute handling. The log may show an operation happened, but not whether it was initiated by the support technician, the end user, or an automated intermediary.
That ambiguity weakens non-repudiation and makes it harder to prove whether access was authorized, delegated, or abused. It also complicates later recertification and forensic analysis because reviewers cannot reliably separate the represented identity from the acting identity.
For delegated flows, the log should be readable as a narrative of authority: who requested, who executed, under what context, and for which account or tenant. The value is not just visibility, but a defensible chain of custody for sensitive actions.
Where On-Behalf-Of Logging Fits in Access Architecture
This pattern sits at the intersection of authorization, delegation, and auditability. It is especially important when a control model permits one identity to act for another, whether through support tooling, token exchange, impersonation, or privileged workflow mediation. RFC 8693: OAuth 2.0 Token Exchange is a useful reference for understanding token exchange as a delegation mechanism that should remain visible in logs.
In mature environments, the audit record should preserve the original actor, the delegated subject, the scope of the delegated action, and the session context that linked them. NHI Authentication Guide is relevant because delegated and on-behalf-of flows often depend on token exchange, service-to-service authentication, and other identity-bearing mechanisms that need clear audit treatment.
In practice, the same requirement shows up across support tooling, customer success platforms, admin consoles, and workload delegation paths. The logging pattern is most effective when identity representation is explicit rather than inferred from a later access event.
Signals of a Good Audit Record
A usable on-behalf-of log should answer three questions quickly: who acted, who was represented, and what changed. It should also show session start and end boundaries, because delegated access is often time-bounded and the duration is part of the accountability story.
The strongest records include customer-visible evidence, such as case reference numbers, approval context, or transaction identifiers, so the action can be matched to a legitimate support event. Ultimate Guide to NHIs, Regulatory and Audit Perspectives is a useful companion where auditors need to connect identity governance, access review, and audit trail expectations.
When those fields are missing, investigators are left with an activity record that may be technically complete but operationally weak. Good on-behalf-of logging is less about volume and more about preserving the relationship between authority, representation, and action.
Risk and Threat Considerations
Delegated access is attractive to attackers because it can hide behind a legitimate support or administration workflow. If the audit trail fails to distinguish the acting identity from the represented identity, abuse can look like normal business activity and delay detection.
Failure mechanism: The record captures only the downstream action or only the represented user, which destroys the evidence needed to prove delegation boundaries, reconstruct intent, or detect misuse of privileged support access.
Impact: Incident responders may be unable to separate authorized on-behalf-of activity from impersonation, fraud, or excessive privilege use, which weakens forensic analysis and accountability.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP API Security Top 10 addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AU-3 — Content of Audit Records | On-behalf-of logs need both actor and represented identity in the event record. |
| AU-12 — Audit Record Generation | The subject is an audit pattern for generating the right records for sensitive delegated actions. | |
| AC-3 — Access Enforcement | Delegated action logging supports enforcement of who may act on behalf of whom. | |
| Recommendation — Record delegated actor, represented subject, and session context in audit events. Generate audit records for delegated actions that preserve accountability chains. Enforce delegation rules so on-behalf-of actions are only logged when authorized. | ||
| OWASP API Security Top 10 | API5 — Broken Function Level Authorization | On-behalf-of actions often use privileged functions that must be authorized and auditable. |
| Recommendation — Authorize privileged functions and log the represented principal for each action. | ||
| CIS Controls v8 | CIS-8 — Audit Log Management | The term is fundamentally about preserving auditability for delegated sensitive actions. |
| Recommendation — Centralize and retain logs that preserve both acting and represented identities. | ||
Practitioner Guidance
Governance implication: Treat on-behalf-of logging as a control requirement whenever a workflow allows one identity to act for another. The log design should be reviewed with the same seriousness as the delegation policy itself, because the audit trail is what makes the delegated authority defensible after the fact.
What to watch for: Logs that collapse the acting and represented identities into one field, omit session boundaries, or lack support case context are a sign that the control may not survive audit or incident review. If the event cannot be explained to a third party from the log alone, the record is probably too weak.
Related resources from NHI Mgmt Group
- What is the difference between session logging and audit-ready evidence?
- Why do access control and audit logging matter so much in ISO compliance programmes?
- Should organisations use proxy logging or native PostgreSQL audit features?
- Why do startups need centralized logging before they need a formal audit?
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on September 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
