RETEST & ATTESTATION
Close findings in weeks, not quarters.
The retest is not an upsell. Every engagement includes one: we re-run the affected tests against your fix within 14 days of you telling us it is deployed, then issue an attestation letter your auditors can file.
Fixes verified within 14 days. Attestation letter issued for auditors.
How the retest runs. Four steps, and the clock starts when you say the fix is live.
Report delivered
Findings land with reproduction steps, a business-impact rating and the remediation plan, plus a walkthrough session with the operators who found them.
You remediate
Your engineers work the remediation plan. Questions during the window go straight to the operator who raised the finding, not to a ticket queue.
Retest
We re-run the affected tests against your fix within 14 days of you calling it done, and record the result for each finding in the retest log.
Attestation
A signed letter stating what was tested, over what dates, what was found and which findings were verified as remediated.
What the letter says. Written to be filed, not to be admired.
The scope that was tested and the dates it was tested over
The findings raised, with their severity
Which findings were verified as remediated at retest
The standards the engagement was aligned to
Issued in English and Bahasa Indonesia, structured for ISO 27001, PCI-DSS and OJK reviewers.
Four service lines. One methodology behind all of them.
NEXT STEP
Tell us what needs testing. An operator reads it first.
A 30-minute scoping call with the operator who would run the engagement. A written scope, timeline and fee follow within 2 working days of the scoping call.