NordChem's First Line of Defence
A hands-on, gamified case study — build an ISMS from scratch and achieve ISO 27001 compliance using Cyberday.
Before you start — Create your Cyberday account
This module uses a live Cyberday workspace embedded on the right side of your screen. The signup page cannot be embedded, so you need to create your account in a separate tab first. Once signed in there, the embedded panel in this module will work automatically.
- Click the button below — it opens app.cyberday.ai in a new tab.
- Choose "Sign up" and register with your email.
- Complete the email verification and finish the short signup form.
- Leave that tab signed in, then return here.
Your Scenario
NordChem Oy — Company Profile
"Welcome aboard. I should be honest with you — your predecessor left behind almost no documentation. There is no formal information security policy, no risk register, and no clear ownership of IT assets. Our ERP, process control network, and customer portal all sit on the same flat network segment."
"Oh, and last autumn a phishing attack compromised two employee accounts. It was never properly documented or reported to senior management. I flagged it at the time but... well, you can see the situation."
"Thank you for coming in. I received something from our largest customer this morning that I need you to look at urgently."
To: Maria Lindqvist <m.lindqvist@nordchem.fi>
Date: 6 January 2026, 09:14 CET
Dear Ms Lindqvist,
As part of our updated supplier qualification process, we require all Tier 1 suppliers to demonstrate ISO/IEC 27001 certification or provide evidence of an active Information Security Management System (ISMS) by the next contract renewal date.
Our records show NordChem's current contract is up for renewal on 30 June 2026. The contract value is €2.1 million annually. Without evidence of ISO 27001 compliance, we will unfortunately not be able to proceed with the renewal.
Please let us know your plans at your earliest convenience.
Thomas Braun
Head of Supplier Quality, Schneider Automotive GmbH
"This is our largest contract. I need you to present a concrete action plan to the board within two weeks. Can you make this happen?"
Learning Objectives
ISMS Fundamentals — Learn Before You Build
What is an ISMS?
An Information Security Management System (ISMS) is a structured set of policies, processes, and controls that an organisation uses to manage information security risks systematically. Think of it as the "operating system" for how your company protects its data, systems, and people.
An ISMS is not a one-off project or a single document. It is a living system that follows the Plan–Do–Check–Act (PDCA) continuous improvement cycle. This means you plan your security measures, implement them, monitor their effectiveness, and continuously refine them.
Who uses an ISMS?
Any organisation that handles sensitive information — customer data, trade secrets, employee records, financial systems — benefits from an ISMS. In practice, the ISMS is managed by a security team or CISO, but it involves everyone in the organisation: from the CEO who approves the security policy, to the warehouse worker who follows physical security rules, to the developer who follows secure coding practices.
Typical roles in an ISMS include a management sponsor (CEO/board), the ISMS owner (CISO or security manager), theme/area owners (IT lead, HR lead, facilities), and all employees who follow guidelines.
How is an ISMS used in practice?
In daily operations, an ISMS translates into concrete activities: documenting your IT assets and who owns them, assessing risks to your information, creating security policies and distributing them to staff, handling incidents through a structured process, reviewing and improving your security posture regularly, and demonstrating compliance to auditors and customers.
ISO/IEC 27001:2022 — The Standard
ISO 27001 is the international standard that defines requirements for establishing, implementing, maintaining, and continually improving an ISMS. It is published by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC).
The 2022 revision has two main parts:
Clauses 4–10 (Mandatory requirements): These 23 requirements cover the management system itself — context of the organisation, leadership commitment, planning, support, operation, performance evaluation, and improvement. Every organisation seeking certification must meet all of these.
Annex A (Security controls): 93 controls covering specific security topics like access control, cryptography, physical security, and incident management. These are grouped into 4 themes: Organisational (37), People (8), Physical (14), and Technological (34). Together with the clauses, Cyberday tracks 116 requirements total.
The role of ISO 27002
While ISO 27001 tells you what controls to implement, ISO 27002 is the companion standard that tells you how to implement them. It provides detailed implementation guidance for each of the 93 Annex A controls. When you're working in Cyberday and see a task linked to an Annex A control, the implementation guidance you'll find is based on ISO 27002. Think of 27001 as the "requirements checklist" and 27002 as the "implementation cookbook."
Key Terms Reference
| Term | Meaning |
|---|---|
| ISMS | Information Security Management System — the full set of policies, processes and controls |
| PDCA | Plan–Do–Check–Act: the continuous improvement cycle underpinning ISO 27001 |
| Compliance score | In Cyberday: percentage showing how many framework requirements are addressed by implemented tasks |
| Assurance value | In Cyberday: measures how much evidence exists to prove your compliance score is accurate |
| Control / Requirement | A measure that modifies or manages a risk — a policy, process, or technical safeguard |
| Risk treatment | The decision to accept, mitigate, transfer, or avoid a risk |
| Statement of Applicability | Document listing which requirements apply and their implementation status — required by clause 6.1.3 |
| Theme | Cyberday's topic-based groupings (e.g., Technical cyber security, Risk management) that organise tasks |
| Task | The main content type in Cyberday — a specific action linked to one or more framework requirements |
| Documentation | Assets, records, and stakeholders that need systematic tracking (e.g., data systems, risks, incidents) |
| Guideline | Security rules distributed to employees for acceptance via the Guidebook view |
Cyberday's Platform Structure
Cyberday (app.cyberday.ai) is a cloud-based ISMS platform. Its hierarchy works like this: you activate frameworks (e.g., ISO 27001), which generate tasks — the main content type. Tasks are organised into themes (permanent topic-based categories like "Technical cyber security" or "Risk management and leadership"). Each task links to one or more framework requirements.
Tasks have supporting content that serves as implementation evidence: documentation (assets, records, stakeholders), guidelines (rules distributed to employees), and reports (auto-generated documents like compliance reports). Together, these elements build your compliance score and assurance value.
Set Up NordChem & Complete Onboarding
"I've set up a trial account for you at app.cyberday.ai. The credentials are in your inbox. Let me know if you need anything — I've been wanting someone to take the lead on this for a long time."
-
Go to app.cyberday.ai and sign in with the credentials provided by your instructor.If you are creating a fresh trial account, click Start free trial and register with your email.
-
Follow the setup wizard to create your organisation. Name it NordChem Oy and choose the industry that best fits a chemicals manufacturer.The industry profile helps Cyberday tailor its recommendations — this is part of profiling your organisation for relevant framework coverage.
-
After you have created your organization, you will be taken to the "Get Started" onboarding. Choose and activate your first framework: ISO 27001:2022 3: Full.Selecting the framework tells Cyberday which requirements to track and generates the initial ISMS structure.
-
Now you have created a ISMS baseline and chosen the first framework. You can come back to the onboarding flow from the left navigation at any point. Let's move on to first tasks.
- Every ISMS starts with understanding your organisation's context — size, industry, and risks shape your controls
- Selecting a framework before drafting ensures Cyberday generates relevant tasks and requirements
- The onboarding checklist gives you a clear path from setup to your first compliance baseline
Explore the ISO 27001 Framework & Themes
"Jarkko, I've got ISO 27001 activated from onboarding. Now I want to understand how Cyberday actually structures the work — themes, tasks, compliance levels. Can you walk me through it?"
"Sure. Head to the Frameworks page first — you'll see the framework card with compliance levels and a goal score. Then check out the THEMES section in the sidebar. Those are Cyberday's own practical categories, not the Annex A structure. They group related tasks together so day-to-day work is easier."
-
Close the onboarding from the bottom and in the left sidebar, click Frameworks. You'll see "Edit frameworks" and list of active frameworks.Cyberday supports many frameworks (ISO 27001, NIS2, ISO 9001, etc.) that can be active simultaneously.
-
Click "Edit frameworks" and verify ISO 27001:2022 is active (toggled ON from your onboarding). Explore the framework card — it shows compliance levels and a goal score.Don't activate NIS2 or other frameworks yet — those may be covered in future case studies.
-
Now look at the left sidebar under the THEMES heading. These are Cyberday's own practical topic-based categories — not the ISO 27001 Annex A categories. Click Show more themes to see the full list.Themes like "Risk management and leadership", "System management", "Incident management" group related tasks for easier day-to-day work.
-
Click on any theme to see tasks inside it. Notice each task shows a status, a link to the underlying ISO requirement, and an assurance value. Take note of your starting Compliance score: 0% — this is your baseline.
-
Browse the "Edit frameworks" list. Notice that Cyberday supports multi-framework compliance: many tasks connect to requirements across multiple frameworks, so work done for ISO 27001 can also count towards NIS2 or other standards.This "smart mapping" means you don't have to redo work when you activate a new framework later.
- ISO 27001:2022 organises 93 controls into themes that map directly to Cyberday's navigation
- Multi-framework mapping means one task can satisfy multiple standards, reducing duplicate work
- Compliance levels help you set realistic targets and track progress over time
Draft Your ISMS & Configure the Security Policy Report
"Quick update — the board meeting has been moved to next Friday. I'll need your action plan by then. How are things going?"
"Good progress, Maria. I've activated ISO 27001 in Cyberday and explored the framework structure. Today I'm going to draft our ISMS and set up the Information Security Policy report — the most fundamental document an auditor will ask for."
-
Go to Get started in the sidebar. Click the "Draft your ISMS" button on the third onboarding step.Cyberday generates a draft ISMS based on your org profile and active framework — pre-filling policies and tasks with best-practice templates.
-
Once drafting completes, navigate to Reporting in the sidebar. Find the "ISMS description and scope" report under "Document" header. Generate the report and open it. Look at the report and see how you can define ISMS scope.The scope defines the boundary of your ISMS — what's included and what's not. Auditors check this carefully.
-
Now find the "Information security policy — report publishing, informing and maintenance" task. Navigate via the Risk management and leadership theme in the sidebar, or search in All tasks.This task addresses ISO 27001 requirement 5.1 "Policies for information security."
-
Open the linked report. Before you can assign an owner, you must first activate the report. Then set yourself (CISO) as the Owner. This can be done from top left under "Select owner". Then select "Assign user" and pick yourself.Setting an owner ensures someone is accountable for keeping the report up to date and reviewing it regularly.
-
As you can see the policy is auto-generated, but these need to be customized to your company's context. At this stage we can leave this as a template, but before you move on set a review cycle for the policy. This can be done from the top right clicking the three dots. Choose "Enable review". For this policy let's choose Yearly.Regular reviews ensure policies stay relevant as the organisation evolves. ISO 27001 expects policies to be reviewed at planned intervals.
- The ISMS description and scope report defines what your security system covers — this is what auditors check first
- Auto-generated policies save time, but must be customised to reflect your actual operations
- Setting report owners and review cycles creates accountability and keeps documentation current
Explore the Compliance Report & Requirement Structure
"Jarkko, the ISMS draft is done and the security policy is configured. Now I need to understand the full compliance picture — how many requirements we're tracking, how they're structured, and what the SoA looks like."
"Good thinking. The compliance report is where everything comes together. You'll see the full and condensed views — the condensed one is basically your Statement of Applicability. Schneider's auditor will want to see that first."
-
In the left sidebar, go to Reporting. Find and open the ISO 27001 compliance report.It opens in "Full compliance view" by default, showing the overall score and requirement breakdown by theme.
-
Explore the Full compliance view. Note how requirements are grouped by categories (matching Cyberday's theme structure). Click on any requirement to see which tasks are linked to it.Remember: requirements are from the framework; tasks are your implementation actions. A requirement may have multiple tasks.
-
At the top of the report, click the "Condensed SoA view" button. This switches to a table showing: ID, Requirement name, Status, Tasks, Applicability, Description, Assurance.The SoA (Statement of Applicability) is required by ISO 27001 clause 6.1.3 — it's one of the first documents an auditor requests.
-
Scroll through the SoA table. Notice it starts with mandatory clauses (requirements 4.1 to 10.2) followed by Annex A controls grouped by category: 5 (Governance), 6 (People), 7 (Physical), 8 (Technological).The Annex A categories (Organisational, People, Physical, Technological) are ISO's own groupings — different from Cyberday's practical Themes.
- The Statement of Applicability (SoA) is a mandatory ISO 27001 document linking every Annex A control to your ISMS
- Requirements connect to tasks — understanding this link shows how daily work translates to compliance evidence
- The Full vs Condensed SoA views serve different audiences: internal teams vs external auditors
Explore the Taskbook & Plan Your First Actions
"The board will want to see specifics — not just 'we'll implement ISO 27001.' They need to know: what are we doing first, who is responsible, and when will each step be done?"
"I'll use the Taskbook to build our action plan. Cyberday has a three-phase roadmap that keeps us focused — foundation first, then systematic management, then continuous improvement. Let me map out Phase 1 priorities."
Phase 1 — Building your ISMS foundation: Establish ISMS team & assign roles, improve compliance score to initial level, create & assign your asset inventory
Phase 2 — Running systematic information security management: Start risk management, create personnel security guidelines, create partner inventory, build key reports, improve assurance to intermediate
Phase 3 — Building continuous ISMS improvement: Handle incidents, conduct management review, perform internal audit, publish Trust Center, start vendor assessments
-
Click Taskbook in the top navigation. This is your personal view — "My cyber security responsibilities" — showing only tasks assigned to your account.For the full organisation view, use "All tasks" in the sidebar.
-
Notice the task status categories: Needs attention (highest priority — blocking compliance), Pending, Active, and Done."Needs attention" tasks are blocking your compliance progress — start with these.
-
Go back to the dashboard from the top and navigate to All tasks (sidebar). Browse the full task list. Look for foundational tasks from the Risk management and leadership theme — these are the building blocks other tasks depend on.Key Phase 1 foundations: ISMS policy, roles and responsibilities, asset inventory. These must come before risk treatment.
-
Identify 10 priority tasks for the first 8 weeks (Phase 1). Consider assigning owners — at least 3 tasks should go to other team members (IT Manager, HR Lead, Operations Lead). Set realistic due dates.Phase 1 focus: team setup, initial compliance, asset inventory. Don't jump ahead to risk management or incident handling yet.
- Task statuses (Needs attention, Pending, Active, Done) create a natural priority queue for your compliance work
- Phase 1 focuses on governance foundations — roles, policies, and asset inventory come before technical controls
- Distributing task ownership across the organisation prevents CISO bottleneck and builds shared accountability
Task 6 — Build NordChem's Asset Inventory & Documentation
- In the left sidebar under CONTENT TYPES, click All documentation. Browse the different documentation lists available.You'll see lists grouped by type — asset lists (data systems, physical assets, etc.) and record lists (risks, incidents, etc.).
- Open the Data systems under the Asset documentation list. Add NordChem's key systems: SAP ERP, SCADA/OT network, Microsoft 365, and Customer Portal. Cyberday has a pre-made library, but add these from the bottom of the list and manually add these key systems. For each, set an owner and fill in basic details.Asset owners are the people responsible for the system — e.g., the IT Manager might own SAP ERP, the Operations Lead owns SCADA.
- Now from the left navigation navigate to theme System management that involves asset documentation. Open the theme and open Documentation under the theme. Notice how it's pre-linked to the data systems documentation table.This link is the key — the documentation serves as evidence that the task has been implemented. Adding assets here increases the task's assurance value.
- Browse the Risk documentation list. This is where NordChem's risk register will live. Note that it's currently empty — risk management belongs to Phase 2, so leave this for later.The roadmap phases recommend building the foundation first (team, compliance, assets) before diving into risk management.
- An asset inventory is the foundation of risk management — you cannot protect what you have not documented
- Assurance value measures evidence completeness, not just whether a task checkbox is ticked
- Linking data systems to themes creates traceability from assets to the controls that protect them
Task 7 — Create Personnel Security Guidelines
- Switch to the Guidebook view using the top navigation bar. This is what NordChem's 210 employees will see — their personal security responsibilities and guidelines to accept.The Guidebook is the "employee experience" of the ISMS. It's designed to be simple and clear, not overwhelming.
- Switch back to the Organisation dashboard (top nav). In the sidebar, under themes click Email and phishing. Then click "Guidelines" and browse the available guidelines.Cyberday provides pre-made guideline examples that you can activate, or you can create custom ones.
- Activate at least two guidelines relevant to NordChem: one on phishing/email security theme (critical given the recent incident!) and one on mobile device use theme.Remember the phishing attack that compromised two employee accounts? Guidelines are how you prevent recurrence by training all staff.
- Guidelines are employee-facing documents that create auditable proof of security awareness
- Activating guidelines in relevant themes (phishing, mobile) directly addresses your organisation's real risks
- Personnel controls often require the least technical effort but deliver the highest risk reduction
Task 8 — Generate the SoA & Map Your Certification Roadmap
- Return to the ISO 27001 compliance report. Click the "Update data" button on the left. Switch to the Condensed SoA view. Note the document title shown at the top.This is the document the auditor will ask for first. It lists every requirement and its status.
- Review the SoA table. Locate requirement 5.1 (Policies for information security). Check its current status — has it changed from your initial work?If you completed Task 3 properly, this should show some progress compared to the initial "Applicable & Not implemented" status.
- Review your overall compliance score on the dashboard. Compare it to the 0% baseline from Task 2. Even small progress demonstrates that the ISMS is actively being built.The score won't be high yet — that's expected. What matters is demonstrating a structured approach and active progress.
- Map your 2-week plan against the three-phase roadmap. In your first 2 weeks you should aim to complete Phase 1 goals: team & roles established, initial compliance score, asset inventory created. The phases below will test your understanding of what belongs where.
Case Study Complete!
You've built NordChem's ISMS foundation — from understanding ISMS concepts to generating a real Statement of Applicability and mapping a three-phase certification roadmap. The CEO now has a credible plan for the German customer.
What's next?
- The SoA is your primary certification evidence — auditors verify every claim against actual controls
- A phased roadmap (Foundation, Systematic Management, Continuous Improvement) makes certification achievable
- Honest status reporting builds credibility — marking incomplete controls as "Implemented" risks disqualifying your audit