Skip to main content

Overview

The Configuration Management API allows you to export your entire Falcon configuration as a portable archive and import it into another CID or restore it to the same CID. This is useful for:
  • Backup and disaster recovery - Regular configuration backups
  • Multi-CID deployments - Replicate configurations across environments
  • Configuration migration - Move policies and settings between test and production
  • Audit and compliance - Document configuration state at specific points in time
Configuration import/export operations can modify or create multiple policies, groups, and settings. Always test in a non-production environment first.

Export-FalconConfig

Create a ZIP archive containing Falcon configuration files including groups, policies, exclusions, rules, and scripts.

Syntax

Parameters

string[]
Selected items to export from your current CID. If not specified, all available items are exported.Valid values:
  • ContentPolicy
  • DeviceControlPolicy
  • FileVantagePolicy
  • FileVantageRuleGroup
  • FirewallGroup
  • FirewallLocation
  • FirewallPolicy
  • HostGroup
  • IoaExclusion
  • IoaGroup
  • Ioc
  • MlExclusion
  • PreventionPolicy
  • ResponsePolicy
  • Script
  • SensorUpdatePolicy
  • SvExclusion
Aliases: Items
switch
Overwrite an existing export file when present.

Examples

Export Process

The export process:
  1. Retrieves all selected items from your Falcon environment
  2. Identifies dependencies (e.g., Host Groups assigned to policies)
  3. Automatically includes dependent items in the export
  4. Saves each item type as a JSON file
  5. Creates a ZIP archive named FalconConfig_<timestamp>.zip
  6. Removes temporary JSON files

Returns

Archive file information including full path, file size, and last write time.
The export automatically includes dependencies. For example, exporting Prevention Policies will also export assigned Host Groups and IOA Rule Groups.

Import-FalconConfig

Import items from a FalconConfig archive into your Falcon environment.

Syntax

Parameters

string
required
Path to the FalconConfig archive (.zip file) to import.
string[]
Import only selected items from the archive. If not specified, all items in the archive are imported.Valid values: Same as Export-FalconConfig
switch
Assign existing host groups with identical names to imported items. Without this switch, imported policies will not be assigned to any groups.Aliases: Force
string[]
Modify default policies to match the import. Use All for all possible values or specify individual policy types.Valid values:
  • All
  • ContentPolicy
  • DeviceControlPolicy
  • PreventionPolicy
  • ResponsePolicy
  • SensorUpdatePolicy
string[]
Modify existing items to match the import. Use All for all possible values or specify individual item types.Valid values: Same as Export-FalconConfig (including All)

Examples

Import Behavior

  • Creates new items that don’t exist
  • Ignores items that already exist
  • Does not modify any existing items
  • Does not assign imported policies to host groups
  • Creates new items
  • Matches host groups by name
  • Assigns imported policies to matched host groups
  • Still does not modify existing items
  • Creates new items
  • Modifies specified default policies to match import
  • Useful for standardizing default policy settings
  • Creates new items
  • Modifies specified existing items to match import
  • Updates policies, groups, exclusions, etc.
  • Use with caution in production environments

Import Results

The import process generates a CSV file with detailed results:
Always review the import results CSV to verify all changes were applied correctly.

Common Workflows

Backup Configuration

Migrate Configuration Between CIDs

Clone Production to Test

Scheduled Backup

Selective Policy Update

Disaster Recovery


What Gets Exported

The export includes all user-created configurations:

Policies

  • Prevention Policies (with settings and IOA rule groups)
  • Response Policies (with settings)
  • Sensor Update Policies (with settings and schedules)
  • Device Control Policies (with classes and exceptions)
  • Firewall Policies (with settings and rule groups)
  • File Vantage Policies (with rule groups and exclusions)
  • Content Update Policies

Groups and Rules

  • Host Groups (with assignment rules)
  • IOA Rule Groups (with custom rules)
  • Firewall Groups (with rules)
  • File Vantage Rule Groups (with rules)

Exclusions and Indicators

  • IOA Exclusions
  • ML Exclusions
  • Sensor Visibility Exclusions
  • Indicators of Compromise (IOCs)

Other Items

  • Firewall Locations
  • RTR Scripts
Default policies and system-created items are exported but handled specially during import to prevent conflicts.

Permissions Required

Export Permissions

For each item type being exported, you need Read permission:
  • Hosts: Read (for Host Groups)
  • Prevention Policies: Read
  • Response Policies: Read
  • Sensor Update Policies: Read
  • Device Control Policies: Read
  • Firewall Management: Read
  • IOA Rules: Read
  • Custom IOA Rules: Read
  • IOC Management: Read
  • Real Time Response Admin: Read (for Scripts)
  • File Vantage: Read

Import Permissions

For each item type being imported, you need Read and Write permissions:
  • Hosts: Read, Write
  • Prevention Policies: Write
  • Response Policies: Write
  • Sensor Update Policies: Write
  • Device Control Policies: Write
  • Firewall Management: Write
  • IOA Rules: Write
  • Custom IOA Rules: Write
  • IOC Management: Write
  • Real Time Response Admin: Write
  • File Vantage: Write
In Flight Control environments, Sensor Download: Read permission is also required for CID comparison.

Best Practices

Regular Backups

Schedule automated backups before making major configuration changes. Keep backups for at least 6 months.

Test Before Production

Always test imports in a test environment before applying to production. Verify all changes in the results CSV.

Version Control

Store configuration archives in version control or secure backup storage with timestamps and change descriptions.

Document Changes

Maintain a log of configuration imports/exports, including purpose, date, and who performed the operation.

Troubleshooting

Export Issues

Ensure your API credentials have Read permission for all item types being exported. Use -Select to export only items you have access to.
Check if you have any user-created configurations. Default policies and system items may be filtered out. Use -Detailed to see what’s being exported.
Large environments may take several minutes. Try exporting specific item types separately using -Select.

Import Issues

Without -ModifyExisting, the import creates new items rather than updating existing ones. Use -ModifyExisting to update items with matching names.
Use the -AssignExisting switch to automatically assign imported policies to host groups with matching names.
Review the results CSV for failed items. Common causes include permission issues, naming conflicts, or missing dependencies.

  • Get-FalconConfig - View current configuration
  • Compare-FalconConfig - Compare configurations between CIDs
  • Request-FalconToken - Authenticate to switch between CIDs