Skip to main content

regulator-portal-service — Migration Plan

Version: 1.0 Status: Draft Owner: Regulator-facing + Legal + SRE Last Updated: 2026-04-21 References: SERVICE_OVERVIEW.md, SERVICE_READINESS.md

Greenfield service. Migration is partner-engagement + phased enablement of capabilities.


1. What Is Migrating

InputSourceNotes
ATRA user certificatesRegulator Liaison engagementPer-user via national-PKI
Auditor certificatesExternal audit firmsPer-engagement, time-boxed
Evidence catalogCompliance teamControl families (ISO 27001, SOC 2)
SIEM destinationsATRA + internal security teamEndpoint + auth config
LI procedure documentationLegal + ATRAStored in runbooks

No data migration — service is new.


2. Migration Phases

Phase 0 — Pre-migration engagement (3 months)

StepOwnerOutput
ATRA MoU for portal accessRegulator Liaison + LegalSigned MoU
Per-regulator-user PKI issuanceSecurity + Regulator LiaisonCerts for initial 5-10 ATRA staff
SIEM destination configuration (Splunk / QRadar / Logstash per ATRA preference)Security + ATRAEndpoints + auth
HSM provisioning + signing key generationSecurity + SREKeys in HSM
Evidence catalog populated for ISO 27001 (control families + auto-collection jobs)ComplianceCatalog complete
Auditor procedure + onboarding templateLegal + ComplianceProcedure doc
Service deployed to stagingSREGreen

Phase 1 — Read-Only Reports (30 days)

StepOwnerOutput
Regulator login live (ATRA staff onboarded)ServiceLogin metrics
Daily CDR submission status report generated + deliveredServiceDaily artefact
Monthly compliance summary report generatedServiceMonthly artefact
SIEM forwarding live to internal security SIEM firstServiceEvent flow
LI workflow disabled (REG_LI_WORKFLOW_ENABLED=false)SRE

Exit criteria. 30 consecutive days of successful reports + ATRA acknowledgement; 0 SIEM lag incidents > 5 min.

Phase 2 — Complaint ingest + scheduled reports (30 days)

StepOwnerOutput
Complaint POST endpoint liveServiceComplaints flowing
Admin-dashboard triage workbench (EP-ADMDASH-10) liveFrontendUI
Ad-hoc report endpoint liveServiceSelf-service reports
Regulator-user count increasedRegulator LiaisonMore ATRA staff

Exit criteria. 50+ complaints processed; < 10 escalations.

Phase 3 — LI Workflow (30 days)

StepOwnerOutput
REG_LI_WORKFLOW_ENABLED=trueSRE
First real LI request processed end-to-endLegal + Regulator LiaisonDelivered + ATRA ACKed
SLA tracking activeSREDashboard
Dual-control bridge testedSecurity + LegalPhone + Slack operational

Exit criteria. 5 real LI requests handled within SLA; no SLA breaches; Legal sign-off.

Phase 4 — SIEM + Attestation (30 days)

StepOwnerOutput
SIEM forwarding to ATRA SIEM endpointServiceCross-boundary flow
Full attestation catalog populatedComplianceCatalog
Auditor portal live (read-only; time-boxed)ServiceLive
ISO 27001 annual bundle generation testedComplianceBundle signed

Exit criteria. First auditor engagement completes successfully; ATRA SIEM receives events within SLA.

Phase 5 — External Auditor (ongoing)

StepOwnerOutput
External audit firm onboarded for ISO 27001 / SOC 2Compliance + LegalEngagement
Audit-access granted with time-boxSecurityProvisioned
Audit completedCompliance + AuditorReport

Rollback flags. REG_LI_WORKFLOW_ENABLED, REG_SIEM_FORWARDING_ENABLED, REG_AUDITOR_PORTAL_ENABLED.


3. Regulator + Auditor PKI Onboarding

3.1 ATRA user

  1. Regulator Liaison identifies ATRA staff member.
  2. Staff member generates CSR with their national-PKI device.
  3. CSR sent to Ghasi Security via secure channel.
  4. Security signs cert with Ghasi Government Trust Anchor (or routes to national PKI when available).
  5. Cert + private-key guidance delivered to staff via in-person or MoU-approved channel.
  6. regulator.users row created with cert subject.
  7. Staff tests login.

3.2 External auditor

  1. Audit firm contracted (Compliance + Legal).
  2. Auditor certs issued by firm's own CA (or Ghasi auditor CA for small firms).
  3. Time-boxed access granted via POST /v1/admin/regulator/auditor-access (default 30 d).
  4. Auditor tests login + evidence download.
  5. Access expires + auto-revokes.

4. SIEM Destination Bootstrap

4.1 Internal SIEM first (Phase 1)

  • Internal security team operates Splunk / ELK.
  • Ghasi forwarder starts with internal-only destination.
  • Validates event volume, schema, latency.

4.2 ATRA SIEM (Phase 4)

  • Regulator Liaison confirms ATRA SIEM endpoint details.
  • Credentials exchanged (mTLS client cert preferred).
  • Schema dry-run: 1 day of events forwarded to ATRA test endpoint.
  • ATRA feedback on schema → adjustment.
  • Production cutover.

4.3 Multi-destination fan-out

  • Destinations configured in regulator.siem_destinations with auth + format.
  • Each destination ACKs independently.
  • One-off or scheduled reconciliation: count per destination should match NATS event count (within tolerance).

5. Downstream Integration Migration

IntegrationPhaseNotes
compliance-engine compliance.audit.v1 consumerPhase 1Read-through for reports
consent-ledger consent.* consumerPhase 1Read-through
sender-id-registry sender.id.* consumerPhase 2Read-through
cdr-mediation CDR submission-status readerPhase 1Daily report
analytics-service ClickHouse cold-tier readerPhase 2Long-range queries
admin-dashboard complaint workbenchPhase 2UI integration

6. Success Metrics

MetricTargetMeasurement
ATRA staff active on portal≥ 5 by end Phase 1Login metrics
Daily reports generated + delivered100% by end Phase 1Daily
LI SLA attainment100% within 24 h (Phase 3 on)Per request
Complaint SLA attainment95% within 5 business days (Phase 2 on)Monthly
SIEM event loss0Continuous
Auditor engagement completion≥ 1 successful by end Phase 5Per engagement
Evidence freshness≥ 95% CURRENT (Phase 4 on)Daily

7. Rollback Plan

Per-phase flags revert behaviour. Catastrophic path:

  • mTLS compromise: revoke all ATRA certs + re-issue.
  • HSM compromise: rotate signing key (key in HSM not usable directly; regenerate on recovery).
  • Data breach: Regulator Liaison + Legal + Security tri-party incident procedure.

8. Dependencies

  • National-PKI or interim Ghasi Government Trust Anchor.
  • HSM operational (per ADR-0004 §11).
  • All read-through upstream services operational (compliance-engine, consent-ledger, sender-id-registry, cdr-mediation, analytics-service).
  • Admin-dashboard EP-ADMDASH-10 (regulator workbench UI).
  • regulator-portal-service infra: Postgres, Redis, NATS, S3, HSM, disk-WAL PVC.

9. Post-Launch Refinement

  • Quarterly regulator-user survey (portal UX).
  • Monthly SLA review with ATRA.
  • Annual compliance-attestation cycle; refine evidence catalog based on audit findings.