#113Guide4 min

Build a secure delivery process

Define release responsibilities, use the project security gate and verify corrections after deployment.

Hackaiz team · updated 21/11/2026

Illustration: an agency discusses several client projects.
Illustration: an agency discusses several client projects. Illustrative photo, not a screenshot.

01Define what your release decision covers

A secure delivery process makes the decision to publish explicit. Before a release, identify the application version, the target environment, the systems you can examine and the person responsible for accepting remaining risk. Use Hackaiz findings as technical evidence in that decision, alongside your functional tests and deployment checks. An analysis is not a certification and cannot replace the product team’s knowledge of business rules.

Consider an application that has just gained invoice downloads. A practical release checklist asks who may retrieve an invoice, which repository implements the route and which verified host serves it. This is more useful than a rule that merely says “run a scanner”. Connect the systems relevant to that change, and record any unexamined component in your own release notes rather than treating it as implicitly covered.

02Run checks on the right authorized version

For a website or API, prove domain ownership before any analysis, using the DNS TXT record _hackaiz, the HTTPS file /.well-known/hackaiz-verification.txt, or the project AI creating that file. Connect the appropriate GitHub repository when code examination is part of the delivery. Access to a repository does not establish control of a deployed domain. If you are delivering for a third-party client, arrange the required client mandate as well as technical proof.

Review the selected checks and their scope before launching. Checks left unticked do not run and are not billed; work that is executed consumes credits. Keep the analysis tied to the release you intend to ship. A completed analysis from before a substantial permission change is not fresh evidence about that change. The release owner should check the analyzed environment and analysis date, and ensure that partial or interrupted work is not described as a finished review.

03Use the CI security gate as a release condition

In the project detail page, CI security gate provides Generate a new key and the command for querying the project gate. CI means the automated checks used in your delivery pipeline. Store the key as the pipeline secret HACKAIZ_CI_TOKEN. It is shown only when generated, and generating a replacement invalidates the old key. Keep it out of your repository and public logs.

The gate endpoint reads the latest project analysis; calling it does not launch a new analysis. An explicit pass returns HTTP 200. Open severe findings that meet the gate’s evidence threshold return 409. No analysis or an unfinished latest analysis returns an unknown verdict with HTTP 424, not permission to release. The response includes verdict information, counts and analysis identifiers or timing, not detailed vulnerability evidence. The gate does not itself establish that the analysis corresponds to your intended commit.

  1. 1Open the intended project and locate CI security gate.
  2. 2Select Generate a new key, copy it immediately and save it in the delivery system’s secret settings.
  3. 3Add the displayed request to a required release step so a failed request stops deployment; generating a key alone does not enforce anything.
  4. 4Check the latest analysis and the release context before relying on the gate’s response.

04Close the loop after human review

When a finding needs a code change, inspect the proposed correction and the affected behavior. Supported GitHub fixes are published as draft pull requests for human review and approval, never automatically merged. Keep a reviewer responsible for understanding the change and a release owner responsible for deciding when it can ship. For the invoice example, test both the legitimate download and the denial of access to an unauthorized user.

After your team merges and deploys an approved change, run a suitable authorized verification and keep the result with the release record. Do not label an issue resolved solely because a proposal exists or a branch was merged. Customer reports use Danger, To fix and To watch; explain remaining items in those terms and name the person who owns follow-up. Monitoring can support later observation, but is optional, applies only to connected systems and consumes credits for its actions. It is not a prerequisite for defining a responsible release process.

Frequently asked questions

Was this article helpful?

Related articles