Module Overview
A. Yahiaoui, Security

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.

Prepared by A. YAHIAOUI, SECURITY
→ Press to begin
Guide Roadmap

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.

Dossier N°01
01
Foundations of GRC

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.

01 / What Is GRC

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.

Governance

Who decides

The structure of authority: who sets policy, who approves exceptions, and who is accountable when something fails.

Risk

What could go wrong

Identifying threats and weaknesses, estimating how much they matter, and deciding how much residual risk is acceptable.

Compliance

Can you prove it

Turning decisions and controls into evidence, the paper trail a regulator or auditor can actually check.

01 / Who's In The Room

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.

Board & executivesSet the organization's risk appetite and hold ultimate accountability for it.
CISOTranslates business risk appetite into an actual security program and budget.
Risk ownersBusiness-unit leads who own specific risks day to day, not just security staff.
Compliance officerTracks legal and contractual obligations, and the evidence that they're met.
Internal auditIndependently tests whether controls actually work, on a regular cycle.
External / certification auditorProvides formal, independent assurance to outside parties, regulators, clients, insurers.
01 / Working Vocabulary

Six terms you'll need for the rest of this guide

Control
A safeguard, technical, physical or procedural, put in place to reduce a specific risk.
Risk appetite
How much risk the organization has explicitly decided it is willing to accept.
Residual risk
What's left over once controls have been applied, never zero.
Audit
A structured, evidence-based check of whether a control actually works as claimed.
Attestation
A formal statement, often signed, that a requirement has been met.
Control owner
The one named person accountable for a single control's day-to-day operation.
Dossier N°02
02
The Global Framework Landscape

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.

02 / Two Kinds Of Rules

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.

02 / The Map

Eight names worth knowing

FrameworkTypeScope
GDPRMandatory regulationEU personal data protection
HIPAAMandatory regulationUS healthcare data
SOXMandatory regulationUS public-company financial controls
PCI DSSMandatory standard (contractual)Payment card data handling
NIST CSFVoluntary frameworkGeneral risk management, 5 functions
SOC 2Attestation reportService & tech providers, mainly North America
COSO / COBITGovernance frameworksInternal controls / IT governance
ISO 27001Certifiable ISMS standardAny organization managing information security
02 / Spotlight

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.

02 / Spotlight

NIST CSF: five functions, one cycle

Voluntary, sector-agnostic, and widely used simply as a common vocabulary for organizing risk work.

01
Identify
Know your assets, data and risks.
02
Protect
Put safeguards in place.
03
Detect
Notice when something's wrong.
04
Respond
Contain and manage an incident.
05
Recover
Restore normal operations.
05 feeds back into 01, this runs continuously, not once
02 / Spotlight

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.
Dossier N°03
03
ISO/IEC 27001 in Depth

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.

03 / The Standard

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.

Plan
Design the ISMS
Scope it, assess risk, decide which controls apply.
Do
Run it
Implement the controls and processes decided above.
Check
Test it
Audit and monitor whether it's actually working.
Act
Improve it
Fix gaps, then repeat the cycle.
03 / Structure

Clauses 4-10: the mandatory core

4Context of the organization
5Leadership
6Planning
7Support
8Operation
9Performance evaluation
10Improvement

These seven clauses are mandatory management requirements. Annex A is the control catalogue you draw specific controls from, next.

03 / Annex A

Rebuilt for 2022

2013 EDITION
114
controls across 14 domains
→
2022 EDITION
93
controls across 4 themes

Fewer, consolidated controls, reorganized and de-duplicated, not weakened.

03 / Annex A · Theme 1 of 4

Organizational controls

37 / 93

The largest theme, because most of information security is decisions and process, not hardware.

Policy for information security Roles & responsibilities Supplier relationships Threat intelligence Cloud service security Business continuity readiness
03 / Annex A · Theme 2 of 4

People controls

8 / 93

The smallest theme by count, but people remain both the biggest attack surface and the first line of defense.

Screening Terms of employment Security awareness & training Disciplinary process Remote working Confidentiality agreements
03 / Annex A · Theme 3 of 4

Physical controls

14 / 93

Physical security is still information security, a stolen laptop is a data breach.

Perimeter security Entry controls Monitoring Equipment siting & protection Secure disposal of media
03 / Annex A · Theme 4 of 4

Technological controls

34 / 93

The largest technical bucket, but still less than half the standard by control count.

Access control Cryptography Secure coding Configuration management Data masking Logging & monitoring Network segmentation
03 / What Changed Under The Hood

Every 2022 control now carries five tags

01Control type
02Information security properties (confidentiality, integrity, availability)
03Cybersecurity concepts
04Operational capabilities
05Security domains

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.

03 / Getting Certified

Four stages, then a three-year clock

Stage 1
Gap assessment
Where do we stand against the standard, today?
Stage 2
Build the ISMS
Remediate gaps, write policies, run risk assessments.
Stage 3
Certification audit
An accredited certification body reviews documents, then operations.
Stage 4
Certificate issued
Valid three years, with annual surveillance audits in between.

Certification proves the management system exists and works, it does not mean the organization is unhackable.

Dossier N°04
04
Algeria's Legal & Regulatory Stack

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.

04 / The Big Picture

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.

04 / Timeline

2009 → 2026, at a glance

2009
Law 09-04, cybercrime foundation
2016
Law 16-02 amends 09-04
2018
Laws 18-04, 18-05, 18-07, telecom, data-at-rest, data protection
2020
Decree 20-05 creates CNSSI
2025
Law 25-11 (breach notice) + Decree 25-321 (national strategy)
2026
Decree 26-07, operational enforcement
04 / The Foundation
Loi N° 09-04 · 5 Août 2009, amendée par Loi 16-02, 2016
Cybercrime & Electronic Surveillance

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.
04 / Telecom Law
Loi N° 18-04 · 13 Mai 2018
General Rules on Post & Electronic Communications

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.
04 / Data Protection
Loi N° 18-07 · 10 Juin 2018, amendée par Loi 25-11, 24 Juillet 2025
Personal Data Protection Law

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.

04 / Securing The Data Itself
Loi N° 18-05 · 10 Mai 2018
Data-at-Rest and Data-in-Transit Protection

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.
04 / Building The Strategy Layer

From a committee to a national strategy

Décret Présidentiel N° 20-05 · 2020, amendé 2025
Creates CNSSI

The Conseil National de la Sécurité des Systèmes d'Information, under the Ministry of Defense, responsible for national information-security strategy.

Décret Présidentiel N° 25-321 · 30 Déc 2025
National Cybersecurity Strategy 2025-2029

Five pillars: protecting state infrastructure, mandatory audits for critical sectors (banking, healthcare, energy), and capacity building.

04 / The Headline Rule
Décret Exécutif N° 26-07 · 7 Janvier 2026
Cybersecurity Governance, Operational Enforcement

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.
04 / Regulators

Who enforces what

ANPDP
Data protection authority, Law 18-07 / 25-11.
ASSI
Accredits security audits under Decree 26-07.
CNSSI
Ministry of Defense body, national ISS strategy.
DZ-CERT
National incident response and reporting point.
ARPCE
Telecom regulator.
DGSN Cybercrime Unit
Police-level cybercrime investigation.
04 / Guidance, Not Law

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.

Dossier N°05
05
Bringing It Together

Law tells you what's required. ISO 27001 tells you how to run it. This chapter closes the loop with a practical program checklist.

05 / Where They Meet

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.
05 / Practical Synthesis

Building a GRC program: six steps

01
Map obligations
Which Algerian laws and decrees actually apply to your organization?
02
Choose your backbone
Pick a voluntary framework, ISO 27001 or NIST CSF, to structure the program.
03
Assign ownership
Name a CISO and control owners; set risk appetite at the top.
04
Build the ISMS
Policies, risk assessments, Annex A controls via a Statement of Applicability.
05
Get audited
Internal audit first, then an accredited certification body if pursuing ISO 27001.
06
Stay reportable
Know your DZ-CERT incident duty and your 5-day breach-notification clock.
Closing

Recap

01Governance, risk and compliance are three distinct, ownable jobs.
02A handful of global frameworks, mandatory and voluntary, set the vocabulary everyone borrows.
03ISO 27001 certifies a management system, built on 93 Annex A controls across 4 themes.
04Algeria's stack has no single law, it's built from statutes, decrees and regulators layered since 2009.
05A working program maps obligations first, then builds the ISMS to satisfy them.
Data authority → ANPDP Incident reporting → DZ-CERT Official texts → JORADP The standard → iso.org
End of Module A. YAHIAOUI, SECURITY