Documentation / Policy and Compliance
Compliance
Compliance
A compliance file is a JSON document listing the rules — including Rego policies — that Prancer applies to validate cloud resources. It references a Snapshot so each rule has a concrete target. Read more in the Tests definition reference.
Before you start
- A collection containing a Snapshot you want to validate.
- A compliance JSON file authored locally, or one you'll edit in place after upload.
View the compliance files in a collection
Open the collection drop-down and choose All Files. Under the Compliance Test header you'll see every compliance file currently in the collection.


1. Upload a compliance file
From Collection Management, drag-and-drop one or more JSON files, or click Click here to browse.

Warning: Uploading a file with the same name as an existing compliance file overwrites it. Keep a copy locally if you need to roll back.
2. Edit a compliance file
Click the file name to open it in the editor. Make changes and click Keep Changes to save.

3. Copy or download a compliance file
Open the file dialog and use the Copy to clipboard or Download icons.

Tip: Keep your compliance files in Git and upload them via the PAC CLI for repeatable, reviewable changes.
Next steps
- Compliance Run — execute the compliance against your snapshot.
- Master Compliance — define rules at the resource-type level.
- Policy Management — search and edit individual Rego policies.