Smart devices are sold with very different levels of security, and buyers have almost no way to tell them apart at the shelf. Singapore's Cybersecurity Labelling Scheme for IoT, known as CLS(IoT), answers that with a tiered label from one to four asterisks, issued by the Cyber Security Agency of Singapore (CSA) through its Cybersecurity Certification Centre (CCC). It matters beyond Singapore because the label is linked by mutual recognition to schemes in Finland, Germany, the Republic of Korea and the UK, so one assessment can open several markets. This guide covers scope, the four tiers, the scheme documents, timelines, fees, how the label is revoked, what it means for device credentials and automated clients, and a compliance path for manufacturers and importers. It is written for product security leads, compliance teams and procurement staff. Status checked against CSA pages on 27 October 2026.
Key takeaways
- Voluntary, with one exception: CSA describes CLS(IoT) as "a voluntary scheme, for a start", but Wi-Fi routers sold for local use in Singapore had to reach at least Level 1 by 2 May 2022 under IMDA requirements.
- Four cumulative tiers: Level 1 is an ETSI EN 303 645 baseline, Level 2 adds full ETSI EN 303 645 mandatory provisions, Level 3 adds secure lifecycle evidence and binary analysis, and Level 4 adds penetration testing by an approved lab.
- The label expires with your support period: validity equals the period the manufacturer commits to security updates, capped at three years, and the support period must be published on the manufacturer's website.
- Mutual recognition saves rework: Germany's IT Security Label maps to Level 2, Finland's label and Korea's CIC Basic map to Level 3, and UK PSTI compliance maps to Level 1.
- Revocation is the enforcement lever: false declarations, undisclosed known vulnerabilities and label misuse can lead CCC to revoke the label and move the product to its historical list.
Scope: who and what is covered
CLS(IoT) launched on 7 October 2020. It first covered Wi-Fi routers and smart home hubs, and on 21 January 2021 CSA extended it to all categories of consumer IoT devices, naming IP cameras, smart door locks, smart lights and smart printers as examples. The scheme overview (CCC SP-151-1 v1.4) is explicit that the label signals basic security hygiene for consumer devices, not formal security assurance, and points enterprise, industrial and healthcare buyers to higher assurance schemes.
| Party | Role in the scheme | Main duties |
|---|---|---|
| Cybersecurity Certification Centre (CCC), under CSA | Owns and manages the scheme, approves declarations, awards and revokes labels | Keeps the Labelled Product List (LPL), handles appeals, investigates reported vulnerabilities |
| Manufacturer (or importer for Level 1 routers) | Applicant and label holder | Declaration of Conformity, supporting evidence, vulnerability disclosure programme, published support period, change notification |
| Approved testing laboratory (TL) | Reviews declarations and performs tests | Since 1 April 2025 must review Level 1 and 2 applications; runs binary analysis (Level 3) and penetration tests (Level 4) |
| IMDA | Telecoms equipment regulator | Residential gateway specification (IMDA TS RG-SEC) whose compliance qualifies routers for Level 1 |
| Consumers and enterprise buyers | Users of the label | Check the QR code against the LPL before purchase |
A sister scheme, CLS for Medical Devices or CLS(MD), launched on 16 October 2024. It was developed by CSA with the Ministry of Health, the Health Sciences Authority and Synapxe, is also voluntary, and covers medical devices under the First Schedule of the Health Products Act that handle personal or clinical data or connect to other devices, systems or services. Its four levels end with third party binary analysis plus penetration testing (Level 3) or security evaluation (Level 4). Device makers should treat it separately from CLS(IoT); see the Medical Device Security Guide.
Key obligations
Each level is shown by a number of asterisks and equals the highest tier completed. Tiers are cumulative: a Level 3 applicant goes through Tiers 1, 2 and 3.
| Level | Tier requirement (CSA wording, summarised) | Who checks it | Fee from 1 April 2025 (S$) |
|---|---|---|---|
| Level 1 (*) | Baseline from ETSI EN 303 645: no universal default passwords, security updates available, a way to manage vulnerability reports | Manufacturer Declaration of Conformity, reviewed by an approved TL | 57 |
| Level 2 (**) | Adherence to an international standard covering all mandatory requirements of ETSI EN 303 645 | Declaration of Conformity, reviewed by an approved TL | 142 |
| Level 3 (***) | Security built into the development lifecycle per the IMDA IoT Cyber Security Guide (threat modelling, secure engineering, secure supply chain, security testing), plus automated binary analysis of device software | Approved TL | 633 |
| Level 4 (****) | Penetration testing for basic resistance to common attacks, under the Tier 4 Minimum Test Specifications | Approved TL | 2,347 |
| Mutual recognition route | Device already holds the Finnish, German or Korean label | CCC | 51 |
Fees are from CSA's updates page and the Fee Schedule (CCC SP-151-8 v1.1); lab charges are separate. Fees are not refunded on withdrawal, suspension or termination.
Obligations that continue after the label is awarded
- Keep meeting the level: the labelled product must continue to meet the requirements of its level (SP-151-1 section 13.5.1(a)).
- Vulnerability disclosure: run a vulnerability disclosure programme and notify CCC of reported vulnerabilities as early as possible, with impact, remediation plan and timeline (section 8.1.1). This is the same duty that underpins ETSI EN 303 645 provision 5.2.
- Published support period: the defined support period, the minimum time you agree to provide security updates, must be published at least on your website (section 8.2.2).
- Change notification: tell CCC immediately about changes that could affect the product's ability to meet requirements. Major changes that invalidate earlier results need retesting for Level 3 and 4; minor updates and patches do not invalidate the label (sections 10.1.2 and 10.1.3).
- Label use: use the label exactly as issued, show the LPL product name and model wherever it appears, affix it to packaging or product within six months of issue, and never imply CSA endorsement or warranty (sections 13.4 and 14.1).
- Binary scans and SBOM: since September 2023, Level 3 and 4 binary scans cover known vulnerabilities and components declared in the SBOM, so the SBOM you submit must be accurate.
Timeline and current status
| Date | Event |
|---|---|
| 7 October 2020 | CLS launched (application fees waived until 6 October 2021) |
| 12 October 2020 | IMDA publishes Residential Gateway security specification; compliant home routers qualify for Level 1 |
| 21 January 2021 | Scheme extended to all consumer IoT device categories |
| 2 May 2022 | Date by which routers sold for local use had to attain at least Level 1 (per CSA registration page) |
| 20 October 2022 | Level 2 tied to an international standard; Level 3 adds lifecycle security and binary analysis |
| 22 September 2023 | Assessment Methodology v1.0, applications moved to the GoBusiness Portal, Declaration of Conformity replaces checklist |
| 19 March 2024 | Mutual recognition arrangement with the Connectivity Standards Alliance |
| 16 October 2024 | CLS(MD) for medical devices launched |
| 1 January 2025 | Korea MRA takes effect (CIC Basic and CLS Level 3 recognised both ways) |
| 1 April 2025 | Approved TL review mandatory for Level 1 and 2; revised fees; Home Gateway methodology v1.1 for routers |
| 21 May 2026 | Latest CSA updates page revision noted at time of checking |
The current core documents listed by CSA are the Overview of the Scheme (SP-151-1 v1.4), Scheme Specifications (SP-151-2 v1.4), Requirements for Testing Laboratory (SP-151-3 v1.1), Assessment Methodology (SP-151-4 v1.2), the Home Gateway methodology (SP-151-4A v1.1), Tier 4 Minimum Test Specifications (SP-151-5 v1.1) and the Declaration of Conformity templates (SP-151-7 and 7A). Versions change, so download them fresh at the start of each project.
Mutual recognition
| Partner | Instrument | Equivalence |
|---|---|---|
| Finland (Traficom) | MoU | Finnish Cybersecurity Label recognised as CLS Level 3; CLS Level 3 and above recognised by Finland; dual label via single application for Level 3 and 4 |
| Germany (BSI) | MRA | IT Security Label recognised as Level 2 and vice versa for Level 2 and above; home gateways must meet the Home Gateway methodology |
| Republic of Korea (KISA) | MRA, effective 1 January 2025 | CIC Basic and above recognised as Level 3, and Level 3 and above as CIC Basic |
| United Kingdom | MoU | PSTI Statement of Compliance recognised as Level 1; see the UK PSTI Act Guide |
| Connectivity Standards Alliance | MRA, 19 March 2024 | Mutual recognition of consumer IoT cybersecurity labels |
A label obtained through mutual recognition cannot itself be used to apply for another scheme's label. For the wider picture of product security law, see the Product Security Laws Map.
Enforcement and penalties
CLS(IoT) is an administrative scheme, so its enforcement is about the label rather than fines. CSA's scheme documents do not set out monetary penalties. The levers in SP-151-1 chapter 15 are:
- Revocation (section 15.1.1): grounds include breach of publication terms, known vulnerabilities not disclosed, failure to take corrective measures within a grace period, label misuse, misrepresentation of testing or labelling, TL conflicts of interest, no longer meeting label conditions, and false statements or declarations. Use of the label must stop immediately and the product moves from the LPL to the historical product list.
- Malware findings: under SP-151-2, if malware is confirmed by two scanners during binary analysis, CCC reserves the right to take action against the manufacturer.
- Suspension and termination of applications (section 15.2): no testing activity for more than eight consecutive weeks, no updated work plan within 30 days of a request, unpaid fees, or an application running over one calendar year.
- Appeals (chapter 19): first with the responsible certifier, then to the Head of CCC, whose decision is final.
Routers are the exception to "voluntary": the Level 1 requirement for locally sold routers sits within IMDA's equipment registration and labelling rules, and routers must carry both the IMDA compliance label and the CSA label. Check IMDA's current requirements for the consequences of selling non-compliant equipment; this guide does not summarise them.
What it means for AI agents and non-human identities
Every labelled device is itself a non-human identity with credentials, update channels and cloud connections, and increasingly it is driven by software clients rather than people. The scheme does not mention AI agents, but several of its requirements land directly on machine identity design:
- Default credentials: Tier 1 targets universal default passwords. That covers the device's local admin and API credentials, not just the web login. Unique per device secrets or certificates provisioned at manufacture are the robust answer; see the IoT Device Identity with TPM and DICE Guide.
- Companion cloud and app tokens: smart home devices are typically controlled through a vendor cloud using OAuth tokens or API keys. Voice assistants, home automation hubs and now AI agents hold those tokens. Lifecycle evidence at Level 3 (threat modelling, secure engineering) should cover token scope, expiry and revocation for third party integrations, even though the label assesses the device.
- Update signing keys: the support period promise depends on a secure update channel. Protect firmware signing keys as tier 0 secrets and log every signing event; see the IoT Secure Firmware Update Guide (SUIT, signed OTA).
- Agent driven control: where an AI assistant can unlock a smart lock or change camera settings through an API, the device's local authorisation model is what limits damage if the agent is manipulated. Penetration testing at Level 4 focuses on logical interfaces, which makes those APIs part of the test scope.
- Enterprise use: the label is consumer hygiene. Organisations deploying labelled devices at scale still need device inventory and credential governance; see the Device and IoT Identity Guide.
Compliance steps
- Choose the target level by market: Level 1 for routers and baseline consumer products, Level 2 if you also want the German label, Level 3 if you sell into Finland or Korea, Level 4 where you want to show tested resistance. Selecting the level first avoids paying twice for testing.
- Run a gap assessment against ETSI EN 303 645: map each mandatory provision to evidence (password scheme, VDP URL, update mechanism, support period statement). Reuse PSTI or EU evidence where you already have it; the EU Cyber Resilience Act Guide covers the EU obligations that overlap.
- Engage an approved testing laboratory early: since 1 April 2025 every Level 1 and 2 application needs TL review, and Level 3 and 4 need TL testing. Pick from CSA's approved laboratory list.
- Prepare the Declaration of Conformity and evidence pack: use the current SP-151-7 template (SP-151-7A for home gateways) and CSA's supporting evidence slide template. For Level 3, include threat model, secure development process, supply chain controls and an accurate SBOM.
- Fix binary analysis findings before submission: run your own scans of the firmware image for known CVEs and leftover credentials so the TL scan is a confirmation, not a discovery. Significant vulnerabilities lead CCC to encourage withdrawal.
- Apply through the GoBusiness Portal and pay the fee: track the application so it does not idle for eight weeks or exceed a year, either of which triggers termination.
- On award, publish and label correctly: publish the support period, affix the label within six months, keep the model name with every label use, and check the QR code resolves to your LPL entry.
- Operate the label: run the VDP, notify CCC of reported vulnerabilities, assess each firmware release as minor or major, and request renewal up to six months before expiry. An expired label cannot be renewed; it needs a new application.
Choosing between levels
Small manufacturers selling only in Singapore usually start at Level 1 or 2 because they are declaration based and cheap. Larger brands selling across Asia and Europe benefit from Level 3, since it maps to Finland and Korea and forces lifecycle discipline that the EU Cyber Resilience Act also expects. Level 4 is worth it for security sensitive categories such as door locks and cameras, where buyers compare labels and where a penetration test is likely to find interface weaknesses a declaration would miss.
Framework mapping
| CLS(IoT) element | NIST CSF 2.0 | NIST SP 800-53 Rev 5 | Related baseline |
|---|---|---|---|
| No universal default passwords | PR.AA (identity management) | IA-5 Authenticator Management | ETSI EN 303 645 provision 5.1; NIST IR 8259 |
| Vulnerability disclosure programme | ID.RA-08 | RA-5 Vulnerability Monitoring and Scanning | ETSI EN 303 645 provision 5.2 |
| Security updates and support period | PR.PS-02 | SA-22 Unsupported System Components | ETSI EN 303 645 provision 5.3; UK PSTI |
| Secure lifecycle and supply chain (Level 3) | GV.SC-05 | SR-3 Supply Chain Controls and Processes | IMDA IoT Cyber Security Guide |
| Binary analysis and penetration testing (Levels 3 and 4) | ID.RA-01 | SA-11 Developer Testing and Evaluation | SP-151-5 Minimum Test Specifications |
| Secure default configuration | PR.PS-01 | CM-6 Configuration Settings | IMDA TS RG-SEC for routers |
Common failure patterns
- Treating the label as permanent: validity ends with the declared support period or three years, whichever is shorter. Teams that do not diarise the six month renewal window lose the Label ID and start again.
- Undeclared vulnerabilities: knowing about a vulnerability and not disclosing it is a revocation ground. Route VDP reports to the person who owns CCC notification.
- Inaccurate SBOMs: binary scans compare what is in the image with what you declared. Stale SBOMs create findings and delays.
- Hard coded service credentials: a unique web password does not help if telnet, debug or cloud API credentials are shared across the fleet. Binary analysis is designed to find these.
- Major change shipped as a patch: a rewritten network stack or new remote interface is a major change for Level 3 and 4 products and needs retesting.
- Marketing overreach: claiming the device is "CSA certified secure" or endorsed by CSA breaches label use conditions.
Practitioner checklist
- Confirm target markets and pick the CLS level that unlocks the mutual recognition you need.
- Download the current SP-151 publications and fee schedule from CSA at project start.
- Map ETSI EN 303 645 mandatory provisions to evidence and close gaps, starting with default credentials.
- Publish a vulnerability disclosure policy and the defined support period on your website.
- Contract an approved testing laboratory before drafting the Declaration of Conformity.
- Generate an accurate SBOM and pre-scan firmware for known CVEs and embedded secrets.
- Protect firmware signing keys and cloud API credentials as privileged non-human identities.
- Set a change classification rule (minor or major) for every firmware release of a labelled product.
- Diarise renewal six months before expiry and assign an owner for CCC vulnerability notifications.
- Buyers: scan the label QR code and confirm the model is on the Labelled Product List.
Standards and references
- Cyber Security Agency of Singapore: CLS(IoT) for Manufacturers
- Cybersecurity Certification Centre: CCC SP-151-1 CLS(IoT) Overview of the Scheme v1.4
- Cybersecurity Certification Centre: CCC SP-151-2 CLS(IoT) Scheme Specifications v1.4
- Cyber Security Agency of Singapore: CLS(IoT) Publications
- Cyber Security Agency of Singapore: CLS(IoT) Updates
- Cyber Security Agency of Singapore: CLS(IoT) Registration
- Cyber Security Agency of Singapore: About CLS(IoT) and Mutual Recognition
- Cyber Security Agency of Singapore: Launch of Cybersecurity Labelling Scheme for Medical Devices
Related NHI Mgmt Group resources: ETSI EN 303 645 Consumer IoT Guide · UK PSTI Act Guide · Product Security Laws Map · Singapore Cybersecurity Act Guide. This guide summarises the Singapore Cybersecurity Labelling Scheme as published by CSA at 27 October 2026 and is not legal advice.