Skip to content

Security testing

We try to break into your systems, with your permission, so we find the holes before criminals do (penetration testing).

01 / Do I need this?

Do I need this?

  • Customers log in to your website or app
  • A customer or tender requires the solution to be tested
  • You're about to launch something new
  • It's been a long time since anyone outside checked your systems

02 / What we test

What we can test

Your website and online shop

Whether someone can log in as someone else, see other people's data or change what they shouldn't.

Your app

Whether the app stores things it shouldn't, and talks safely to the rest of the system.

Connections between systems

The links that move data between your app, website and other services (APIs).

What's visible from the internet

Old services, forgotten pages and doors left open.

Email and cloud services

Whether one stolen account could give access to everything else.

03 / How it works

How a test works

  1. 01

    We agree what to test

    What's included, what isn't, and when the test happens.

  2. 02

    You give written permission

    We sign an agreement and a confidentiality agreement before we start.

  3. 03

    We test

    If we find something serious, we tell you right away. You don't wait for the report.

  4. 04

    You get a summary

    What we found, how serious it is, and what to do first.

  5. 05

    We check again

    Once the holes are closed, we test again to confirm the fix works.

Principle

We never test without written permission from the owner of the system.

04 / What you get

What you get

  • A short summary in plain language, for management
  • A list of the holes we found, sorted by how serious they are
  • A meeting where we walk through the findings with whoever will fix them
  • A re-check afterwards to confirm the holes are closed
Example summaryFictional example

The report you get

  • 2Urgent
  • 4Should fix
  • 11OK
  • Urgent: Customers could see each other's orders

    Action: The developer closes the hole, we check afterwards.

  • Urgent: Old test accounts with weak passwords

    Action: Delete the accounts that aren't used.

  • Should fix: The website shows which software version it runs

    Action: Hide the version and keep the software updated.

Once the holes are closed, we test again.

You always get a short summary for management and a detailed part for whoever will fix things.

05 / Questions

Common questions

06 / For IT managers

For IT managers

Free check of your email

Could someone send email that looks like it came from you? We check how your domain is configured. You get the answer by email within a few minutes when you use an address on the domain you want checked. We only use publicly available information.

Free, with no obligation. We won't call to sell you anything.

Questions you may have

Will this be expensive?
You get a written price before we start. No surprises.
Are we too small?
We mainly work with businesses that don't have their own IT department.
Will it be technical and complicated?
You get a one-page summary in plain English.
Could you break something?
We never test without a written agreement, and agree in advance what is safe.

Next step

Tell us what you need

Tell us briefly what you need. We reply within one business day with a suggestion for how to proceed.

Related