> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/hosting/securing/security-audit.md).

# Run security audits on Duaer

Run a security audit on your Duaer instance.
## How do you run a security audit in Duaer?

You can run a security audit on your Duaer instance to detect common security issues. The report is read-only: it does not edit the canvas, rotate keys, or print [external secret](/external-secrets.md) values.

- CLI: run the audit subcommand in the install directory (check this version’s `--help`).
- Public API: make a `POST` call to `/audit`. Authenticate as the instance owner. Refer to [authentication](/api/authentication.md).
- You can also generate an audit from a workflow with the instance node when your version exposes that operation.

## What is in the security audit report?

The audit typically covers unused or long-idle credentials, expressions in SQL Execute Query fields, nodes that touch the file system, and loose instance settings.

An item in the report means that configuration is worth checking, not that someone already got in. Change that configuration, then run the audit again to confirm the change is still in place.
## Questions

### Does a Duaer security audit change workflows?

No. A Duaer security audit is read-only. Run it from the CLI or the public API (owner auth). It lists credentials, nodes, and instance settings worth checking. It does not edit nodes or reveal secret values.

