1 | What the guideline is, whom it binds and when it applies | 0 |
10.1.I | Adopt a zero trust architecture | 0 |
10.1.II | Run an ISMS aligned with ISO/IEC 27001 and the NITDA ISMS guideline | 0 |
10.1.III | Encrypt data at rest and in transit with AES-256 or stronger | 0 |
10.1.IV | Run annual independent penetration tests and continuous vulnerability scanning | 0 |
10.1.V | Protect public-facing applications and APIs with a web application firewall | 0 |
10.1.VI | Assess operational, cyber, concentration, systemic, dependency, supply chain, outsourcing and exit risks periodically | 0 |
10.1.VII | Manage supply chain risk to recognised standards and keep security operations accountable | 0 |
10.2.I | Enforce role-based access and multi-factor authentication, with FIDO2 keys for Level 3 and 4 environments | 0 |
10.2.II | Apply location-aware, risk-based access for Level 2 data and above with justified, time-bound exceptions | 0 |
10.2.III | Manage all privileged access through PAM with just-in-time access, session recording and immutable logs | 0 |
10.3.I | Report verified breaches and significant incidents within 24 hours to the FPI, NDPC where personal data is involved, sector regulators and NITDA | 0 |
10.3.III | Include the minimum content in the initial breach notification | 0 |
10.3.IV | Log every security incident in detail and cooperate with law enforcement and security agencies | 0 |
10.4.I | Maintain tested disaster recovery with distributed backups and automated failover, with RTO and RPO in every SLA and verified by the SI | 0 |
10.4.III | Evidence successful DR testing for NITDA certification and recertification | 0 |
10.4.IV.a | Keep primary and secondary sites in Nigeria in different geopolitical zones for Level 2 and above, and never move Level 4 data abroad | 0 |
10.4.IV.c | Use an out-of-country tertiary backup only for Level 1 and 2 data, under the stated conditions and with NITDA's prior written approval | 0 |
11.1 | Run a cloud readiness assessment, dependency mapping, migration classification and rollback plan before migrating | 0 |
11.2 | Execute a pilot migration before full-scale migration | 0 |
11.3 | Secure the migration with end-to-end encryption, TLS 1.2 or higher, integrity verification and an immutable audit trail | 0 |
11.4 | Validate after deployment, monitor SLAs continuously and run FinOps | 0 |
11.5 | Decommission legacy infrastructure under an approved plan with certified data destruction and a final report | 0 |
11.6 | Control sovereign compute and AI infrastructure workloads | 0 |
12.1 | Classify data under the national framework and host it to the matching residency and security standard | 0 |
12.2 | Give access to audit logs and compliance dashboards and file the quarterly infrastructure status report | 0 |
12.3 | Submit to NITDA and third-party audits and meet any higher sector-specific requirements | 0 |
13.1 | Build and operate data centres to Tier III or Rated-3 for Level 3 and 4 data and Tier II or Rated-2 for Level 2 | 0 |
13.2 | Provide N+1 power redundancy and report PUE annually | 0 |
13.3 | Secure data halls with three-factor entry, 24x7 guards and 90-day CCTV retention | 0 |
13.4 | Hold NITDA certification under the NDIAF, maintain continuous compliance and notify material changes | 0 |
9.1 | Source cloud services by data classification, prioritise indigenous providers and apply Cloud First with a TCO analysis | 0 |
9.2.I | Require the baseline international standards of every procured cloud service | 0 |
9.2.II | Select the service model on documented need and fiscal responsibility | 0 |
9.2.III | Choose the deployment model by data classification: public for Levels 1 and 2, in-country private for Levels 3 and 4 | 0 |
9.3.I | Meet the tiered 24x7 availability and support levels set by data level | 0 |
9.3.IV | Guarantee in-country network latency between 50 and 150 milliseconds | 0 |
9.3.V | Give FPI governance officers continuous performance dashboards and monthly reports | 0 |
9.3.VI | Relax latency or support targets only with a justified impact assessment | 0 |
9.4 | Procure through the Digital Regulatory Platform and keep marketed service bundles compliant | 0 |