A website to secure, a WordPress site to take over or infrastructure to review? Start with your environment to define useful checks, prioritise remediation and plan what comes next.
Clarify risks and responsibilities around your services: hosting, accounts, configurations and backups. Define the appropriate review and contributors.
A starting point if you need a broader view of your services, are preparing a takeover or want to prioritise an improvement programme.
Deliverables to agree together
Inventory of in-scope services and dependencies
Agreed review of access, configurations and restoration arrangements
You know what will be examined, what you will receive and how actions will be handled. Assessment, remediation and verification are distinguished in the proposal.
01
Define the scope
Your important services, goals and available access. Define the scope, contributors, authorisations and verification conditions together.
An agreed assignment and deliverables
02
Assess & prioritise
The agreed checks produce documented findings. The review distinguishes impact, priorities and actions to organise.
A summary and action plan
03
Remediate & verify
Assign fixes to named owners. Agree on the work Gaspa will handle, verification of fixes and useful follow-up.
Tracked actions and an updated status
Prepare our conversation
Start with your situation.
A few details are enough for an initial conversation. Your team or current provider can participate in defining the scope.
The website, application or services involved
Your goal: launch, takeover, maintenance or verification
Hosting provider, technologies and owners, if known
Your timing and operational constraints
Describe your needs in the form; access-sharing arrangements will be agreed afterwards.
A proposal that fits the scope.
Budget and timing depend on what needs to be examined and the depth of the checks. These are specified after scoping.
For a website, application or API, start with a web security assessment. For a WordPress site to take over and maintain, choose WordPress security. To also review hosting, accounts and continuity, request cybersecurity and infrastructure scoping. The initial conversation helps define the right scope.
Penetration testing can be part of an assignment when explicitly agreed. The proposal defines targets, authorisations, test conditions, contributors and deliverables. It is not automatically included in a UX and technical audit or maintenance.
Scoping starts with the existing environment, available access and allocation of responsibilities. It defines a takeover or intervention with your team, agency and hosting provider where their involvement is needed.
The proposal distinguishes assessment, review, remediation and verification of fixes. It specifies the work Gaspa will handle and the work assigned to your other providers, giving you an explicit scope and responsibilities.
The price depends on the number of services and environments, user roles, access and the depth of checks. Remediation, verification of fixes and any follow-up are specified in the proposal after scoping.
Agreed deliverables may include a scope inventory, documented findings, an impact summary and a prioritised action plan. If verification of fixes is included, it records the status of the remediation examined. Conclusions apply to the scope and period of the assignment.
Cybersecurity · Brussels, Belgium