Keeper Commander compliance reporting commands
Compliance reports let account administrators adhere to regulations by providing on-demand visibility to access permissions on records and credentials across the enterprise.
Using Commander, compliance reports can be scheduled and automated, and results can be exported to a CSV file or JSON.
For more information about Compliance Reports, see the Compliance Reports documentation:
compliance-reportcommand allows you to run reports just as you would in the Keeper Admin Console. See record permissions by node, user and title, filter by owned or shared records and output results to a file.
compliance-reportcommand relies on a cache in order to improve performance across multiple report queries.
This means that the first call to
compliance-reportmay take several minutes as the system pulls in the required data.
During this time, Commander will display messaging explaining the current step.
Additionally, a manual rebuild of the cache can be performed with the
-rflag. Do this to see recent changes in the compliance data.
Removing the Cache
The compliance report cache can be removed manually with the
--no-cacheflag. When run, this completely removes all cached compliance report information from your machine.
Alternatively, you can delete the cache file locally on disk from the location where you ran Commander. Delete the file called
sox_<ID>.dbwhich contains the encrypted compliance data.
The compliance report can be filtered by Node, User, Job Title and if the record is shared.
--username [USER EMAIL]or
-u [USER EMAIL]
Filters the record results to only records that exist in the Keeper Vault of the given username
The filter flags can be used together to create advanced reports
compliance-report --node "Chicago" --job-title "Managers" --shared
This example shows a report of records that have been shared from Vaults owned by Managers in the Chicago Node.
The same filter can also be used multiple times
Filters the record results to only records that exist in Keeper Vaults in the given Node
Like many Commander reports, the compliance report results can be saved to a file. To do this use the
--output [FILE PATH]
Tells Commander to write results to a file at the given location. If no file exists it will be created.
--format [csv, json, table]
To save compliance report results as a CSV file viewable in Excel, use the following flags:
The results will be saved as a csv formatted file at the given location
To save compliance report results as a CSV file to use in code or scripting, use the following flags:
The results will be saved as a json formatted file at the given location
Shared folders can be shared to Keeper Teams as well as individuals. The compliance report can display a report of the access that each team has to these shared folders.
To run the Compliance Team Report, use the following command in Commander:
The report shows each team that has access to a shared folder, and what access it has to that shared folder.
My Vault> compliance team-report
Team Name Shared Folder Name Shared Folder UID Permissions
----------- -------------------- ---------------------- -------------
Engineering Devops Secrets 8-2gk4cUdde3es567NwpCA read-only
Marketting Website Logins 5v3lduLYf81CED5N4dOKEA edit, share