GRCLibrary.ai

Document type

Plans

6 documents. Event-triggered or schedule-bound coordination such as incident or recovery.

Documents, 6

Every document of this type

Each with its area and its purpose; a document that states no purpose gets a line naming its type and area. A title in a corpus area opens the document's page, which holds the record and, where the document has them, its outline, frameworks, and related documents; a title in the Library area is a library specification with no page and opens its source on GitHub. The full text of every document is read on GitHub.

  • AI Incident Response PlanAIThis plan defines the AI-specific incident response path that operates alongside the security and privacy incident procedures. It covers prompt injection, indirect prompt injection, jailbreak, data poisoning, model inversion, membership inference, retrieval leakage, agent compromise, unsafe tool execution, hallucination causing material harm, model degradation, and supplier model incidents.
  • Business Continuity and Crisis Management PlanResilienceThis plan defines an organization-neutral structure for maintaining critical business functions and managing crises that disrupt operations, technology, facilities, suppliers, data, AI systems, or personnel availability.
  • Crisis Communication PlanResilienceThis plan defines a reusable structure for preparing, approving, issuing, tracking, and closing communications during incidents, disruptions, breaches, crises, supplier failures, AI system events, or other material events requiring coordinated messaging.
  • IT Disaster Recovery PlanResilienceThis plan defines the system-specific recovery procedures, RTO and RPO targets, and runbook references for IT Disaster Recovery (DR). It is a companion document to the BC/DR Standard and the Business Continuity and Crisis Management Plan, which govern the broader BC/DR framework. This plan focuses on IT system recovery execution rather than business continuity governance. The plan reflects industry experience with phased recovery from major security incidents; adopting organizations calibrate RTO/RPO targets, tier assignments, and phasing to their own incident history, risk appetite, and operational context. The specific infrastructure, environments, and topology named throughout this plan (for example on-premises and cloud tiers, a hypervisor estate, directory and identity services, and a cloud-based recovery platform) are an illustrative reference deployment, not a description of any particular organization's environment; an adopter substitutes its own.
  • Pandemic Continuity PlanResilienceThis plan defines the organization's continuity posture for a pandemic or other prolonged workforce-impacting disruption (severe respiratory disease, novel infectious outbreak, prolonged civil unrest affecting facility access, prolonged extreme weather affecting commuting). It covers staged activation, workforce health, remote-work scaling, supplier impact, facility and operational adjustments, essential-service prioritization, communications, deactivation, and learning. It is a sister plan to the IT disaster recovery plan and the business continuity and crisis management plan.
  • Physical Site Continuity PlanResilienceThis plan defines how a specific physical site (office, data centre, warehouse, operational facility) maintains essential operations and supports a controlled return to baseline when the site is disrupted. It covers protective actions during the event, partial-operations posture during recovery, alternate-site activation when relocation is required, and full restoration. It is a sister plan to the IT disaster recovery plan and the business continuity and crisis management plan; it does not replace either.

With script, All Documents, filtered to Plans, lists these 6 documents, and the area chips holding any of them, and its text filter, narrow them further.