Consider running StepSecurity on your repo

StepSecurity automatically generates a pull request that adds several hardening measures to your repo. Run it [here](https://app.stepsecurity.io/securerepo).

By default, the process will create one composite PR that makes multiple changes. I recommend running it several times to create separate PRs for each feature.

The changes it makes include:
1. dependabot - registers the repo with a GitHub service that subsequently submits PRs to upgrade to new releases of workflow actions. An example OpenEXR PR is [here](https://github.com/AcademySoftwareFoundation/openexr/pull/1807).
2. Set workflow permissions to read at the top level, and enable write permissions only on the steps that require it.
3. Pin workflow releases to explicit SHA values rather than named releases.
4. Adds a "Harden Runner" step that monitors CI jobs, although note that this does not work with the current release of the ASWF images, don't enable this for any workflow that uses the prebuilt images.

Start with the StepSecurity Secure Repo link and inspect the repository's GitHub Actions workflows. The hardening work is done when the requested changes are split into separate pull requests for Dependabot registration, permissions, and SHA pinning; do not enable Harden Runner for workflows using the prebuilt ASWF images.

Written by the indexing model from the issue text.