#103Guide4 min
Set up application security governance
Define who authorizes checks, reviews findings and accepts the result of a change.
Hackaiz team · updated 21/11/2026

01Assign decisions before launching checks
Application security governance means deciding who may authorize an examination, who interprets its results and who can accept or reject the proposed response. Start with one application and write these responsibilities in an internal operating note. Hackaiz supplies observations and proposed corrections; it does not replace the person accountable for the application. Name a technical reviewer and a business decision-maker where those roles belong to different people.
Use Connect for authorized targets, then use Projects to keep the application context accessible. Before a website or API analysis, prove domain control with the _hackaiz DNS TXT record, an HTTPS file at /.well-known/hackaiz-verification.txt, or the project AI creating the file. Owning a repository does not by itself prove control of every website named in that repository. Your operating note should say who manages each authorization and when your team must review it.
- 1List the application and environments within your internal scope.
- 2Name the people authorized to request checks and review results.
- 3Record who approves changes and who accepts unresolved risk.
02Agree on how findings become decisions
Hold a review after an analysis rather than forwarding a severity count without context. Open Findings, inspect the evidence and confidence, and distinguish Danger, To fix and To watch. For example, a customer-facing access weakness and a low-impact configuration observation need different discussions. Consider what data is reachable, which user could act and whether the result concerns production or development. These questions help your reviewers prioritize; they are not a claim that Hackaiz knows every business consequence.
Keep a short decision record in your team’s existing tracking system: observation, accountable person, next action, target date and reason for any delay. These are suggested governance records, not assumed fields in the product. Establish an internal escalation path for urgent findings and a review date for accepted risks. A deliberate postponement should remain visible to the owner instead of disappearing because no code change was scheduled.
03Keep approval separate from implementation
Use Corrections to review available correction work. For eligible fixes, Hackaiz prepares a proposal for human approval and delivers a draft GitHub pull request. Your developer reviews the proposed changes, runs appropriate tests, merges and deploys them. There is no automatic merge. In your operating process, separate approval to prepare or publish a proposal from approval to put its code into production. The same person may hold both roles in a small team, but the decisions should still be explicit.
Define what the reviewer must check: intended behavior, access for legitimate users, effects on adjacent features and any manual deployment steps. Preserve the review link in your internal action record. Analyses and correction preparation use credits, so decide who can authorize that work before recurring requests accumulate. Unchecked checks are not run or billed. A budget decision to leave a check unselected must not later be presented as evidence that the underlying area was examined.
04Make follow-up a recurring management task
From a project, use the analysis history to return to earlier results and establish what was known at each review. After a change, inspect the actual new analysis and its coverage rather than assuming a lower finding count proves improvement. A different target, incomplete analysis or unrun check can change the count without reducing risk. Record which original observation you intended to verify and whether the new evidence addresses it.
Monitoring is optional and applies only to connected systems; it is not a substitute for naming someone to read results and act on them. Choose an internal review rhythm appropriate to releases and significant access changes. In each meeting, distinguish remaining technical findings, unexamined areas and decisions waiting on people. Hackaiz is neither an antivirus nor a firewall: governance is about making informed decisions from bounded evidence, not assuming the service blocks attacks or guarantees a secure application.
Frequently asked questions
Take the next step
Was this article helpful?