External SOX reviewers do not want a tour of your security admin screens. They want a dated inventory of who can initiate, approve, and change money-moving Workday tasks, plus proof that those policies are the ones currently active. Workday already ships the reports that build that inventory; the slow part is usually hunting policies by memory instead of by securable item.
This walkthrough is how consultants assemble that evidence in a focused working session: map sensitive duties to domain and business process policies, compare groups that share people, clear pending policy edits, and export proof before the control walkthrough. It does not claim Workday contains a packaged segregation-of-duties engine that auto-certifies SOX. Your control matrix still defines conflicting pairs; Workday shows who holds which permissions today.
Which Delivered Reports Replace Weeks of Spreadsheet Archaeology?
Start from the same delivered security catalog Workday documents for payroll and other modules:
| Report or Task | What Auditors Usually Ask | How You Use It |
|---|---|---|
| Report or TaskView Security for Securable Item | What Auditors Usually AskWhich policy secures this task, field, or web service? | How You Use ItEnter the exact securable item; record Functional Area, policy name, and View/Modify or Get/Put |
| Report or TaskDomain Security Policies for Functional Area | What Auditors Usually AskWhat domains exist in Financials, Payroll, Settlements? | How You Use ItFilter by functional area; export enabled policies and assigned groups |
| Report or TaskBusiness Process Security Policies for Functional Area | What Auditors Usually AskWho can initiate, approve, rescind, or cancel? | How You Use ItCapture Initiating Action and approval step security groups |
| Report or TaskBusiness Process Types and Initiating Security Groups | What Auditors Usually AskWho can start Hire, Journal, Supplier Invoice, Pay? | How You Use ItFast initiator inventory across BP types |
| Report or TaskView Security Groups for User | What Auditors Usually AskWhat groups does this person belong to? | How You Use ItSample high-risk users from your SoD matrix |
| Report or TaskCompare Permissions of Two Security Groups | What Auditors Usually AskDo these two roles overlap dangerously? | How You Use ItDiff policies before merging or cloning groups |
| Report or TaskSecurity Analysis for Security Groups / Action Summary for Security Group | What Auditors Usually AskWhat can this group actually do? | How You Use ItAttach as appendix evidence per role |
| Report or TaskSecurity Exception Audit | What Auditors Usually AskAre there config warnings left unresolved? | How You Use ItClear exceptions before freeze |
| Report or TaskActivate Pending Security Policy Changes | What Auditors Usually AskIs production running the policies we edited? | How You Use ItActivate only after reviewing both pending-change reports |
For the conceptual split between domain policies (data and integrations) and business process policies (who can do workflow actions), keep domain vs. business process security policies open while you build the matrix.
How Do You Translate a SoD Pair Into Workday Objects?
Auditors speak in duties (“create vendor” vs. “pay vendor”). Workday speaks in Domain Security Policies and Business Process Security Policies. Translate each pair once:
- Name the business action (for example, create supplier, approve supplier invoice, settle payment, submit accounting journal, initiate pay calculation).
- Run View Security for Securable Item for the UI task and, separately, for any web service or RaaS report that can perform the same action.
- Record whether access is View/Modify (report and task permissions) or Get/Put (integration permissions). Put includes Get.
- On the matching Business Process Security Policy, record which groups sit on Initiating Action and on approval, correction, cancel, and rescind actions.
- For each person who appears on both sides of a conflicting pair, run View Security Groups for User, then explain whether the overlap is intentional (dual control with different steps) or an accident (same unconstrained group on both sides).
Constrained versus unconstrained groups matter here. An unconstrained Financials administrator group on both Initiate and Approve is a different control story than a constrained role that only sees its own companies. Use constrained vs. unconstrained security groups when you document residual risk.
# Weak evidence pack
- Screenshot of one Domain Security Policy grid
- Verbal claim that "Finance cannot approve their own journals"
- No pending-change check, no user-to-group membership export# Defensible evidence pack (dated export)
1. SoD matrix rows mapped to securable items + policy names
2. Domain + BP policy exports for those functional areas
3. View Security Groups for User for each conflicting person
4. Compare Permissions for any shared groups
5. Pending-change reports empty (or activated with change ticket)What Traps Waste the First Audit Week?
Pending policies. Editing Edit Domain Security Policy Permissions or Edit Business Process Security Policy saves a pending change. Runtime still evaluates the previous activated set until someone runs Activate Pending Security Policy Changes. Review Domain Security Policies with Pending Changes and Business Process Security Policies with Pending Changes first; activation applies every pending edit tenant-wide. See the activation walkthrough in ISU permissions and Activate Pending Security Policy Changes.
Integration bypass. A clean UI approval chain means little if an Integration System Security Group has Put plus web service initiating action on the same process. Include ISSGs in the same matrix when inbound EIBs or Studio jobs can create journals, suppliers, or workers.
Intersection and role-based stacking. People accumulate access through role-based, user-based, and intersection groups. Always resolve membership with View Security Groups for User, not with the org chart alone. Details: role-based, user-based, and intersection groups.
AI and new tools. Any new agent, API client, or service account is another principal. Run the same securable-item lookup before go-live; see security audit before enabling AI agents.
How Does a Consultant Finish the Evidence Pack Quickly?
Work in one pass per functional area that SOX cares about (typically Financial Accounting, Supplier Accounts, Customer Accounts, Banking and Settlement, Payroll or Payroll Interface, and Security Administration itself):
- Export Domain Security Policies for Functional Area and Business Process Security Policies for Functional Area.
- For each SoD pair, attach View Security for Securable Item results.
- Sample real users from HR and Finance rosters with View Security Groups for User.
- Diff overlapping groups with Compare Permissions of Two Security Groups.
- Clear or activate pending policy changes and capture the pending-change reports as empty (or ticketed).
- Store dated exports with the control owner’s name and the tenant name (production vs. non-production clearly labeled).
Kiweely Vine helps when the matrix spans many policies: it works against the connected tenant with consent, traces which groups hold which permissions, and keeps client work isolated so one engagement’s security exports do not mix with another. Pair that with tracing Workday security permissions with an AI agent when you need repeated persona checks before the auditor’s sample arrives.
The outcome auditors notice is not a new product feature. It is a short, dated binder: policies, groups, people, pending-change proof, and a written residual-risk note for any intentional dual access your control owner accepted.
Frequently asked questions
Does Workday ship a segregation of duties product for SOX?
Workday provides domain security policies, business process security policies, and delivered security analysis reports that show who can view, modify, initiate, and approve securable items. Your firm still defines conflicting duty pairs and evidence packs from those reports; Workday does not replace an external control framework.
Why do security edits look correct but auditors still see old access?
Domain and business process policy edits stay pending until Activate Pending Security Policy Changes runs. Group membership changes take effect immediately, but policy permission changes do not. Always review Domain Security Policies with Pending Changes and Business Process Security Policies with Pending Changes before activating.
Which report shows who can initiate a sensitive business process?
Use Business Process Security Policies for Functional Area or Business Process Types and Initiating Security Groups for initiator lists, and View Security for Securable Item when you need the exact policy that secures a task, report field, or web service.
How do I compare two security groups before consolidating roles?
Run Compare Permissions of Two Security Groups, then Security Analysis for Security Groups and Action Summary for Security Group to see secured items and policies for each group before you merge memberships.