Help

Help & principles

Move from migration uncertainty to evidence-based readiness.

How it works

  1. 1
    Discover

    Inventory every system with a Directory or PKI dependency, including indirect dependencies via gateways, proxies and trust stores.

  2. 2
    Assess

    Evaluate the estate against the Migration Control Library. Assessments are read-only and repeatable.

  3. 3
    Remediate

    Findings become owned, scheduled remediations. The platform recommends; engineers implement through the Bank's change process.

  4. 4
    Prove

    Run assurance tests and capture evidence. Every artefact traces to requirement, control, test and result.

  5. 5
    Control

    Gate the production cutover on evidence. The Bank records the Go/No-Go decision.

Product principles

  • Evidence over assertion. Readiness is derived from tests and artefacts, not status updates.
  • Human-controlled remediation. The platform never modifies production systems.
  • Traceability. Requirement → Control → Test → Result → Evidence.
  • Risk-based prioritisation. Cutover blockers and critical findings first.
  • Executive, engineer and auditor views. Same data, role-appropriate depth.
  • Migration today, continuous assurance tomorrow. Assurance modules extend beyond cutover.

Frequently asked

Does the platform change any configuration?
No. It discovers, assesses, recommends and records. Changes go through the Bank's own change process and are then verified by retest.
Who can record the Go/No-Go decision?
Migration Programme Manager, Risk / Compliance and Administrator roles. Auditors are read-only.
Is demo data real?
No. NorthBank UK data is synthetic and contains no real secrets, certificates, credentials or personal information.
How is readiness calculated?
Weighted from controls passing, evidence coverage and test pass rate, with a penalty per open cutover blocker.