Security & audits

Web security
audit.

We look at your website, e-shop or application through an attacker’s eyes before someone else does. You get a list of weaknesses ordered by severity and guidance on fixing them.

Free consultation

What you get

  1. Penetration test

    By hand and with tools we try what an attacker tries: sign-in, permissions, forms, file uploads, APIs.

  2. Code review

    We read the source code and look for flaws that are not visible from outside: input handling, password storage, access to other users’ data.

  3. Dependency audit

    We check the libraries and plugins the site is built on. An outdated dependency with a known flaw is one of the most common ways in.

  4. A report you can read

    Every finding has a description, severity, steps to verify it and a recommended fix. A summary for management, detail for developers.

  5. Retest after fixes

    After the fixes we verify the findings again, so you know they are really closed.

  6. Fixes from us

    If you have no developer of your own, we fix the issues we find. Laravel and PHP projects are our home ground.

Tested by someone
who does it for a living.

  • One of us has worked as a penetration tester for two years and holds the PJPT certification (TCM Security).
  • We build websites and applications ourselves, so we know where developers most often slip and how to fix it.
  • We test only with the owner’s written consent and within an agreed scope and time.
  • Findings stay between us and you.
  • The output is not a dump from an automated tool but verified findings with recommendations.
  • Every project of our own goes through the same check before launch.

FAQ

How much does a web security audit cost?

It depends on the scope: a company site with a form is different from an e-shop or an application with user accounts. We agree the scope and quote after an initial consultation.

Will the test put the site at risk?

We plan the test so it does not limit normal operation. Risky checks are done by agreement outside peak hours or on a test copy.

What do you need for an audit?

Written consent from the site owner, the scope of the test and a contact person available during the test. For a code review, access to the repository.

Someone else built our site. Is that a problem?

No, quite the opposite. An independent view finds what the author missed. You pass the report to your supplier, or we do the fixes.

Contact

Write to us.
We reply within 24 hours.

The first consultation is free and without obligation. Tell us about your project and we will get back to you with a proposal for next steps.

[email protected]

We use the details from this form only to handle your enquiry. We do not pass them on for advertising and do not send marketing messages to them. Details and your rights are in our privacy policy.

Or directly at [email protected]