Request an audit

Guide / 22 November 2026

How to choose a cybersecurity company

Choose the provider that asks for written permission before any test, shows you a sample report, proves its findings and tells you the price before it starts. Below you will find the full checklist and the warning signs.

A good cybersecurity company works only within a written permission, delivers verified findings with evidence, explains in plain language what they mean for the business and gives you a clear order of fixes. The price is fixed before work begins, the retest is agreed up front, and the data it finds is handled and deleted under written rules. Be wary of guarantees, pressure and the promise that a single audit will make you "compliant".

1. Written permission and a clear scope before testing

A security test carried out without permission can be hard to tell apart from an attack. That is why the first serious document is an agreement that states exactly which systems may be tested, in what window and within what limits. If a provider starts testing without one, that is a reason to stop.

With us, after your request and a call about what is in scope, you receive a fixed quote and a permission form that states exactly what may be tested and when. We test only within that permission and window, at a limited rate, with no destructive tests, and real people are never locked out or tricked.

2. A sample report you can read

The report is the product you are buying. Ask to see one before you sign, even if it was written for an invented company. Check whether someone in management could follow it, not only your IT person. Ours is public: a complete sample report for an invented logistics company.

3. Proven findings, not just scanner output

An automated scanner lists possibilities and raises many false alarms. A useful audit says, for every finding, how it was verified and how certain the result is. In our reports every finding comes with its evidence and a confidence level: proven, confirmed, possible or not affected. Anything we could not check is listed as not checked, never as clean.

4. A plain-language summary and the technical detail

Management needs to know what the risk is and what decision has to be made. The IT team needs the exact steps. A good report gives both. We deliver a summary for decision makers, the technical detail for each finding, and the findings as a spreadsheet (CSV) and a SARIF file for your IT team's tools.

5. The order of fixes

A long list of problems with no priorities tends to stay unfixed. Ask for a plan that says what to fix first and how much effort each fix takes. Our report includes an ordered fix plan with the effort for each fix.

6. The retest

A retest confirms that the fixes actually work. Ask whether it is included, how many times and within what period. Our audit includes one retest of the findings within 30 days, followed by a new signed revision of the report.

7. A clear price before work begins

Ask for a fixed quote and a list of what is included and what is charged separately. Our starting prices are public: the security audit from €1,000 before VAT for a small company with one website and email, and monthly monitoring from €50 a month. Other services are quoted after a short call. The detail is in our guide on how much a cybersecurity audit costs.

8. What happens to the data found

During an audit a provider may see sensitive data: accounts, configurations, sometimes customer records. Ask where the evidence is kept, who can access it and when it is deleted. With us, evidence stays on our own machines in the EU, is used only for the report and is deleted 30 days after delivery. You keep the report for as long as you like. Leaked passwords never appear in a report, and we search for leaked accounts on our own machines, never on an outside service.

9. Independence: who makes the fixes

It helps to know whether the firm that finds the problems is also the one selling you the solution. That is not necessarily wrong, but it should be said openly. We do not resell products or licences. Your own team or IT provider makes the fixes, and if you would like our help with them, that is quoted separately.

10. Claims about the law and compliance

No audit, however good, makes you "compliant" with NIS2, GDPR or ISO 27001 on its own. An audit helps you meet part of the requirements and gives you technical evidence. In Romania, NIS2 brings steps with deadlines set by OUG 155/2024 and the DNSC orders, and ISO 27001 certification is carried out only by accredited certification bodies. If you do not yet know whether NIS2 applies to your company, start with the free NIS2 check. For the practical steps, see our NIS2 support and our ISO 27001 and DORA advice.

We do not give legal advice. For how the law applies to your company, speak to a lawyer.

11. Verifiable credentials and references

Ask any provider, including us, for evidence you can check yourself: the professional certifications of the people who will actually do the testing and, if you need an audit for NIS2 obligations, whether the provider is a DNSC-attested auditor. Check the answer at the source, on the issuer's or DNSC's website, not only on the provider's own site. References from other clients are only useful if you can actually speak to those clients.

12. What the provider does not do

A good provider tells you plainly what it does not do. For example, we do not provide incident response and we do not run a 24/7 monitoring centre. During an active attack, call your IT provider first. It is better to know this in advance than to find out on the day you need it.

Does it matter if the company is in Bucharest?

For an audit carried out from the internet, not very much: the checks are done remotely, so location matters less than the criteria above. We work with companies in Bucharest first, then across Romania, and we can carry out the starting audit for a company anywhere, because it is done over the internet.

Warning signs

  • Guarantees such as "100% secure" or "you will never be attacked again".
  • Pressure and fear: invented deadlines, alarming figures with no source, "you need to sign today".
  • Testing with no permission form or no written list of systems.
  • The promise that a single audit will make you legally compliant.
  • A report that is just a scanner export, with no verification and no order of fixes.
  • Refusal to show a sample report or to state the price before starting.
  • Vague answers about where data is kept and when it is deleted.

The short list

Before you choose, ask for written answers to these questions: What exactly will you test, and when? Can we see a sample report? How do you prove findings? What do we get for management, and what for the IT team? Is a retest included? What is the fixed price? Where do you keep our data, and when do you delete it? Who makes the fixes? Which verifiable certifications do the testers hold?

Last updated: 22 November 2026.

Next step

Request an audit

Find out what you expose, before someone else does.

Tell us who you are, confirm by email, and we will call you. Nothing is checked until you agree.

  1. You confirm by email, then we call you within two working days to understand your company and what should be checked.
  2. You get a fixed quote and a permission form that says exactly what we may test, and when.
  3. We do the work in the window you chose, and keep you posted.
  4. You get the report and a walkthrough call, then one retest of its findings within 30 days.

Only systems you own or may have checked / written permission first

Request an audit

No passwords or access details here. We ask for what we need after you sign the permission form.

After you send this, we email you a link to confirm it. We contact you only after you confirm.