Product team testing a smart-speaker-style device with microphones in an anechoic chamber

Cyber Resilience Act

Singapore's Cybersecurity Labelling Scheme for IoT (CLS(IoT)), explained

Last updated:

Singapore's Cybersecurity Labelling Scheme for IoT (CLS(IoT)) has been mandatory for Wi-Fi routers sold in Singapore since 2 May 2022, requiring at least Level 1 of CSA's four-tier consumer security rating run by the Cyber Security Agency of Singapore (CSA). CSA describes it as "the first of its kind in the Asia-Pacific region." It was announced on 6 October 2020 as part of Singapore's Safer Cyberspace Masterplan 2020 — under the strategic thrust to secure "our core digital infrastructure... devices and endpoints" — and started with Wi-Fi routers and smart home hubs before extending to "IP cameras, smart door locks, smart lights and smart printers."

Key takeaways

  • CSA publishes two parallel descriptions of the same four levels — a short consumer-facing version and a more technical manufacturer-facing one.
  • An application runs through an approved testing laboratory first and then through CSA's Cybersecurity Certification Centre (CCC) on the GoBusiness portal.
  • CSA publishes its own application fees; testing laboratory fees are commercial and not published by CSA.
  • At Level 3 the lab runs automated analysers over the firmware and any companion mobile app.

What are the four levels, and how does each build on the last?

CSA publishes two parallel descriptions of the same four levels — a short consumer-facing version and a more technical manufacturer-facing one. Combined:

Level (asterisks) Consumer-facing requirement Manufacturer-facing assessment tier
1 Unique default passwords; software updates provided Tier 1 — baseline requirements based on ETSI EN 303 645, eliminating "common mistakes" (default passwords, missing update mechanism, no vulnerability-reporting channel)
2 All mandatory requirements of an international standard, plus Level 1 Tier 2 — adherence to "all mandatory requirements within ETSI EN 303 645"
3 Developed using Security-by-Design, software binaries assessed by an approved third-party lab, plus Level 2 Tier 3 — secure development lifecycle per the IMDA IoT Cyber Security Guide (March 2020) plus automated binary analysis for "known critical software weakness, vulnerabilities, or malware"
4 Structured penetration testing by an approved third-party lab, plus Level 3 Tier 4 — third-party penetration test for "a basic level of resistance against common cybersecurity attacks"

Tiers are completed strictly in sequence — a manufacturer targeting Level 3 "undergo[es] assessments at Tiers 1, 2, and 3," not Tier 3 alone.

Levels 1 and 2 are still declarations by the manufacturer, but they are no longer filed alone. CSA's scheme updates page states that from 1 April 2025, Level 1 and Level 2 applications "are required to be reviewed by an approved CLS Testing Laboratory (TL)". Applications without one "will not be processed". The lab reviews the declaration and evidence without testing the device; independent testing starts at Level 3.

How does an application work, step by step?

An application runs through an approved testing laboratory first and then through CSA's Cybersecurity Certification Centre (CCC) on the GoBusiness portal. The steps below follow the CLS(IoT) Scheme Specifications v1.4 (April 2025) and the Overview of the Scheme v1.4:

  1. Pick the target level and the modelsSeveral models can share one application if they belong to the same product family. For Levels 1–2 the firmware may differ only in look and feel and chipset drivers; for Levels 3–4 the security-relevant hardware and software (SoC, radio chipset, security modules) must be identical.
  2. Engage an approved labCSA lists the labs on its approved laboratories page, which named eleven labs in Singapore, Germany and the Netherlands when last updated on 4 November 2026.
  3. Complete the Declaration of Conformityand the supporting-evidence template: descriptions, screenshots, process charts or work instructions for each provision. Home gateways use a separate declaration and methodology that also reference ETSI TS 103 848.
  4. Lab review and testingFor Levels 1–2 the lab assesses the declaration and gives a verdict per clause. Level 3 adds lifecycle evidence (eight provisions, CK-LP-01 to CK-LP-08) and binary analysis. Level 4 adds a black-box penetration test, for which the manufacturer also sends one unit to CCC.
  5. Apply on GoBusinesswith the declaration, evidence and the lab's assessment or report, and pay the CCC fee before work starts.
  6. CCC reviewCCC can ask for clarification or a presentation, and the lab presents Level 3–4 results to CCC.
  7. Label issuedThe label shows the asterisks, a registration identifier in the format "CSA/IOTXXXXX" and a QR code linking to the product's entry on CSA's labelled-product list.

What does a CLS label cost, and how long does it take?

CSA publishes its own application fees; testing laboratory fees are commercial and not published by CSA. The CLS(IoT) Fee Schedule v1.1 (April 2025) sets these CCC fees, in Singapore dollars and subject to GST:

Application CCC fee (S$, before GST)
Level 1 57
Level 2 142
Level 3 633
Level 4 2,347
Mutual recognition (existing Finnish, German or Korean label) 51

Fees are paid before any CLS work starts and are not refunded, even if no label is issued. Rework caused by the applicant is charged extra. The revision took effect on 1 April 2025, when Level 2 fell from S$418 and Level 4 from S$3,810, according to the updates page.

On time, the specifications give two lab durations. Level 3 binary analysis should take "around 3 – 5 working days, inclusive of submission of the full report". The Level 4 penetration test "should take no longer than 15 working days", with at least 4 days of freeform testing. The overview adds deadlines. CCC can end an application after 8 weeks without activity, after 6 months from acceptance without an extension request, or after one year in any case. Plan remediation time on top of the lab days.

What does the Level 3 binary analysis check?

At Level 3 the lab runs automated analysers over the firmware and any companion mobile app. The device must come out "free from identified exploitable vulnerabilities". Section 5 of the Scheme Specifications asks the manufacturer for:

  • The firmware binary and app packages in a format the scanners can read (for example unencrypted), with SHA-256 hashes of every file.
  • A list of all software components in the firmware and apps (the examples given are Micro_Httpd and OpenSSL) and the permissions each app requests.
  • A rationale and remediation for each CVE the software composition analyser finds: a patch or upgrade, a false-positive explanation (for example, the vulnerable component is unused), or an exploitability assessment that the lab reviews.
  • Consent to a cloud malware scan. A positive result is re-checked with a second scanner.

The lab also checks open-source licence compliance, looks for hard-coded critical security parameters, searches public sources for known issues with the device, and compares its analyser results with the manufacturer's SBOM to catch components the tools missed. The specification warns that if many vulnerabilities remain, the manufacturer "is strongly encouraged to withdraw the application" and fix them first. Our firmware SBOM guide and hard-coded credentials guide cover the two areas that most often hold up this step.

How long is a label valid, and what happens after a firmware update?

A CLS label is valid for as long as the manufacturer supports the device with security updates, up to 3 years, under section 13.2 of the Overview of the Scheme. Renewal can be requested up to six months before expiry and keeps the label ID; an expired label cannot be renewed and needs a new application.

Change after labelling Levels 1–2 Levels 3–4
Minor software update or patch Label remains valid Label remains valid
Major change (new OS, new language, firmware rewritten, new security architecture) Label remains valid Retesting with a lab is required

While the label is live, the manufacturer must run a vulnerability disclosure programme, notify CCC "as early as possible" of each reported vulnerability with impact and remediation plan, and publish the defined support period on its website.

Is CLS mandatory for any product?

CLS is largely a voluntary, market-differentiation label — CSA's framing is to "encourage manufacturers to prioritise cybersecurity," not to compel it. The one explicit exception is Wi-Fi (residential gateway) routers: CSA's registration guidance states plainly that "it is a requirement for all Wi-Fi routers that are to be sold for local use in Singapore to comply with the [IMDA Technical Specification for Security Requirements for Residential Gateways (IMDA TS RG-SEC)] and attain minimally CLS Level 1 by 2 May 2022." The two frameworks share a registration portal (GoBusiness), and a compliant router must carry both the IMDA compliance label and the CSA Cybersecurity Label.

Which foreign labels count toward CLS?

CSA has negotiated recognition arrangements that let a label earned under a partner scheme count directly toward a CLS level, without a separate full assessment:

Partner scheme Country/region Recognised CLS level
Traficom Cybersecurity Label Finland (MoU, 2021) Level 3
IT Security Label (BSI) Germany (MRA, 2022) Level 2
Certification of IoT Cybersecurity (CIC), Basic Level South Korea (MRA, KISA) Level 3
Product Security and Telecommunications Infrastructure (PSTI) Act compliance United Kingdom Level 1

Each arrangement runs both ways — a CLS Level 3 (or 4) label is in turn recognised as meeting Finland's requirements, and so on for the other three. CSA's own manufacturer page adds a one-way restriction worth noting: a label obtained through mutual recognition cannot be used to then apply for a third scheme — "a developer who has attained the Cybersecurity Label from Traficom would be eligible to attain the CLS Cybersecurity label through the mutual recognition partnership. However, the developer shall not use the granted CLS label to apply for Germany's IT Security Label." CSA's about page adds that Level 3 and Level 4 applications can receive the Singapore and Finnish labels at once through a single application process.

How does CLS relate to ETSI EN 303 645, UK PSTI and the EU CRA?

CLS's Tier 1/Tier 2 split maps directly onto ETSI EN 303 645's baseline provisions, the same standard underlying the UK's PSTI regime and the US Cyber Trust Mark — which is precisely why CSA can recognise UK PSTI compliance as meeting CLS Level 1. Where CLS goes further than a single-tier pass/fail scheme is the explicit Level 3/4 escalation to independent binary analysis and penetration testing, placing a declared Level 1 and a lab-tested Level 4 product on the same visible asterisk scale rather than treating "certified" as one undifferentiated outcome.

The UK link now runs in the other direction too. Since 4 December 2025, SI 2025/1267 treats a product holding an unexpired CLS label at any level as meeting the three PSTI security requirements and the duty to ship a statement of compliance. The definition names CLS specification CCC SP-151-2 version 1.4. Our PSTI statement of compliance guide covers that route, and the JC-STAR guide covers Japan's equivalent.

Market What a CLS label does there
Singapore Mandatory Level 1 for Wi-Fi routers (with IMDA TS RG-SEC); voluntary for other devices
United Kingdom Unexpired label at any level = deemed compliance with PSTI Schedule 1 and section 9(2)
Finland, Germany, South Korea Recognised at the mapped level under the bilateral arrangements
European Union (CRA) No legal effect; CRA conformity relies on harmonised standards, common specifications or EU certificates

For the EU, the Cyber Resilience Act gives a CLS label no presumption of conformity. The evidence still carries over: the EN 303 645 work behind Levels 1–2, and the SBOM and CVE handling behind Level 3, feed the CRA technical file.

Worked example: what does a Level 3 application look like for a smart lock?

This is a hypothetical example, not a customer case. A 60-person maker of Wi-Fi smart door locks with a companion app wants a Singapore listing, and its UK distributor wants PSTI cover.

  1. GroupingIts two lock models share the SoC, radio chipset and firmware, so they go into one Level 3 application.
  2. EvidenceThe team maps its EN 303 645 test records to the Level 1–2 declaration and its secure development process to CK-LP-01 to CK-LP-08.
  3. Pre-checkBefore submission it generates a firmware SBOM and triages known CVEs in bundled components. It upgrades an outdated TLS library and writes false-positive rationales for two components that are compiled out.
  4. Lab workIt sends unencrypted firmware, both app packages, SHA-256 hashes and the component list. The lab plans the analysis within the 3–5 working days the specification expects, plus one re-scan after a fix.
  5. FeesIt pays the S$633 CCC fee plus GST on GoBusiness; the lab fee is agreed separately.
  6. After the labelThe team records the expiry date, at most three years out, in its PSTI file, because the UK deemed compliance ends when the label expires.

What are the common pitfalls?

  • Applying for Level 1 or 2 without a lab. Since 1 April 2025 those applications are not processed.
  • Encrypted firmware or no component list at Level 3. The scanners need readable binaries, and the lab compares results against your SBOM.
  • Grouping models that differ in security hardware. Level 3–4 groups need identical security-relevant components.
  • Treating the label as permanent. It lasts at most three years, and a major firmware change at Level 3–4 triggers retesting.
  • Assuming CLS covers the EU. It does not give CRA presumption of conformity.
  • Forgetting to notify CCC of vulnerabilities reported after labelling.

Where should a device maker start?

  1. Check whether your category has a mandatory floorWi-Fi routers sold in Singapore must clear IMDA TS RG-SEC and CLS Level 1 together — treat that as a market-access gate, not an optional label.
  2. Start from ETSI EN 303 645 regardless of target level, since Tiers 1 and 2 are defined directly against it — work already done for EU/UK conformance (EN 303 645, PSTI) carries over.
  3. Decide your target level by audience, not by defaultLevels 1–2 are a declared baseline reviewed by an approved lab; Levels 3–4 add independent binary analysis and penetration testing and buy more credibility with enterprise or export buyers.
  4. If you already hold a Finnish, German, Korean or UK label, apply for the matching CLS level through mutual recognition before commissioning a fresh assessment — but don't plan on using the resulting CLS label to bootstrap a fifth scheme.
  5. If you sell in the UK, decide whether CLS will be your PSTI route, and plan renewal before the label expires.

SoftWSP's device and firmware assessments can be scoped against the CLS Tier 1-4 ladder alongside the CVE and SBOM evidence a labelling assessment expects. Its firmware analysis extracts the components into a CycloneDX 1.6 SBOM and matches them against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories. It then drafts a cited report for an engineer to review, which is useful preparation before the lab's own binary analysis, not a replacement for it: see Device & Firmware Security.

This guide summarises the public CSA Singapore CLS(IoT) documentation current as of this guide's last-updated date; it is not a substitute for CSA's current scheme rules and does not constitute compliance or legal advice.

Put this guide to work

Frequently asked questions

What is the Cybersecurity Labelling Scheme (CLS)?

CLS(IoT) is a consumer smart-device security rating label run by the Cyber Security Agency of Singapore (CSA). CSA's own page describes it as introduced 'to enhance IoT security, guide consumers in choosing secure smart devices, and encourage manufacturers to prioritise cybersecurity in their products,' and states it is 'the first of its kind in the Asia-Pacific region.' It was announced on 6 October 2020 as part of Singapore's Safer Cyberspace Masterplan 2020, under the strategic thrust of 'securing our core digital infrastructure... devices and endpoints.' It started with Wi-Fi routers and smart home hubs and 'has since been extended to include all categories of consumer IoT devices, such as IP cameras, smart door locks, smart lights and smart printers.'

What do CLS Levels 1 to 4 actually require?

Per CSA's consumer-facing level table, each level includes everything below it: Level 1 — 'basic security requirements such as ensuring unique default passwords and providing software updates'; Level 2 — 'all mandatory security requirements of international standards,' plus Level 1; Level 3 — developed using Security-by-Design principles and 'assessment of software binaries by approved third-party test labs,' plus Level 2; Level 4 — 'structured penetration tests by approved third-party test labs,' plus Level 3. CSA's manufacturer-facing page maps these to four sequential assessment tiers: Tier 1 is based on ETSI EN 303 645's baseline provisions (eliminating 'common mistakes' like default passwords); Tier 2 requires adherence to 'all mandatory requirements within ETSI EN 303 645'; Tier 3 adds secure-development-lifecycle practices from the IMDA IoT Cyber Security Guide plus automated binary analysis for known weaknesses, vulnerabilities or malware; Tier 4 is the third-party penetration test.

Is CLS mandatory, or voluntary?

It depends on the product category. CSA's general framing is encouragement-oriented ('encourage manufacturers to prioritise cybersecurity'), and most device categories register voluntarily. But for Wi-Fi routers specifically, CSA's registration page states a hard requirement: 'It is a requirement for all Wi-Fi routers that are to be sold for local use in Singapore to comply with the IMDA TS RG-SEC and attain minimally CLS Level 1 by 2 May 2022' — compliance with IMDA's residential-gateway technical specification (IMDA TS RG-SEC) automatically qualifies a router for CLS Level 1, and the two compliance labels (IMDA and CSA) must be affixed together.

Does a CLS label get recognised outside Singapore?

CSA has signed mutual recognition arrangements with four other schemes, each mapped to a specific CLS level: Finland's Traficom Cybersecurity Label (2021) is mutually recognised with CLS Level 3; Germany's BSI IT Security Label (2022) with CLS Level 2; South Korea's KISA Certification of IoT Cybersecurity (CIC) 'Basic Level' with CLS Level 3; and products compliant with the UK's Product Security and Telecommunications Infrastructure (PSTI) Act are recognised as meeting CLS Level 1. CSA's own manufacturer page adds a caveat worth repeating: a label obtained *through* mutual recognition cannot then be used to apply for a *third* scheme — e.g. a Finnish-label holder who gets CLS via the MoU cannot use that CLS label to apply for Germany's IT Security Label.

Sources

  1. CSA Singapore: About the Cybersecurity Labelling Scheme for IoT — CLS(IoT)
  2. CSA Singapore: CLS(IoT) for Manufacturers — cybersecurity levels and assessment tiers
  3. CSA Singapore: CLS(IoT) for Consumers — what the cybersecurity levels represent
  4. CSA Singapore: CLS(IoT) Registration — Wi-Fi router / IMDA TS RG-SEC requirement
  5. CSA Singapore press release: Singapore's Safer Cyberspace Masterplan 2020 (6 October 2020)
  6. ETSI EN 303 645 V2.1.1/V3.1.3, Cyber Security for Consumer Internet of Things: Baseline Requirements (Tier 1/2 basis)
  7. CSA Singapore: CLS(IoT) updates (lab review of Level 1 and 2 applications and revised fees from 1 April 2025)
  8. CSA Singapore: CLS(IoT) approved testing laboratories
  9. CSA Singapore: About CLS(IoT) (mutual recognition, single application for Singapore and Finnish labels)
  10. CSA CCC SP-151-2: CLS(IoT) Scheme Specifications v1.4 (April 2025)
  11. CSA CCC SP-151-1: CLS(IoT) Overview of the Scheme v1.4 (grouping, assurance continuity, renewal, label validity)
  12. CSA CCC SP-151-8: CLS(IoT) Fee Schedule v1.1 (April 2025)
  13. UK SI 2025/1267: PSTI (Security Requirements for Relevant Connectable Products) (Amendment) (No. 2) Regulations 2025 (Singapore CLS deemed compliance)
Was this guide helpful?

In this cluster

Singapore's Cybersecurity Labelling Scheme for IoT (CLS(IoT)), explained