Skip to main content

Number Intelligence Service — Risk Register

Version: 1.0 Status: Draft Owner: Messaging Core Last Updated: 2026-04-20

1. Intent

This document tracks the known risks for number-intelligence-service, their owner, likelihood, impact, and mitigation. Risks specific to NI cluster around dependence on MNO cooperation (live HLR, MNP, EIR feeds) and sovereign data-residency obligations.

2. Risks

TBD

IDRiskLikelihoodImpactOwnerMitigation
R-NI-01MNO refuses to expose live HLR / SS7 accessMedHighPartnershipsNegotiate REST adapter as alternative; pre-warm Postgres from MNP files
R-NI-02Per-MNO TPS contracts insufficient for OTP stormsMedHighPartnerships + SREIncrease cache hit ratio; pre-warm batches; renegotiate TPS
R-NI-03MNP file format drift across MNOsHighMedMessaging CoreAdapter per MNO; schema validation with rejection counts
R-NI-04ATRA changes EIR feed format / cadenceMedMedComplianceAdapter pattern; daily verify cadence
R-NI-05MSISDN PII leakage via metrics / logsLowCriticalSecurityHash MSISDN in all non-Postgres surfaces; security review
R-NI-06Sovereign residency breach via cross-region replicationLowCriticalSRE + SecurityHSM-wrapped backups; key never leaves kbl HSM
R-NI-07Hash-chain mutation by privileged operatorLowCriticalSecurityDB role separation; chain verify daily
R-NI-08Stale routing decisions due to delayed MNP ingestMedMedMessaging CoreHourly recon retry; on-demand admin endpoint
R-NI-09Tenant enumeration of national numbering plan via Lookup APIHighMedTrust & SafetyPer-tenant quotas; AI anomaly scoring; audit
R-NI-10Live HLR cost spikes under malicious tenant trafficMedMedFinance + SREInternal callers do not pay; tenant forceFresh carries premium SKU

3. Risk Review Cadence

TBD

4. References

  • ADR-0004 §5
  • SECURITY_MODEL.md