#102Guide3 min
Use Hackaiz in an ISO 27001 effort
Prepare bounded technical evidence for your information security management work.
Hackaiz team · updated 21/11/2026

01Position technical checks within the wider effort
ISO 27001 work concerns how an organization manages information security, not just whether one application has visible weaknesses. Use Hackaiz as a source of technical observations for the systems you are authorized to examine. Keep the organization’s scope, risk decisions, responsibilities and operating procedures in its own management documentation. A report is an input to that work, not a replacement for an assessment by the people responsible for it.
Before collecting evidence, write down the application, environment, business use and review period you intend to cover. A repository and its deployed website are different evidence sources. Testing one does not establish the condition of the other. For a website or API, prove domain ownership before any analysis through the _hackaiz DNS TXT record, the HTTPS file /.well-known/hackaiz-verification.txt, or the project AI creating that file. Authorization is part of the evidence context.
02Read control coverage without inflating it
The report’s Coverage by standard area presents a technical alignment view. Expand the relevant standard and read individual control states rather than turning the display into an overall pass. The interface distinguishes Issue detected: see evidence, Examined, nothing found, Partly examined and Not examined by this analysis. Each state describes the evidence available from this analysis, not the condition of every system or organizational practice.
Other states deliberately preserve human responsibility: Your answers or documents are expected, Must be proven by a person and Declared by you: in place (not proven). A declaration records what someone says is implemented; it does not become technical proof because it appears beside automated findings. Download (JSON) preserves control identifiers, states and available finding references. Keep the accompanying limits when placing this file in your evidence collection; do not rewrite unknown controls as successful checks.
- 1Open the completed analysis and locate Coverage by standard.
- 2Expand the relevant standard and inspect the control states.
- 3Use Download (JSON) and retain the analysis reference with the export.
03Build a review package around a specific risk
Choose a concrete issue, such as a potentially exposed application secret, and assemble the finding, available location, business consequence and proposed treatment. Severity appears as Danger, To fix or To watch. Record the accountable reviewer and treatment deadline in your own risk or action register. Explain whether the observation concerns source code, the deployed service or another connected target so the reviewer can judge its relevance to the scope you defined.
For eligible fixes, link the approved proposal to its draft GitHub pull request. A human authorizes publication and your team reviews, tests, merges and deploys the changes; there is no automatic merge. Add the deployment reference and subsequent verification result to the package. This makes the evidence useful for a discussion about how a specific risk was treated, without implying that a code change establishes the effectiveness of unrelated organizational controls.
04Retain missing evidence as a visible gap
Document separately the topics that require interviews, documents or organizational decisions. Examples for your own evidence plan include approval responsibilities, staff guidance and the review of access rights. Do not claim Hackaiz verified these practices merely because an application analysis finished. If a control is marked as needing human proof, name the person who will supply that material in your internal plan rather than replacing the state with an unsupported conclusion.
Budget follow-up work deliberately: analyses and fix preparation consume credits, and unchecked checks are neither run nor billed. A partial analysis requires a narrower evidence statement, not a broader inference. Keep dates and target references when comparing reviews over time. Hackaiz supplies technical evidence and limitations; it does not certify an organization or establish ISO 27001 conformity. Decisions about the management system remain with your organization and its qualified reviewers.
Frequently asked questions
Take the next step
Was this article helpful?