All servicesHardening
Audit report gathering dust? We apply the fixes and write down every change.
We harden your systems after diagnosis: patches, settings, access. The deliverable describes every change, so your team can redo it without us.
On quote
After diagnosis
We fix what your diagnosis ranked first, not a generic checklist.
Every change written
What was changed, where, why, and how to roll it back.
Repeatable without us
Your team can redo the work on a new workstation or a new server.
Your access stays yours
Administrator accounts remain yours from start to finish.
You know what is wrong. Nobody has time to fix it.
An audit, an insurer or an incident left you with a list: default passwords, overdue updates, too many administrator accounts. The list is clear. But whoever looks after your IT is putting out fires all week, and every setting they touch feels like an outage waiting to happen.
| Leaving the defaults | Doing it yourself | With Cerbère | |
|---|---|---|---|
| Administrator passwords | Sometimes still the manufacturer's | Changed when someone remembers | Changed, and handed to you alone |
| Updates | Whenever a reminder pops up | When time allows | Automatic updates turned on wherever possible, exceptions noted in writing |
| Order of work | None | Easiest first | Most serious first, following the diagnosis |
| If a change goes wrong | Not applicable: nothing changes, known flaws stay open | A rollback improvised on the spot | A rollback written before the change, done at an agreed time |
| Record | None | In the memory of whoever did it | A written deliverable: each change, its reason, how to redo it |
| Dependence | Not applicable | On one person | None: your team can redo the work without us |
A diagnosis with no fixes behind it leaves your exposure exactly where it was. Hardening is the step that reduces it.
In 2023, about 1 in 6 (16%) Canadian businesses were impacted by cyber security incidents.
Canadian businesses' spending to recover from incidents doubled, from approximately $600 million in 2021 to $1.2 billion in 2023.
In its baseline controls for organizations with fewer than 500 employees, the Canadian Centre for Cyber Security recommends enabling automatic patching and changing all administrator passwords.
What changes
Four work streams, in the order of the diagnosis
Access and accounts
As the diagnosis calls for: default passwords changed, unused accounts closed, administrator rights cut back to those who need them, multi-factor authentication turned on.
Patches
Systems and software brought up to date, automatic updates enabled wherever they can be.
Settings
Unneeded services switched off, unsafe defaults corrected on the workstations, servers and network equipment in scope.
Written record
Every change is described in the deliverable, with how to redo it and how to undo it.
Who it is for
A small business holding an audit report
You received a list of findings, from Cerbère or someone else. Your technical team does not have the hours to work through it.
A non-profit or professional with no IT team
Someone set everything up years ago. You hold personal information, and the settings have never been reviewed.
This is for you if
- You have a diagnosis and findings waiting to be dealt with.
- An insurer or a client is asking you to fix specific points.
- You want your team to be able to redo the work without calling anyone.
- You insist on keeping your administrator accounts.
Probably not for you if
- You have no diagnosis yet: start with the initial security audit.
- You want someone to run your IT day to day. This engagement has a beginning and an end.
- You want a compliance certificate. The deliverable describes changes; it is not a certificate.
What is included
What is included
Reading the diagnosis
We read your report, from Cerbère or anyone else, and tell you whether it is enough to start.
Written work plan
The planned changes, in order, each with its rollback. You approve it before we touch anything.
Applying the fixes
The updates and patches your diagnosis ranked first.
Security settings
Access, accounts, services and parameters, on the systems in scope.
Check after each change
After every change we check that your services respond and that the setting is in place.
Written, self-reproducible deliverable
The deliverable describes every change, so your team can redo it without us.
Access handed back
When the engagement ends, you close the access opened for the work. We keep nothing.
How it goes
How it goes
-
Step 01
You write
Send your diagnosis or describe what was flagged. Written reply within 24 business hours.
-
Step 02
We scope
Scope, work plan and quote, in writing. No change before you agree.
-
Step 03
We apply
Changes follow the plan in order, the delicate ones at a time agreed with you.
-
Step 04
We hand over
The written deliverable, access closed, and your questions answered in writing.
Pricing
Price
-
Hardening
On quote
depending on scope.
- Written work plan and quote before any change
- Top-of-list fixes and settings applied
- A check after every change
- A written deliverable your team can redo
The quote covers Cerbère's work. If a fix requires a third-party licence or hardware, it is at the vendor's price, with no hidden margin.
What we do. What we don't.
We do
- Put everything in writing: plan, quote, every change.
- Leave your administrator accounts in your hands.
- Write the rollback before each change.
- Tell you what can wait.
We don't
- Change a setting that is not in the plan.
- Keep any access after the engagement.
- Tie you into a contract you cannot leave.
- Promise that nothing can happen any more.
Frequently asked questions
Do we need an audit first?
You need a diagnosis, because that is what says what to fix first. It can come from Cerbère's initial security audit or from a report you already have: we read it and tell you whether it is enough.
Could this cause an outage?
Every change carries some risk, and we treat it that way: each change has a written rollback, the delicate ones happen at a time agreed with you, and we check afterwards that your services respond.
What does 'self-reproducible' mean?
The deliverable describes each change precisely enough for your team to redo it alone, for example on a new workstation or a new server.
Who keeps the administrator passwords?
You do. We work with the access you open for the length of the engagement, and you close it at the end.
Can our own technician do part of the work?
Yes, and the deliverable is written for that. If you prefer, we apply only the most delicate changes and your team does the rest, plan in hand.
Do you work remotely?
Yes, everything is done remotely and in writing. If a change needs someone physically on site, we prepare it in writing for that person.
Does this make us compliant with Quebec's Law 25?
Hardening is neither legal advice nor a certificate. The law makes you responsible for protecting the personal information you hold. Better-configured systems contribute to that, and the written deliverable shows what was done.
After hardening, are we safe?
No. We close the known flaws your diagnosis ranked first, which reduces your exposure. New vulnerabilities keep being published, so watching and updating remain necessary.
What does it cost?
On quote, depending on scope. You get the quote in writing, with the work plan, before any change.
Send us your list of findings.
An audit report, a letter from an insurer, or your own notes. Written reply within 24 business hours: what we would fix first, and what can wait.
Written reply within 24 business hours. No video calls, no booking calendar.