The Policy Export feature allows administrators to download an offline copy of the workspace’s Policy. Whether you require a high-level summary for internal compliance, or a granular technical breakdown for a security audit, this tool ensures your policy configuration is accessible and portable outside the Fireblocks Console.
Export formats
You can choose between two formats based on your specific requirements:
- CSV (high-level summary): Optimized for general audits and human review. This file mirrors the Rule Management table in the Console, providing a summary of rules, actions (Allow, Deny, or 2-step approval), and conditions, including specialized parameters such as Amount over Time (e.g., "$5 in 2 hours").
- JSON (technical detail): Optimized for technical deep-dives or programmatic analysis. This format includes the full policy hierarchy and resolves all internal Object IDs (Vault accounts, User Groups, and Assets) into human-readable names.
How to export your policy
To initiate an export, follow these steps:
- In the Fireblocks Console, navigate to the Policy menu.
- Select the Export button located at the top of the Policy Overview screen.
- In the configuration drawer, select your desired Format (CSV or JSON).
- Select the specific Policy Types you wish to include in the export.
- Select Generate Export.
Note:
For security and performance reasons, Fireblocks generates an archive and sends a secure download link directly to your registered email address.
Filename convention
Exported files are automatically labeled using the following format: [Workspace-Name]_Policy-Export_[Type]_[Format]_[Date].zip
Security and permissions
User roles
The Policy Export feature is restricted to users with elevated permissions. The following roles can initiate an export:
- Owner/Admin
- Non-signing Admin
- Security Admin
- Security Auditor
Audit trail & versioning
- Logging: Every export request is logged in the Fireblocks Audit Trail. This log includes the identity of the requester, the export type, and the timestamp.
- Data Integrity: Both export formats include the specific policy version and generation date to ensure the data is mapped to a specific point in time.
Best practices
- For stakeholders: Use the CSV format for internal presentations or non-technical compliance reviews.
- For backups: Use the JSON format for full security posture backups or when importing data into third-party security information and event management (SIEM) tools.