All servicesApplication / infrastructure pentest
Find out whether your defences hold, before someone else does.
We attack your systems, inside a scope set in writing, to qualify your defences. Every flaw we find comes with its proof of concept and the recommended fix.
CAD $3,500–5,000/day
A written scope
The scope and the rules of engagement are set in writing before the first test.
Proof, not opinion
Every flaw is delivered with its proof of concept.
The fix comes with it
Every flaw comes with the recommended fix, so your techs know what to do.
Qualify, not destroy
We test to learn whether it holds, not to break things or to alarm you.
On paper, everything is in place. Nobody has ever tried to get in.
You have a firewall, passwords, an application your clients use. Your provider says it is secure, and so does your developer. But until someone tries to get in the way an attacker would, that is an assumption, not a finding.
| No testing | An automated scan alone | With Cerbère | |
|---|---|---|---|
| What gets checked | Nothing: you trust the intended configuration. | The known vulnerabilities the tool can recognize. | What a person can actually exploit inside the agreed scope. |
| Evidence | None. | A list of alerts, with the false ones still to sort out. | A proof of concept for every flaw found. |
| Ground rules | Not applicable. | Often launched with no written rules. | Scope and rules of engagement set in writing before the first test. |
| What you receive | Nothing to hand a client or an insurer. | A tool-generated report. | A detailed report, written to be read and acted on. |
| What happens next | You learn about the flaw the day someone uses it. | Your team guesses what to fix first. | A recommended fix for every flaw. |
An automated scan has its place: it prepares the test. It does not replace someone actually trying to get in.
In 2023, about 1 in 6 (16%) Canadian businesses were impacted by cyber security incidents.
In 2023, over 1 in 8 (13%) impacted businesses reported experiencing ransomware attacks, up from 11% in 2021.
What changes
From an assumption to a finding
You know what gives way
The flaws that can really be exploited inside the scope are named, one by one.
You can show it
The proof of concept lets your developer or provider see the flaw, not just take it on faith.
You know what to fix
A recommended fix comes with every flaw. Your techs start from there.
You stay in control
Nothing is tested outside the scope you approved in writing.
Who it is for
A business that runs an application
Client portal, online store, in-house software: client data flows through code that no outsider has ever put to the test.
An organization asked for proof
A client, an insurer or a funder requires a penetration test. You need a written report from someone who did not build the system.
This is for you if
- You have a specific application or infrastructure to put to the test.
- A client or an insurer is asking for a penetration test.
- You have techs or a developer who can apply the fixes.
- You want proof, not a list of alerts.
Probably not for you if
- You have never had an assessment: the initial audit is a better starting point.
- You want a statement that your systems are flawless: no test can give you that.
- You want systems tested that are not yours, without their owner's written consent.
What is included
What is included
Written scope
What is tested and what is not, in black and white.
Rules of engagement
What is allowed during the test, set in writing before the first attempt.
Penetration testing
We attack the targeted application or infrastructure to qualify its defences.
Proofs of concept
Every flaw found is demonstrated.
Recommended fixes
For each flaw, what needs to change.
Detailed report
A written document you can hand to your techs and to whoever asks for it.
How it goes
How it works
-
Step 01
Scope
You describe what you want tested. The scope, the rules of engagement and the price are set in writing.
-
Step 02
Test
We attack the agreed scope, and nothing else.
-
Step 03
Trace
Every flaw is documented with its proof of concept.
-
Step 04
Report
You receive the detailed report and the recommended fixes.
Pricing
Pricing
-
Application / infrastructure pentest
CAD $3,500–5,000/day
depending on complexity, fixed price on quote.
- Scope and rules of engagement set in writing
- Penetration testing on the agreed scope
- Proof of concept for every flaw found
- Recommended fix for every flaw
- Detailed report
The price covers scoping, testing and the report. Applying the fixes is left to your techs, or handled as a separate engagement.
What we do. What we don't.
We do
- Put everything in writing: scope, rules of engagement, price, report.
- Test only what you approved.
- Hand you every proof and every recommended fix.
- Tell you what held, too.
We don't
- Test outside the agreed scope.
- Test to destroy.
- Promise that a test finds every flaw.
- Inflate findings to sell the next engagement.
Frequently asked questions
What is the difference between a pentest and a vulnerability scan?
A scan is an automated tool that flags known vulnerabilities. A pentest is done by a person who tries to exploit them, as an attacker would, and brings back proof. The scan prepares the test; it does not replace it.
Could the test break our systems?
The goal is to qualify your defences, not to destroy. The rules of engagement, set in writing before the first test, say what is allowed and what is not. No test is free of risk, which is why the ground rules are written first.
How many days does it take?
It depends on what is tested. The rate is CAD $3,500–5,000/day depending on complexity, and a fixed price is available on quote. The number of days is set in writing at the scoping stage, before work starts.
Do we need an audit first?
Not necessarily. If you have never had an assessment, the initial audit costs less and often shows what to fix before paying for a test. If you have a specific application to put to the test, the pentest is the right tool.
Can you test a service hosted by a third party?
Only with the required authorizations. The written scope states who owns each system, and nothing is tested without consent from whoever has the right to give it.
What is in the report?
For each flaw found: its description, its proof of concept and the recommended fix. The report is written so your techs can act on it.
Do you fix the flaws?
The pentest delivers the findings and the recommended fixes. Your techs can apply them, or you can hand us the next step as a separate engagement.
Does a clean pentest mean we are secure?
No. A test says what was found inside a scope, at a point in time. It reduces a risk; it does not remove it.
How do we start?
Describe in a few words what you want put to the test in the contact form. The reply comes in writing within 24 business hours.
We test to qualify, not to alarm.
Describe the application or infrastructure you want put to the test. You get a written reply within 24 business hours.
Written reply within 24 business hours. No video calls, no booking calendar.