Kubryx › Audit methodology
Audit methodology
This page describes how we work during an audit and what the report tells you. The aim is that you understand every finding and know what to do with it.
Areas checked
- Security: secret keys and credentials, authentication and authorisation, database access rules, CORS, security headers, dependencies, common OWASP risks.
- Functionality: navigation, forms and validation, ordering and payments (if present), e-mail workflows, key user scenarios.
- Technical quality: HTTP and JavaScript errors, broken links, display on different devices, performance, compatibility.
- SEO: indexing, metadata, canonical, language versions, sitemap, robots.txt, internal links, rendered content.
- AI discoverability: crawler access, clarity of content, consistent company identity, structured data.
- Privacy & accessibility: cookies and consent, personal data in forms, keyboard, contrast, alternative texts.
Automatic and manual checks
The free quick scan and the detailed scan report are automatic. They check publicly available pages and cannot judge application logic, permissions after login or whether a finding is actually exploitable. In a manual audit, a person verifies these on agreed pages and scenarios.
Classification of findings
| Severity | Meaning |
|---|---|
| Critical | Direct and serious impact, for example unauthorised access to sensitive data. Needs immediate action. |
| High | Significant risk or failure of a key process. Fix first. |
| Medium | Limited impact or conditions for abuse. Planned fix. |
| Low | Minor issue, hardening or quality improvement. |
| Info | Observation or recommendation without a demonstrated vulnerability. |
What every finding contains
- evidence (what we found and where),
- impact,
- steps to reproduce,
- a recommended fix.
The report distinguishes what was detected automatically, verified manually, unverified or potential, and what is out of scope.
Limits of the service
- We do not use "secure website" as a guarantee. An audit shows the state at the time of the check and within the agreed scope; the result can change after the site changes.
- A penetration test is not part of the audit and requires a separate written agreement on scope and authorisation.
- We only review websites and apps for which we have the owner's permission.
- An audit is not legal advice or a certification. For questions about personal data protection we recommend consulting a specialist.
Results of the automatic scan are indicative and valid at the time the scan ran. See AI website audit for the services and pricing for prices.
Last updated: 18. 11. 2026
More: AI website audit · Audit methodology · Pricing · Contact