Skip links

How to Plan Backups, Access Controls, and Recovery for an RCIC Website

Share

Plan your RCIC website around three connected responsibilities: recoverable backups, appropriate access, and a tested recovery process. Start by identifying what the website stores, how much recent data your firm could lose, and how long each service could remain unavailable.

Then assign an owner to every essential account and recovery task.

A website failure can affect consultation enquiries, booking confirmations, uploaded documents, and CRM connections. Getting the homepage online is only part of restoring the service clients and staff depend on.

The Code of Professional Conduct for CICC licensees addresses confidentiality in section 28 and reliable office administration and record keeping in section 37. Your technical plan should support those responsibilities alongside the privacy requirements applicable to your firm. laws-lois.justice.gc.ca

Know What Depends on Your Website

Create an inventory before buying backup software.

List the website, its connected services, the information each holds, and the person responsible for it.

ComponentWhat to establish
Website and CMSWhere pages, code, themes, plugins, and media are stored
Forms and enquiriesWhether submissions remain on the website, enter the CRM, or both
Booking systemWhere appointments, availability, and confirmations are recorded
Client portal and uploadsWhich system stores files, permissions, and document history
Domain, DNS, and emailWho controls accounts, renewals, records, and recovery methods
External integrationsHow CRM, payment, messaging, and other connections can be restored

A hosting backup may cover only the hosting account. Confirm the scope of each provider’s service in writing.

When planning technology for your immigration firm, treat this inventory as the foundation for ownership and recovery decisions.

Set Recovery Targets Your Firm Can Actually Meet

Agree on two business targets with your technical provider:

  • Recovery point objective, or RPO: how far back in time your recovered data may go, reflecting the amount of recent data loss your firm can tolerate.
  • Recovery time objective, or RTO: the target time for restoring the agreed service after disruption. CSRC

For example, suppose your firm decides it can tolerate losing up to two hours of enquiry records and needs the enquiry service restored within eight hours.

A single nightly backup cannot reliably meet that two-hour data-loss target. Your provider must design the relevant protection around it and demonstrate recovery within the agreed time.

Set targets for individual services. Public blog content and frequently changing appointment records may need different arrangements.

Define what “restored” means: a visitor can submit an enquiry, the record reaches its destination, and the assigned staff member can access it.

 

Portable navy backup drive beside an ivory case and open blank notebook.

Back Up Every Part of the Website Workflow

A complete recovery plan identifies the files, database, uploads, configuration, and dependencies required to rebuild the service.

For a WordPress website, that usually means more than exporting blog posts. For a custom application, it also means preserving source code, deployment instructions, and the configuration needed to recreate its environment.

Coordinate database and file recovery so restored records point to the correct uploaded files. A database snapshot and an unrelated upload archive may leave broken or mismatched records.

For external services, confirm backup coverage, available exports, restoration limits, and responsibility. An export is useful only if your team can restore or otherwise use it.

Connect these decisions to your website design and planning. Reducing unnecessary storage of sensitive information on the public website can simplify its protection and recovery.

Schedule additional recovery points before significant updates, while preserving the regular backup schedule.

 

Protect Backups From the Same Failure

Keep recovery copies protected from the incident that could affect the live website.

The joint #StopRansomware Guide, published by CISA and partner agencies, recommends offline, encrypted backups and regular recovery testing. It also explains that attackers may target accessible backups. ic3.gov

Discuss an independent backup location, separate administrative controls, and an offline copy or appropriately configured immutable storage. Immutable storage prevents changes or deletion for a defined period under its configured controls.

Verify who can delete backups or shorten their protection period.

Record where encryption keys and recovery credentials are held. Authorized staff must be able to retrieve them if the website or its usual administrator is unavailable.

Keep multiple dated recovery points, monitor failed jobs, and define retention according to business needs and applicable obligations. A backup policy should specify what happens when a scheduled copy is missed.

 

Two hardware security keys on a coral tray beside a tablet and navy folio.

Give Each Person the Access Their Role Requires

Give each user the permissions needed for assigned work.

OWASP’s Authorization Cheat Sheet recommends least privilege, denying access by default, and checking permissions on every request. OWASP Cheat Sheet Series

Translate those principles into your firm’s responsibilities:

RoleExample access
Content editorEdit approved website content without administering hosting or client records
Intake staffHandle assigned enquiries without changing infrastructure or backup settings
Case team memberAccess authorized matters and documents according to assignment
Technical maintainerTime-limited maintenance access; production data access only when justified
Recovery operatorControlled restoration permissions, with destructive actions restricted

Use individual accounts so changes can be attributed to a person. Review access when responsibilities change and promptly remove access when someone leaves.

For a client portal, permissions must apply to the individual matter and file. Hiding a download button does not protect the underlying document.

Make those checks part of any custom web application development scope.

Keep Account Recovery Under the Firm’s Control

The firm should control its domain, hosting, business email, backup service, and essential vendor relationships.

Use firm-managed ownership and recovery details. Assign a second authorized custodian so recovery does not depend on one employee or an agency’s personal account.

Require multifactor authentication for privileged accounts. Prefer phishing-resistant methods, such as supported passkeys or security keys, where available.

Store recovery codes and credentials in an approved vault with appropriate access controls. Keep the recovery route available independently of the affected website.

Document how an authorized person obtains emergency access, how its use is logged, and how access is reviewed afterward.

Include domain renewals, billing contacts, and vendor support procedures. An expired domain or inaccessible recovery email can interrupt operations even when the website backup is intact.

 

Write a Recovery Runbook With Named Owners

Create a short operating guide that staff can follow during an outage.

Assign a decision-maker, technical recovery lead, backup contact, and person responsible for staff and client updates.

The runbook should explain:

  1. How to identify and classify the disruption.
  2. Who can authorize containment and recovery.
  3. Where to find account access, backups, and provider contacts.
  4. Which services to restore first.
  5. How to validate restored functions and data.
  6. Who authorizes reopening and communicates updates.

Keep an accessible copy outside the affected hosting environment. Refer to protected credentials through the approved vault.

For suspected compromise, involve qualified incident responders, preserve relevant evidence, address the cause, and select a recovery point assessed as suitable. Restoring a website does not settle whether information was exposed.

Have the responsible people assess applicable reporting and notification obligations.

Maintain an approved alternative contact route and keep urgent client deadlines visible during disruption. Include the guide in your documentation and handover.

 

Two laptops beside a portable backup drive and coral notebook in a bright office.

Practise Recovery Before You Need It

A successful backup notification confirms that a job reported success. A recovery rehearsal shows whether the firm can use its recovery arrangements.

Restore into an isolated environment. Control access and prevent test systems from sending real emails, charging clients, publishing private material, or triggering live automation. Use fictional data wherever practical.

Check the complete journey:

  • Pages, media, and consultation links load.
  • A test enquiry reaches its intended destination.
  • Booking records and time zones remain correct.
  • Authorized users can access the appropriate files.
  • HTTPS, domain resolution, and email routing work correctly.
  • Unauthorized accounts are denied access.
  • Restored records match their uploaded documents.
  • Integrations resume without duplicate messages or transactions.

When reconnecting your CRM and automation, reconcile records created during the outage. Replaying queued events blindly can repeat actions.

After restoring an older backup, reapply account removals, permission changes, and credential rotations made since that backup. Confirm that former staff and revoked credentials remain blocked.

Include an exercise where the original hosting account is unavailable. Record the backup date, recovery duration, missing records, failed checks, and corrective actions.

Repeat exercises after material changes and on a documented schedule appropriate to the service.

Choose a Practical Starting Plan

Match the depth of the plan to what your website actually does.

Website setupStarting priorities
Public information websiteContent and configuration recovery, domain ownership, editor permissions, tested rebuilding
Website with enquiries and bookingsAdd data-loss targets, submission monitoring, integration recovery, and record reconciliation
Website with a client portalAdd consistent file and database recovery, matter-level permissions, protected testing, and professional incident support

Assign a monthly review of backup failures, privileged accounts, renewals, and unresolved recovery issues.

After each significant website change, ask whether the inventory, permissions, and recovery instructions still match the live service.

Your next project

Let’s make your brand recognizable.

Have a business in mind? Tell us about your ideas, your audience, and the identity you want to create.

Prefer a direct conversation?

1 Step 1
Tell us about your project.

A few details are all we need to start the conversation.

keyboard_arrow_leftPrevious
Nextkeyboard_arrow_right
FormCraft – WordPress form builder

FAQ

Choose frequency from the rate of change and acceptable data loss. Frequently changing enquiries or bookings may need protection more often than public content. Confirm that completed, recoverable backups meet the firm’s agreed target.

 

Check its scope, retention, access controls, restoration process, and exclusions. Establish how recovery would work if the hosting account or provider became unavailable. The answer depends on the actual service and your firm’s recovery needs.

 

Synchronization can carry deletions or unwanted changes into another location. Assess version history, independent recovery points, retention, and administrator controls before relying on it. Demonstrate that an earlier usable state can actually be recovered.

 

RPO concerns the point in time to which data must be recovered. RTO concerns the time target for restoring service. A firm could recover quickly but lose too much recent data, or preserve data while experiencing excessive downtime.

 

Assign it to named people whose duties require it. Content editors, intake staff, and marketing contractors often need narrower permissions. Review privileged accounts periodically and after staffing or supplier changes.

 

Keep ownership and essential recovery details under the firm’s control. Give the agency appropriate delegated access for its work. Document renewal responsibility and handover arrangements so the firm can continue operating through supplier changes.

 

They can, depending on the systems and records included. Apply appropriate protection, access limits, and retention to recovery copies. Review where providers store them and who can access them.

 

Prefer fictional or appropriately anonymized data where it meets the test’s purpose. If production data is necessary, authorize and protect the test environment, restrict access, prevent live actions, and dispose of temporary copies under policy.

 

Use the incident response process first. Qualified responders should help assess scope, preserve evidence, contain the problem, and establish a suitable recovery approach. Recovery also needs to address the route that enabled the compromise.

 

Specify backup scope, frequency, retention, ownership, monitoring, restoration responsibilities, access controls, testing, support hours, and escalation contacts. Define response commitments separately from recovery targets and identify services handled by other providers.

Turn Recovery Planning Into Routine Website Care

Start with the inventory, agree on data-loss and downtime targets, review privileged accounts, and schedule a recovery rehearsal. Assign owners and resolve the gaps the exercise reveals.

M4YOURS IT can help your firm plan website maintenance, backup coverage, access controls, and recovery documentation around its actual systems.

Discuss your RCIC website recovery plan with M4YOURS IT and establish what your team needs to keep its website services recoverable.

Leave a comment

This website uses cookies to improve your web experience.