Study guide
10.4 Vault Reports, Report Authorizations & the Export Vault Data (EVD) Utility
CyberArk Defender - PAM PAM-DEF
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Vault Architecture, Network & Security
1.1 CyberArk PAS Core Architecture & Component Topology 1.2 Vault OS Hardening, Network Isolation & Port Requirements 1.3 Vault Cryptography, Encryption Keys & Master User Recovery
2 Chapter 2: Vault Configuration, Administration & CLI Utilities
2.1 Vault Server Configuration Files & DBParm.ini Tuning 2.2 Vault Administrative Utilities & PARClient Commands 2.3 Event Notification Engine (ENE) & Notification Administration
3 Chapter 3: Password Vault Web Access (PVWA) Administration
3.1 PVWA Web Portal Architecture & Interface Configuration 3.2 PVWA REST API Administration & Lifecycle Automation 3.3 PVWA Security Settings, User Access & Session Timeouts
4 Chapter 4: Central Policy Manager (CPM) Architecture & Operations
4.1 CPM Service Architecture, Logs & Multi-CPM Load Distribution 4.2 The Credential Management State Machine: Change, Verify & Reconcile 4.3 CPM Plug-in Architecture, Process/Prompts Files & Custom Plug-in Troubleshooting 4.4 Loosely Connected Devices: Rotating Laptop & Workstation Credentials
5 Chapter 5: Safe Design, RBAC & Account Governance
5.1 Enterprise Safe Architecture & Naming Conventions 5.2 Safe Permissions, Authorizations & Safe Handler Delegation 5.3 Object Versioning, Retention Policies & Storage Quotas 5.4 Mandatory Account Properties, Account Types & Linked Accounts 5.5 Vault Users, Predefined Groups & Vault-Level Authorizations
6 Chapter 6: Account Discovery & Lifecycle Workflows
6.1 Automated Account Discovery, Detection Rules & Pending Accounts 6.2 Dual Control Workflows, Multi-Level Approvals & Master Approver 6.3 Exclusive Access, One-Time Passwords (OTP) & Check-out Automation 6.4 Bulk Onboarding: Password Upload Utility, Bulk Upload REST API & AccountUploader
7 Chapter 7: Master Policy & Platform Management
7.1 Master Policy Framework & Enterprise Compliance Rules 7.2 Platform Architecture, Settings Tree & Platform Duplication 7.3 Platform Policy Overrides, Advanced Settings & Target Tuning
8 Chapter 8: Privileged Session Manager (PSM) Core Architecture
8.1 PSM Architecture, Jump Host Isolation & Service Accounts 8.2 PSM Connection Components (PSM-RDP, PSM-SSH, PSM-Web) 8.3 PSM Universal Connector Framework & Custom Integrations 8.4 Split Workflow: Separating Session Use from Credential Retrieval
9 Chapter 9: PSMP, HTML5 Gateway & Session Security
9.1 PSM for SSH (PSMP) Architecture & Unix Proxy Brokering 9.2 PSM HTML5 Gateway Architecture & Clientless Web Access 9.3 Session Recording, Storage in Recordings Safes & Vault Retention 9.4 CyberArk Remote Access (Vendor PAM): Administering Third-Party Privileged Access
10 Chapter 10: Live Session Auditing, Reporting & Privileged Threat Analytics
10.1 Live Session Monitoring, Shadowing & Active Termination 10.2 Privileged Threat Analytics (PTA) Behavioral Anomaly Detection 10.3 PTA Automated Incident Response & SIEM Integration (CEF/Syslog) 10.4 Vault Reports, Report Authorizations & the Export Vault Data (EVD) Utility
11 Chapter 11: Application Access Manager (AAM) & Secrets Management
11.1 AAM Credential Provider (CP) Architecture & Local Memory Cache 11.2 Central Credential Provider (CCP) & Web Service Integration 11.3 Application Server Credential Provider (ASCP) & Application Authentication (AppID) 11.4 Conjur Secrets Manager & Cloud-Native DevOps Workflows
12 Chapter 12: Directory Integration, Disaster Recovery & Troubleshooting
12.1 Directory Integration: LDAP Mapping, RADIUS MFA & SAML 2.0 SSO 12.2 Disaster Recovery (DR) Vault & PADR Replication Architecture 12.3 Vault Backup Operations with PAReplicate & Safe Recovery 12.4 Diagnostic Procedures, Vault/CPM/PSM Error Codes & System Recovery
10.4 Vault Reports, Report Authorizations & the Export Vault Data (EVD) Utility
Key Takeaways Explain This Topic AI
The PVWA generates nine built-in reports: Privileged Accounts Inventory, Applications Inventory, Privileged Accounts Compliance Status, Entitlement, Activity Log, Users, Safes, Owners List, and License Capacity.
PVWAMonitor is the default group whose members may generate and manage reports, and PVWAReports is the default Reports Safe, created automatically when the first report is generated.
A report contains only the information the generating user is already authorized to access, so Safe permissions - not report parameters - determine report scope.
Running the Privileged Accounts Compliance Status report for the entire system requires adding the user to the Auditors group in addition to PVWAMonitor membership.
The Export Vault Data utility, ExportVaultData.exe, exports Vault data to TXT or CSV files or to an MSSQL database, with output types including SafesList, UsersList, LogList, Italogfile, and MasterPolicySettings.
Last updated: September 2026
10.4 Vault Reports, Report Authorizations & the Export Vault Data (EVD) Utility
Quick Answer: CyberArk exposes audit evidence through two very different channels. Inside the PVWA, nine built-in reports — Privileged Accounts Inventory, Applications Inventory, Privileged Accounts Compliance Status, Entitlement, Activity Log, Users, Safes, Owners List, and License Capacity — are generated by members of the PVWAMonitor group and saved into the Reports Safe, PVWAReports , which the PVWA creates automatically the first time a report runs. Outside the PVWA, the Export Vault Data (EVD) utility, ExportVaultData.exe , exports Vault data to TXT/CSV files or an MSSQL database so it can be consumed by third-party analytics. The governing rule for both: a report contains only what the user who generated it was already authorized to see.
The Nine Built-In PVWA Reports
Each report answers a different audit question, and each carries its own permission requirements.
Report What it provides Required permissions
Privileged Accounts Inventory Information about all privileged accounts in the system, filtered as needed In the included Safes: List accounts , View Safe members . Users without View Safe members see only information about their own activities.
Applications Inventory Information about the application IDs (AppIDs) in the system In the Vault: Audit users . Can be generated for users at the same level or lower in the Vault hierarchy.
Privileged Accounts Compliance Status Account compliance and management status against policy In the included Safes: List passwords/files , plus View Audit or Confirm Safe request in Safes configured for dual control. Membership in PVWAMonitor . Add the user to the Auditors group to run it for the entire system.
Entitlement Users' entitlement rights across PAM - Self-Hosted In the Vault: Manage users or Audit users
Activity Log Activities performed in the Vault In the Vault: Audit users for user-related activity; View audit in Safes for Safe/account-related activity
Users User activity, and active vs. non-active users over a period, including disabled users In the Vault: Manage users , Audit users
- Safes Safes and their properties by location, or active/non-active Safes over a period —
- Owners List Safe owners and their permissions —
- License Capacity Licensed user types and objects, the maximum licenses for each, and how many are consumed —
Two of these deserve emphasis because candidates confuse them constantly. Privileged Accounts Inventory answers "what accounts exist?" . Privileged Accounts Compliance Status answers "are those accounts actually being managed in line with policy — and when is the next change due?" . An auditor asking whether rotation is working wants the Compliance Status report, not the Inventory.
License Capacity is the report to reach for when onboarding suddenly starts failing across the estate: it shows consumed versus maximum licenses per user type and object, which is frequently the real cause.
Configuring Who Can Run Reports
Reporting is governed by two parameters under Administration → Configuration Options → Reports :
The reports group parameter specifies the group of users who can generate and manage reports. Its default value is PVWAMonitor . Members of PVWAMonitor can view the reports they generated and the reports shown on their My Reports page. Only users specifically granted the required permissions in the Reports Safe can see all generated reports.
The Reports Safe parameter specifies the Safe where reports are saved. Its default value is PVWAReports , and the Safe is created automatically when the first report is generated — so on a freshly installed system the Safe legitimately does not exist yet.
The provisioning sequence an administrator follows is therefore short: add the user to the PVWA Monitoring group, have them open the Reports page and run a report, and the PVWA adds their account to the Reports Safe as part of that first run.
How Safe Permissions Limit Report Scope
This is the single most important reporting concept on the exam, and it is a security control rather than a bug:
Reports contain only the information that the user who generated the report is authorized to access . Any other information is excluded, regardless of the properties specified in the Reports parameters.
The practical consequences follow directly:
Two auditors running the same report on the same day legitimately receive different row counts, because they are members of different Safes.
Adding a user to PVWAMonitor does not widen what they can see; it only grants the ability to run reports at all. Scope is still bounded by Safe-level permissions.
To produce a genuinely enterprise-wide compliance report, the generating identity must have visibility across the estate — which is why the documentation directs you to add the user to the Auditors group for a system-wide Privileged Accounts Compliance Status report.
A "missing data" complaint about a report is almost never a reporting defect. It is a Safe membership gap on the generating user.
The Export Vault Data (EVD) Utility
The PVWA reports are designed for human consumption inside the portal. EVD exists to get Vault data out of CyberArk entirely , so it can be loaded into a SIEM, a data warehouse, a GRC platform, or a long-term archive.
The EVD utility enables you to create reports — such as a list of Safes or incoming requests — by exporting data from the Vault to TXT or CSV files , with each report saved in a separate file . It can also export to an MSSQL database by changing its target.
It is run from a command line as ExportVaultData.exe : ExportVaultData \VaultFile="D:\ExportVaultData\Vault.ini" \CredFile="D:\ExportVaultData\auditor.cred" \Target=File \LogList="D:\ExportVaultData\loglist.txt"
That invocation creates a log activities report for the Vault defined in Vault.ini , connecting as the user identified by the auditor.cred credential file, and saves the output to loglist.txt .
Parameters and Output Types
- Parameter Purpose
- \VaultFile The Vault.ini describing which Vault to connect to
- \CredFile The credential file identifying the exporting user (commonly an auditor identity)
- \Target File or MSSQL . Optional when exporting to a file; default File
- \LogNumOfDays Days of history included in the Safe and user log activities report. Default 1
- \Separator / \Qualifier / \UseQualifier Control CSV delimiting and quoting
- \LogFile Where EVD writes its own execution log
- \BundleTransaction How EVD batches requests to the Vault; relevant to FilesList and LogList
Each \<OutputName>=<FileName> pair requests one export, and at least one output file must be specified . The available output types include SafesList , UsersList , GroupsList , GroupMembersList , OwnersList , FilesList , LogList , RequestsList , ConfirmationsList , LocationsList , EventsList , ObjectProperties , Italogfile (the system log), and MasterPolicySettings (Master Policy settings including exceptions).
Two EVD Errors Worth Recognizing
ITACM012S — "Timeout has expired error when FilesList reporter executed." Occurs on large reports; the fix is to run the FilesList report with \BundleTransaction set to Yes .
ITATS379E — "Authentication failure for User %s. Incompatible client version." The EVD utility and the Vault are not on the same version ; upgrade both to the same major version.
EVD terminates automatically on any error and writes the error to its log file, named Log.txt by default and placed at the location given in \LogFile .
Choosing Between PVWA Reports and EVD
- Need Use
- An auditor wants compliance evidence on screen, scoped to their own Safes PVWA built-in report
- Scheduled nightly extract of Vault activity into Splunk or a data warehouse EVD
- A dump of the Master Policy including its exceptions, for change-control evidence EVD MasterPolicySettings
- Confirming how many licenses remain before a large onboarding wave PVWA License Capacity report