> For the complete documentation index, see [llms.txt](https://klouddb.gitbook.io/klouddb_shield/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klouddb.gitbook.io/klouddb_shield/pg_backup_compliance-extension.md).

# Pg\_backup\_compliance Extension

**Extension URL** 

<https://github.com/klouddb/pg_backup_compliance>

**Why Do You Need This Extension for Backup Compliance?**

1. In security and compliance frameworks such as ISO 27001, NIST, and HIPAA, organizations must maintain tamper-evident evidence proving that backups are being performed as required. This extension provides auditable records that serve as backup compliance proof.
2. While it is possible to track pgBackRest, pg\_basebackup, and pg\_dump individually, there is no easy way to automatically and consistently track all three utilities together.
3. One of the major security risks is unauthorized database exports using pg\_dump. Tracking all backup and dump activity is critical for audits and for detecting potential data exfiltration.
4. This extension includes built-in views that generate monthly and quarterly compliance reports, making audits significantly easier.
5. Although backup activity can be inferred from logs, that evidence may be rotated or lost over time. This extension stores the evidence centrally and persistently.
6. With this extension, you can quickly identify successful and failed backups across all supported tools for any given time period