05 / Security research & engineering
Security needs evidence.
Not promises.
Web engineering informed by hands-on security research. We trace relevant controls, document evidence and explain what remains outside the review.
Define a security review- 01
Scope & authorization
Agree assets, test identities, demonstration data, traffic limits and written authorization before testing.
- 02
Review & assessment
Review authentication, access control, input handling and configuration using OWASP categories relevant to the scoped features.
- 03
Remediation & retest
Findings describe root cause, evidence, impact and recommended fixes. Retesting checks the same controls after remediation.
- 04
Technical handover
Reports distinguish validated findings, hypotheses, testing limits and residual risk. No website is claimed to be 100% secure.
CASE STUDY / 10 OCTOBER 2026
techindo.com
Authorized, time-bounded external assessment of the exact origin. The archive contains 78 first-party HTTP requests and independently reviewed evidence.
Read the full audit report (PDF) ↗
AUDIT RESULT
The sample validated no impactful security finding or exploit chain. A search input formed a new HTML attribute, but the offline browser check did not execute the sentinel. Anonymous API requests were rejected, tested logins did not create an admin session, and search comparisons did not demonstrate SQL injection.
Backend source, comparative test accounts, and owner-side database, queue, and mail observations were unavailable. The result applies to the tested sample, not the whole site.
EVIDENCE STATUS
The archive directly shows a client-side configuration with a public anonymous role. Audit notes describe sensitive API reads, but raw admin and data API responses are absent. Access-control impact and present-day exposure cannot be independently confirmed from this folder alone.