Trust & Security
Incident response
High-level public process for how MedicalBot approaches security and service incidents. This page intentionally omits sensitive operational details.
MedicalBot communicates security and governance capabilities based on documented architecture, implementation scope, and verified agreements. Certification or regulatory status is presented only when formally established.
Process
Public incident stages
A shared vocabulary for procurement conversations. Contact channels and contractual SLAs remain the authoritative notification paths when incidents occur.
Detect
Identify anomalous behaviour, service degradation, suspected unauthorised access, or reportable events through monitoring, staff reports, or customer notices.
Contain
Limit further impact using access suspension, isolation of affected systems, credential rotation, and temporary feature disablement as appropriate — without publishing playbook internals here.
Assess
Determine scope, data classes involved, affected organisations, and whether contractual or regulatory notification duties may apply. Assessment is evidence-driven and role-separated where possible.
Communicate
Notify affected customers and stakeholders according to contractual commitments and applicable law. Public marketing pages are not the primary incident notification channel.
Recover
Restore known-good service, validate integrity of restored systems, and confirm that temporary containment measures can be safely lifted.
Review
Document root cause at an appropriate level, capture corrective actions, and feed improvements into security, clinical governance, and responsible-AI change control.
What we do not publish here
- Internal runbooks, detection signatures, or network diagrams
- Employee personal contact details for war rooms
- Guaranteed notification timelines presented as universal SLAs without a signed agreement
Customer-facing security contact and contractual notification terms will be published when operational programmes are finalized. Contact us for current information.
See MedicalBot in a guided demo
Book a product walkthrough with our team. We discuss architecture, governance patterns, and fit for your organization — without collecting PHI.
Do not submit protected health information (PHI) on this website.