Dawid Balwierz — security testing from Etten-Leur.
I test web applications, APIs and mobile apps for the people who own them, and I write results down so that both the owner and the developer know exactly what to do next. Dutch, English and Polish, on site in the Netherlands or remotely across the EU.
How I got here
My route into this work was coordinated vulnerability disclosure: reporting security problems to companies through bug bounty and disclosure programmes, and learning how much of the real work happens after something is found — in the quality of the write-up, the reproduction steps and the fix advice.
That shaped how I work. A vulnerability that is reported vaguely, without evidence or with exaggerated severity, is not a finding — it is an argument. So I test with the smallest possible proof, document every step with a timestamp and a hash, and rate severity against the impact on your business rather than against a scanner's score.
The other half of the work is follow-through. Most systems I am asked to look at are not attacked by novel techniques; they are attacked through a hardened-looking surface with a secret in a public file, an identifier that is trusted instead of checked, or a component nobody updated. Those are fixable, and they are worth automating so they stay fixed.
Practical details
- Based in
- Etten-Leur, 4871 CL, the Netherlands
- Working area
- On site across NL, remote across the EU and for clients in Poland
- Services
- Penetration testing, AI-assisted test automation, code & configuration review, and website building for ZZP, uitzendbureau and small businesses
- Website delivery
- Business, ZZP and uitzendbureau sites built and live within a few days of the order; domain, hosting, HTTPS, forms and privacy page included
- Reporting languages
- English, Dutch, Polish
- Response time
- Enquiries answered within one working day
- Availability
- Fixed-scope projects and retainers; urgent pre-launch reviews by arrangement
How I work
Evidence over opinion
Every finding carries a reproduction path, request and response evidence, and a confidence tag. If I cannot reproduce it, it does not go in the report as a fact — it goes in as something that needs verification, and it says so.
Plain language for the owner
You should not need a security background to decide what to fix first. The summary explains the risk in business terms and puts the items in priority order; the technical appendix is for whoever writes the code.
Authorisation before everything
Written scope, signed, naming the assets, the window, the source IP and the person who can stop the test. No signature, no packets — no exceptions, however small the job.
Restraint
No denial-of-service, no persistence, nothing left behind, no customer data read or copied. Where a finding could be pushed much further, I stop at proof of impact and document the boundary.
Third parties stay untouched
Payment providers, cloud platforms, chat widget vendors, hosting and app stores are outside scope unless they have given their own written permission. Findings that belong to them are written up so you can forward them.
Fix verification included
The engagement is not finished at the report. It is finished when the fixes have been retested and you have a written statement of what is closed and what is still open.
What I refuse to do
- Test a system without written authorisation from someone who owns or controls it.
- Use credentials found in public code, leaks or backups as a way in — they get reported, not exercised.
- Read, export or modify real customer data beyond the smallest proof a finding needs.
- Inflate severity to make a report look more impressive, or hide the parts of a system that were not tested.
- Run load, stress or denial-of-service testing without a separate written agreement.
- Promise a "clean bill of health". A test result is evidence about a period of time and a defined scope — nothing more.
Background
Hands-on vulnerability research and coordinated disclosure through public bug bounty and disclosure programmes (HackerOne, Intigriti), alongside client work: web, API and mobile application testing, configuration and hardening reviews, and security automation.
The other side of the same craft is building: websites for ZZP'ers, uitzendbureau and employment agencies and small companies in the Netherlands and Poland — a site is only as good as it is safe and maintainable, so they ship hardened and simple by design.
For recent references, programme profiles or a specific technical question, e-mail me — I will answer directly rather than publish claims I cannot back with evidence.
Working on something that needs testing — or building?
For a test: send the assets, the environment and your deadline. For a website: say what your business does and what pages you need, and you get the day it goes live — usually within a few days of the order. If neither is the right answer for your situation, I will say so and suggest what is.