GRC · ISO 27001 · Algerian Cyber Law
GRC, ISO 27001 & Algerian Cyber Law
A practical foundation in governance, risk and compliance, and the specific rules that apply to organizations operating in Algeria.
Five chapters
Each chapter builds on the last: general principles first, then the standard that operationalizes them, then the law that makes them mandatory in Algeria.
Before any standard or statute, three questions: who decides, what could go wrong, and can you prove you did what you said. This chapter defines the vocabulary the rest of the guide depends on.
Governance, risk and compliance are three separate jobs
Teams that skip GRC end up reacting to every fire as it starts. GRC turns security into a program the business can govern, budget and audit, before the fire, not after.
Who decides
The structure of authority: who sets policy, who approves exceptions, and who is accountable when something fails.
What could go wrong
Identifying threats and weaknesses, estimating how much they matter, and deciding how much residual risk is acceptable.
Can you prove it
Turning decisions and controls into evidence, the paper trail a regulator or auditor can actually check.
Roles in a GRC program
A GRC program only works when each of these roles is filled by a named person, not a shared inbox.
Six terms you'll need for the rest of this guide
GRC isn't invented from scratch by each organization. A small set of laws and standards, some mandatory, some voluntary, set the vocabulary everyone else borrows, including Algeria's own regulators.
Mandatory law vs. voluntary standard
Mandatory
You don't choose whether it applies. Non-compliance carries legal or contractual penalties. Examples: GDPR, HIPAA, SOX, PCI DSS.
Voluntary
Adopted by choice, usually to prove maturity to customers, insurers or regulators. Examples: NIST CSF, ISO 27001, SOC 2, COBIT.
In practice the two blend: a mandatory law often points to a voluntary standard as the accepted way to comply with it.
Eight names worth knowing
| Framework | Type | Scope |
|---|---|---|
| GDPR | Mandatory regulation | EU personal data protection |
| HIPAA | Mandatory regulation | US healthcare data |
| SOX | Mandatory regulation | US public-company financial controls |
| PCI DSS | Mandatory standard (contractual) | Payment card data handling |
| NIST CSF | Voluntary framework | General risk management, 5 functions |
| SOC 2 | Attestation report | Service & tech providers, mainly North America |
| COSO / COBIT | Governance frameworks | Internal controls / IT governance |
| ISO 27001 | Certifiable ISMS standard | Any organization managing information security |
GDPR set the template everyone copies
- Extraterritorial reach, applies to any organization handling EU residents' data, regardless of where that organization is based.
- Lawful basis, you need a specific, documented reason to process personal data at all.
- Breach notification, a fixed clock starts the moment a breach is discovered.
- Data subject rights, access, correction and deletion rights held by the individual, not the company.
You'll see this exact pattern again, declaration and breach-notification duties, in Algeria's own data protection law in Chapter 4.
NIST CSF: five functions, one cycle
Voluntary, sector-agnostic, and widely used simply as a common vocabulary for organizing risk work.
Sector rules and attestation reports
- PCI DSS, mandatory anywhere payment cards are processed, stored or transmitted, enforced contractually by the card networks.
- SOX, mandatory for US-listed public companies; covers controls over financial reporting, which increasingly means IT controls too.
- SOC 2, a CPA-audited attestation report, common for SaaS and technology vendors, mostly in North America.
- COSO / COBIT, governance frameworks for internal controls and IT governance, usually cited inside an audit rather than certified against directly.
Of everything in the last chapter, this is the one we go deep on: a certifiable, internationally recognized standard for actually running an information security program.
Not a checklist: a management system
ISO 27001 certifies an Information Security Management System (ISMS): the policies, risk process, roles and improvement cycle built around information security, not a fixed list of technical controls.
Clauses 4-10: the mandatory core
These seven clauses are mandatory management requirements. Annex A is the control catalogue you draw specific controls from, next.
Rebuilt for 2022
Fewer, consolidated controls, reorganized and de-duplicated, not weakened.
Organizational controls
37 / 93The largest theme, because most of information security is decisions and process, not hardware.
People controls
8 / 93The smallest theme by count, but people remain both the biggest attack surface and the first line of defense.
Physical controls
14 / 93Physical security is still information security, a stolen laptop is a data breach.
Technological controls
34 / 93The largest technical bucket, but still less than half the standard by control count.
Every 2022 control now carries five tags
Why it matters: these tags make it far easier to map ISO 27001 controls onto other frameworks, like NIST CSF, or pull audit evidence quickly.
Four stages, then a three-year clock
Certification proves the management system exists and works, it does not mean the organization is unhackable.
Everything so far has been global. Now the specific statutes and decrees that actually apply if you operate in Algeria, built up piece by piece since 2009, and accelerating sharply since 2025.
No single omnibus law
Unlike jurisdictions with one comprehensive cybersecurity act, Algeria's framework is a layered stack of statutes, decrees and regulatory bodies, each one adding a piece.
- Statutes (laws), passed by parliament, define offenses, obligations and rights.
- Decrees, issued by the executive, create institutions and operational requirements.
- Regulatory bodies, enforce and interpret the above day to day.
The rest of this chapter walks that stack bottom-up, in the order it was built.
2009 → 2026, at a glance
Where it all started
- Defines ICT-related offenses, Algeria's foundational cybercrime statute.
- Authorizes electronic-communications surveillance for investigating those offenses.
- Created a national committee to combat cybercrime.
The first legal definition of "cybersecurity"
- Article 10, gives Algeria's first formal legal definition of cybersecurity.
- Articles 97 & 119, require telecom operators to secure their networks and protect data confidentiality.
- Article 165, sets penalties for operators who fail to do so.
Algeria's closest equivalent to GDPR
- Requires organizations to declare personal-data processing to ANPDP before it begins.
- The 2025 amendment added a mandatory breach-notification duty: both ANPDP and affected individuals must be told within 5 days of a breach.
Compare this to GDPR's breach-notification rule from Chapter 2, the same underlying idea, on Algeria's own clock.
A narrower, technical mandate
- Mandates technical protection for personal and payment data specifically.
- Applies both while that data is stored and while it is transmitted.
From a committee to a national strategy
The Conseil National de la Sécurité des Systèmes d'Information, under the Ministry of Defense, responsible for national information-security strategy.
Five pillars: protecting state infrastructure, mandatory audits for critical sectors (banking, healthcare, energy), and capacity building.
The newest, and most consequential, rule to date
Applies to all public institutions, and in practice, to critical private-sector operators too: banking, health, energy, telecoms, water, transport and government services.
- Stand up a dedicated cybersecurity unit.
- Appoint a qualified CISO.
- Undergo audits accredited by ASSI.
- Report incidents to DZ-CERT.
- Penalties reach 10,000,000 DZD, with penal sanctions of up to 10 years' imprisonment for serious violations.
Who enforces what
NISR: the National Information Security Repository
- Published in 2020 by the Ministry of Post & Telecommunications.
- A 20-domain best-practices reference, guidance, not a statute.
- Deliberately aligned with GDPR, NIST 800-53, and ISO/IEC 27002.
The bridge back to Chapters 2 and 3, Algeria's own guidance is built on the same global vocabulary this guide started with.
Law tells you what's required. ISO 27001 tells you how to run it. This chapter closes the loop with a practical program checklist.
Algeria and ISO 27001, in practice
- ISO 27001 certification is not yet legally mandatory for Algerian private companies.
- Decree 26-07 pushes public-sector governance hard, and large-client procurement increasingly expects it from SMEs as a de facto entry ticket.
- Local providers now run ISO 27001 Lead Implementer courses inside Algeria; groups like OWASP/CSA Algeria connect Laws 18-07/25-11 directly to ISO 27001 and NISR governance.
- Academic research shows adoption still lags behind quality-management standards locally, despite rising cybercrime losses, a real gap, and a real opportunity.