Add protection to a project
- Who it is for
- A new or growing project that needs sensible protection from the start.
- What you receive
- A short plan, then the protections put in place and explained.
CS-S03Quote on request
Protection you can explain to anyone.
We add protection, strengthen what already exists and check whole systems. Always with your written permission.
Pricing is agreed after a conversation.
01 Three ways to work
Choose where to start.
-
-
Modify existing protection
- Who it is for
- A system that already has some protection you are not sure about.
- What you receive
- A review of what is there, a list of changes and the changes made.
-
Full security audit
- Who it is for
- An owner who wants a careful look at a whole system.
- What you receive
- A written report of what we checked and found, with what to fix first.
02 How an engagement works
Permission first, then work.
- 01
Discuss
We listen to what you run and what worries you, and agree what is in scope.
- 02
Authorise in writing
You confirm in writing that you own the system or may allow testing. Nothing is tested before that.
- 03
Test or build
We make the agreed changes or run the agreed checks, inside the scope and nowhere else.
- 04
Report
You receive a report in plain words: what we checked, what we found and what to do first.
- 05
Follow up
We answer your questions, and we check again after the fixes.
03 What we cover
Six areas we look at.
- 01
Web applications
Sites and apps that your customers or your staff sign in to.
- 02
Accounts and access
Who can sign in, and what each person is allowed to do.
- 03
Servers and hosting
The machines and services that keep your system running.
- 04
Data
Where information is kept, who can reach it and how it is protected.
- 05
Email and phishing
How your messages are protected, and how your people spot fakes.
- 06
Backups
Copies you can restore from, and a restore that has been tried.
04 What you receive
Something you can act on.
- 01
A written report
In plain words: what we checked, what we found and what matters most.
- 02
Fixes or guidance
We make the fixes, or we tell your team exactly what to change.
- 03
A re-test
After the fixes we check the same things again and tell you what changed.
05 Trust and limits
What we promise, and what we do not.
Permission comes first
We test only systems you own or may allow us to test, and only after you confirm it in writing.
Your details stay private
What you tell us about your system, and what we find, stays between you and us.
We say what we checked
We tell you what we checked, what we found and what risk remains. We do not describe any system as beyond attack.
06 Questions
Good questions.
No. We test only what you own or have written permission to test, and we ask you to confirm it before we start.
We tell you what we checked, what we found and what is left to do. Nobody can honestly say that a system cannot be attacked.
You do. The scope and the findings stay between you and us, and any sharing is agreed in writing.
By the size of the system and the work it needs. We give a written price after a short conversation.
07 Other services