Skip to Content
A doctor talks with a person in a healthcare setting.

GROUPETAURUS · Cybersecurity & continuity

Review access.
Test your backups.

A compromised account, an unavailable computer or an unusable backup can interrupt your work. We organise protection measures and recovery procedures around your critical activities, with clear responsibilities and checks planned from the beginning of the engagement.

Illustrative professional setting

Cybersecurity & continuity

What needs to work better.

Security decisions should reflect your organisation’s actual risks. Start by identifying what matters, who can access it and how work can continue if a tool becomes unavailable.

01

Access is hard to track

Shared accounts, departures not processed and excessive permissions make it difficult to know who can do what. An inventory of identities and administrators provides a practical basis for putting access management in order.

02

Backups have never been restored

A successful backup message does not prove that information can be recovered. Check the copy, its isolation, retention and an actual restoration within an explicitly agreed test scope before relying on it.

03

There is no outage procedure

Contacts, emergency access and priorities are scattered. An interruption needs defined roles, a recovery decision and information that remains available when the main system no longer responds, rather than instructions stored only inside that system.

Build useful layers of protection.

Identities and workstations

Review permissions, separate everyday and administrator accounts, use multifactor authentication where supported and organise updates. The selected measures must remain workable day to day, with a process for new starters, role changes and departures, including ownership of exceptions.

Data and backups

Identify information needed for operations, restrict access and define suitable backup copies. Backup data also requires protection, ownership and testing. Documented retention helps distinguish collecting many copies from maintaining a real ability to recover the information that the business needs.

Continuity and response

Prepare contacts, escalation steps and restoration priorities. Separate temporary working arrangements, technical restoration and the return to normal operations. A limited exercise checks whether people can follow the procedure, without presenting a theoretical document as a guarantee of availability.

Set recovery targets with the business.

RTO is a target recovery duration; RPO describes a target for acceptable data loss expressed in time. Business owners set these objectives and compare them with available resources. A backup alone is not a recovery plan. Network, software, supplier and people dependencies also need consideration. No measure removes every risk, so the scope and limitations of checks are recorded rather than left implicit. An exercise provides evidence for the tested conditions only.

Prevent, detect and recoverIdentities, workstations and data receive appropriate controls. An alert starts response and tested recovery, followed by a review of what was learned.IdentitiesWorkstationsDataResponseTested recoveryPrevent, detect and recoverIdentities, workstations and data receive appropriate controls. An alert starts response and tested recovery, followed by a review of what was learned.IdentitiesWorkstationsDataResponseTested recovery
Prevent, detect and recover. Identities, workstations and data receive appropriate controls. An alert starts response and tested recovery, followed by a review of what was learned.

DELIVERY

From the need to daily operation.

  1. 01

    Scope the risks

    Identify critical activities, assets, access, backups and known incidents. Agree permissions and intervention boundaries. No intrusive action is undertaken without an explicit scope, authorised access and an agreed way to stop if necessary.

  2. 02

    Prioritise measures

    Rank gaps by impact and feasibility. Assign an owner, an implementation order and expected evidence for each action, instead of producing only a list of security products to purchase.

  3. 03

    Implement the changes

    Configure the selected measures with a rollback approach. Document changes and arrange necessary communications, so users are not locked out without an alternative way to perform essential work.

  4. 04

    Test and hand over

    Run the agreed access, restoration or recovery exercise. Record results, outstanding issues and next actions. Give contacts and procedures to the people responsible for keeping them current.

ILLUSTRATIVE SCENARIO

An organisation needs to resume administrative work.

Example scenario without patient information. The team needs to find its documents if a main workstation fails. Work covers authorised accounts, a protected backup copy and restoring a test folder onto another workstation. The owner checks recovered files and the recovery steps. Recovery targets remain subject to testing and the dependencies observed during the exercise. The exercise also identifies who can authorise recovery and where the necessary contact information is kept.

DELIVERABLES

What the engagement can deliver.

The proposal confirms selected deliverables and their acceptance criteria.

  • Scope inventory and review of the main risks observed.
  • Access matrix and prioritised action plan with assigned owners.
  • Documentation of configured measures and accepted exceptions.
  • Backup, response or recovery procedures according to the engagement.
  • Test report and guidance for periodic follow-up checks.

A sequence to agree together.

  1. Review · 1–2 weeks

    Scope, access and critical activities.

  2. Priorities · 1 week

    Actions, owners and required approvals.

  3. Implementation · by risk

    Scheduled measures and controlled changes.

  4. Exercise · agreed window

    Limited test, report and corrections.

Indicative planning, without a delivery commitment. Timing depends on scope, access, approvals, procurement and team availability. Stages may overlap.

What affects the quotation.

Account, workstation, location and application counts, business criticality and the depth of checks change the scope. Licences and subscriptions are separated from services. Continuous monitoring, on-call coverage and incident response are included only when expressly agreed, with their hours, responsibilities and limitations stated in the proposal.

Practical questions.

Does an audit guarantee protection?

No. It describes an agreed scope and findings at a particular time. Remediation, everyday practices, maintenance and regular checks remain necessary. The report identifies limitations in visibility and does not imply that untested areas are secure.

Can we start without replacing every tool?

Yes. Reviewing access, enabling protections already available and testing a restoration can form a useful first increment. Any purchases follow the identification of gaps and approval of priorities, rather than replacing those decisions.

Tell us about your situation.

Describe your activity, locations, existing tools and the problem to solve. You can provide an initial context without sharing confidential documents.