Security should follow the sensitivity of the information.

Tibacare separates patient, clinician and operations access. Clinician and operations access uses multi-factor authentication in staging and production, with role and permission controls appropriate to those privileged areas.

Authentication is followed by permission and resource checks. A clinician is limited to assigned consultations and other authorised resources; operations users do not receive clinical-record access by default. Exceptional elevated access must be justified, limited and auditable.

Tibacare applications use host-only session cookies so credentials are not deliberately shared across unrelated subdomains. Mutating application requests use cross-site request-forgery protections, and privileged sessions use stricter controls than ordinary public browsing.

The public marketing website does not request access to a visitor's camera, microphone or location. It also applies browser-facing protections against content-type confusion, framing and unnecessary referrer disclosure.

Public application traffic uses HTTPS, database connections require transport encryption, and the approved Azure services provide encryption at rest for core database, storage and secret-management services.

Application secrets are held in Azure Key Vault and supplied to authorised workloads through managed identities and secret references. Routine application access to private file storage also uses managed identity rather than embedded storage keys.

Tibacare's approved core production architecture uses UK Azure regions. Production and non-production environments are separated, and file containers used for uploads, documents and operational recovery are private rather than anonymously accessible.

UK hosting is a location control, not a claim that authorised international access can never occur. Any new country, supplier or material access route remains subject to the applicable security, privacy and transfer review.

This public website is hosted separately, in Microsoft's West Europe region.

Tibacare uses application and platform monitoring, service health checks, alerts and audit records to support detection, investigation and accountability. Relevant database, infrastructure and secret-management events feed the monitoring environment.

Operational logging is designed to retain useful context such as correlation, route, status and audit events while redacting authentication secrets, session tokens, passwords and other sensitive credential material.

The infrastructure uses database backup and point-in-time recovery capabilities together with storage soft deletion and versioning where applicable. Recovery procedures include validation rather than treating the existence of a backup as proof that restoration will succeed.

A staging database restore drill has been completed successfully. Recovery arrangements remain environment-specific and are reviewed as the service and operating scale change; this page does not promise zero data loss or uninterrupted availability.

Tibacare maintains defined processes for identifying, classifying, containing, investigating and recovering from platform, security and privacy incidents. The process includes evidence preservation, access or secret revocation where necessary, communication and post-incident improvement.

Clinical-safety, safeguarding, payment and privacy concerns may require parallel specialist escalation. Platform operations does not replace clinical judgement, professional regulation or the responsibilities of the relevant data controller.