Safeguard Docs
Compliance FrameworksMiddle East & Africa

Cameroon Law 2010/012 on Cybersecurity

National cybersecurity framework: software asset inventory, component integrity, supply-chain verification, and vulnerability management.

National cybersecurity framework: software asset inventory, component integrity, supply-chain verification, and vulnerability management.

Short nameCM Cyber
RegionMiddle East & Africa
Country or scopeCameroon
SectorGovernment
In your workspaceOff until you switch it on in Compliance โ€บ Manage.

How Safeguard covers CM Cyber

  • Scan requirements: 6, all decided by a scan.
  • Controls: the scan requirements below.
  • Automated tests: none map to it directly. You can link any automated test to its controls yourself (how).
  • Policy templates: 22 from the standard set.

How each kind of coverage works, and what the readiness score counts: Compliance frameworks.

What a scan checks

Each scan of a product checks these 6 requirements against what the scan found, including the product's software inventory (SBOM).

RequirementWhat Safeguard checksDecided by
CM-CYBER-AUD Mandatory Security Audit InventoryElectronic communication networks and information systems are subject to compulsory security audits examining components, policies, measures and resources, which requires an enumerated inventory of the software components in scope (Law No. 2010/012, Arts. 7, 13 and 14 audit framework)Scan
CM-CYBER-SEC Security of Networks and Information SystemsOperators and providers must protect their networks and information systems and ensure conformity with laid-down security standards, presuming verifiable integrity of the software components deployed (Law No. 2010/012, security obligations verified via the Art. 13-14 audit regime)Scan
CM-CYBER-INC Intrusion Notification ReadinessOperators must notify ANTIC of intrusions into their networks and information systems; assessing what was compromised requires precisely identifiable components (PURL/CPE) across those systems (Decree No. 2012/1643/PM implementing Law No. 2010/012)Scan
CM-CYBER-GRAPH Auditable System CompositionA systematic audit of security components and actors requires the relationships between software components to be documented so auditors can trace how the system is composed (Law No. 2010/012, Art. 32 and Art. 61 audit provisions)Scan
CM-CYBER-VULN Maintained, Patchable SystemsEnsuring conformity of information systems with security standards over successive audits requires known versions for every component so vulnerable software can be identified and remediated (Law No. 2010/012, audit-conformity obligation)Scan
CM-CYBER-DOC Dated Audit DocumentationThe recurring audit and certification regime requires dated, identifiable documentation of system composition, satisfied by an SBOM with document ID and creation timestamp (Law No. 2010/012, audit framework with Decree No. 2012/1643/PM)Scan

Policy templates

All 22 from the standard set, adapted to CM Cyber.

On this page