Service
We find weaknesses before they are exploited
We test websites and applications the way an attacker would — but only with written permission and within the agreed scope.
What we test
We only test systems for which the owner has given written permission.
Websites and web systems
Checking forms, login, roles, permissions, common vulnerabilities, and configurations.
Mobile and other applications
Review of the application and the API it communicates with, according to the agreed scope.
Risk distribution
Each finding is described with its potential impact and priority so you know what to fix first.
What you get
- Written agreement on scope, deadlines, and points of contact
- Testing within agreed boundaries
- Report with findings, risk, and remediation recommendations
- Re-verification after corrections
We do not begin testing without signed permission. Systems that are not yours or for which you lack the authority to provide consent are out of scope.
How the process works
- Written inquiry
A brief description of the system and the purpose of the test.
- Permission and scope
Written consent from the owner and agreed-upon scope.
- Testing
Controlled checks.
- Report
Findings and recommendations in writing.
- Retesting
We confirm the corrections.
Frequently asked questions
Could you disrupt system operations?
We plan tests to minimize risk and specify timing and limitations in advance.
Do you also handle the corrections?
The report explains how to fix the issue. Corrections can be arranged separately.
Do you test third-party websites?
No. Only client systems or those for which there is written permission from the owner.
Other services
Do you want to check your system?
Describe your system and receive a proposal with a clear scope of testing.