<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Export Vault Data Quick Start in PAM Self-Hosted Articles</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/export-vault-data-quick-start/ta-p/1429720</link>
    <description>&lt;P&gt;Export Vault data is a data dumping tool for customers looking to do more advanced reporting and analytics then the out of box reporting function can provide. The ExportVaultData utility exports data from the Vault to TXT or CSV files, from where they can be imported into third party applications or databases. Each report is saved in a different file. Most EVD implementations will require the customer to have skills in database management, reporting, and scripting. These skills are needed as EVD does not have filters beyond how many days old the dumped data is and will require the customer to collect, link up, and create reports of their own.&lt;/P&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;H2 id="ExportVaultData(EVD)-EVDmustberunwiththefollowingVaultandSafeauthorization:"&gt;EVD must be run with the following Vault and Safe authorization:&lt;/H2&gt;
&lt;P&gt;Vault authorizations:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;&amp;nbsp;Audit All&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Safe authorizations:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;View Audit – for the Owners List, Files List, User and Safe Activities, and Events List&lt;/LI&gt;&lt;LI&gt;Retrieve Files – on the System Safe for the System Log List&lt;/LI&gt;&lt;LI&gt;Update Files – on the System Safe for the System Log List&lt;/LI&gt;&lt;LI&gt;Access Safe without Confirmation&lt;/LI&gt;&lt;LI&gt;Confirm Safe Requests – for the Requests List and Confirmations List&lt;/LI&gt;&lt;/UL&gt;
&lt;H2 id="ExportVaultData(EVD)-ListofEVDoutputreports"&gt;List of EVD output reports&lt;/H2&gt;
&lt;TABLE&gt;&lt;COLGROUP&gt;&lt;COL /&gt;&lt;COL /&gt;&lt;/COLGROUP&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;FilesList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A files list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;LogList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A log activities report will be generated&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;OwnersList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;An owners list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;RequestsList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;
&lt;P&gt;An incoming requests list report. will be&lt;BR /&gt;			generated&lt;/P&gt;
&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;SafesList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A Safes list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;GroupsList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A groups list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;GroupMembersList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;
&lt;P&gt;A group members list report will be&lt;BR /&gt;			generated.&lt;/P&gt;
&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;UsersList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A users list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;LocationsList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A locations list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;ConfirmationsList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;
&lt;P&gt;A request confirmations list report will be&lt;BR /&gt;			generated.&lt;/P&gt;
&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;Italogfile&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A system log (ITAlog) file will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;EventsList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;An events list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;ObjectProperties&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A file categories list will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;
&lt;P&gt;One or more reports in any combination can be dumped in a single run of the EVD utility&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Example commands:&lt;/B&gt;&lt;/P&gt;
&lt;P&gt;Export to a local file&lt;/P&gt;
&lt;P&gt;ExportVaultData \VaultFile="Vault.ini" \CredFile="user.ini" \Target=File \fileList="D:\EVD\filelist.txt" \objectproperties=d:\EVD\objectproperties.txt&lt;/P&gt;
&lt;P&gt;This report assumes the vault.ini and user.ini files are in the current working directory. The target type is File which means reports will be dumped to a text file. there are two report types being run, filelist and objectproperties. Since the target type is file the output file for each report must be defined.&lt;/P&gt;
&lt;P&gt;Export to a database&lt;/P&gt;
&lt;P&gt;ExportVaultData \VaultFile="Vault.ini" \CredFile="user.ini" \Target=MSSQL \DBServerName=&amp;lt;DBServerName&amp;gt; \LogList&lt;/P&gt;
&lt;P&gt;report assumes the vault.ini and user.ini files are in the current working directory. The target type is MSSQL which then requires a DBServerName to be defined. only a loglist report is run (Note no output file path is specified as the target type is MSSQL).&lt;/P&gt;</description>
    <pubDate>Thu, 14 Oct 2021 16:51:54 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2021-10-14T16:51:54Z</dc:date>
    <item>
      <title>Export Vault Data Quick Start</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/export-vault-data-quick-start/ta-p/1429720</link>
      <description>&lt;P&gt;Export Vault data is a data dumping tool for customers looking to do more advanced reporting and analytics then the out of box reporting function can provide. The ExportVaultData utility exports data from the Vault to TXT or CSV files, from where they can be imported into third party applications or databases. Each report is saved in a different file. Most EVD implementations will require the customer to have skills in database management, reporting, and scripting. These skills are needed as EVD does not have filters beyond how many days old the dumped data is and will require the customer to collect, link up, and create reports of their own.&lt;/P&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;H2 id="ExportVaultData(EVD)-EVDmustberunwiththefollowingVaultandSafeauthorization:"&gt;EVD must be run with the following Vault and Safe authorization:&lt;/H2&gt;
&lt;P&gt;Vault authorizations:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;&amp;nbsp;Audit All&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Safe authorizations:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;View Audit – for the Owners List, Files List, User and Safe Activities, and Events List&lt;/LI&gt;&lt;LI&gt;Retrieve Files – on the System Safe for the System Log List&lt;/LI&gt;&lt;LI&gt;Update Files – on the System Safe for the System Log List&lt;/LI&gt;&lt;LI&gt;Access Safe without Confirmation&lt;/LI&gt;&lt;LI&gt;Confirm Safe Requests – for the Requests List and Confirmations List&lt;/LI&gt;&lt;/UL&gt;
&lt;H2 id="ExportVaultData(EVD)-ListofEVDoutputreports"&gt;List of EVD output reports&lt;/H2&gt;
&lt;TABLE&gt;&lt;COLGROUP&gt;&lt;COL /&gt;&lt;COL /&gt;&lt;/COLGROUP&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;FilesList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A files list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;LogList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A log activities report will be generated&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;OwnersList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;An owners list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;RequestsList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;
&lt;P&gt;An incoming requests list report. will be&lt;BR /&gt;			generated&lt;/P&gt;
&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;SafesList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A Safes list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;GroupsList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A groups list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;GroupMembersList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;
&lt;P&gt;A group members list report will be&lt;BR /&gt;			generated.&lt;/P&gt;
&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;UsersList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A users list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;LocationsList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A locations list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;ConfirmationsList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;
&lt;P&gt;A request confirmations list report will be&lt;BR /&gt;			generated.&lt;/P&gt;
&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;Italogfile&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A system log (ITAlog) file will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;EventsList&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;An events list report will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;ObjectProperties&lt;/TD&gt;&lt;TD colspan="1" rowspan="1"&gt;A file categories list will be generated.&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;
&lt;P&gt;One or more reports in any combination can be dumped in a single run of the EVD utility&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Example commands:&lt;/B&gt;&lt;/P&gt;
&lt;P&gt;Export to a local file&lt;/P&gt;
&lt;P&gt;ExportVaultData \VaultFile="Vault.ini" \CredFile="user.ini" \Target=File \fileList="D:\EVD\filelist.txt" \objectproperties=d:\EVD\objectproperties.txt&lt;/P&gt;
&lt;P&gt;This report assumes the vault.ini and user.ini files are in the current working directory. The target type is File which means reports will be dumped to a text file. there are two report types being run, filelist and objectproperties. Since the target type is file the output file for each report must be defined.&lt;/P&gt;
&lt;P&gt;Export to a database&lt;/P&gt;
&lt;P&gt;ExportVaultData \VaultFile="Vault.ini" \CredFile="user.ini" \Target=MSSQL \DBServerName=&amp;lt;DBServerName&amp;gt; \LogList&lt;/P&gt;
&lt;P&gt;report assumes the vault.ini and user.ini files are in the current working directory. The target type is MSSQL which then requires a DBServerName to be defined. only a loglist report is run (Note no output file path is specified as the target type is MSSQL).&lt;/P&gt;</description>
      <pubDate>Thu, 14 Oct 2021 16:51:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/export-vault-data-quick-start/ta-p/1429720</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-10-14T16:51:54Z</dc:date>
    </item>
  </channel>
</rss>

