#116Guide3 min
Create a recurring security follow-up offer
Define an agency service around authorized reviews, optional monitoring and human-led remediation.
Hackaiz team · updated 21/11/2026

01Sell a review process with a clear boundary
A recurring security offer should explain what your agency will do between deliveries: inspect authorized assets, interpret results, agree on corrections and return with evidence of the next review. Avoid selling an uninterrupted shield or a promise to stop every attack. Hackaiz is an analysis service, not an antivirus or a firewall, and a report describes what was examined at a particular time.
Draft the service scope in your own agreement. Identify the client application, the repositories and databases included, the person who can authorize access, and the person who will implement approved changes. Define what your agency does when an urgent finding appears outside its normal review hours. These are commitments you must organize yourself; the tool does not create a response team or a contractual response time for you.
03Offer monitoring only where it is available
For an eligible connected project, the interface can offer “Monitor this project”. Monitoring is optional and runs configured checks on authorized assets within the available credits. If the interface instead asks you to “Connect my system”, resolve that requirement first. Do not promise to monitor a pasted address or every client asset simply because you can name it in a service proposal.
Agree with the client how your team will read alerts and who can authorize follow-up work. Describe monitoring as an input to your review process, not as automatic attack blocking or proof that a person is watching continuously. Revisit the arrangement when a connection changes, access is revoked or credits are insufficient. Your recurring meeting schedule is a manual service arrangement, separate from the product’s monitoring behavior.
04Deliver a useful review, not a recurring pile of alerts
At each agreed review, open the relevant project reports and distinguish newly observed weaknesses from previously discussed items. Use Danger, To fix and To watch to explain the order of work. Compare the actual scope before claiming improvement: fewer findings after losing database access is not a demonstrated reduction in risk. Present unresolved evidence, blocked actions and the next decision in the client’s own operational language.
Prepare the client document through “Shareable report”, choosing “Executive” for management or “Developer” for the implementation team. Eligible fixes are draft GitHub pull requests approved by a human for publication and reviewed before merging; nothing is merged automatically. Agree who tests and deploys, then recheck the affected behavior. End the review with an owner and a next checkpoint in your service records, without claiming certification or guaranteed compliance.
Frequently asked questions
Take the next step
Was this article helpful?