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

Cyber Resilience Act

JC-STAR (Japan IoT security labeling), explained

Last updated:

JC-STAR — the "Labeling Scheme based on Japan Cyber-Security Technical Assessment Requirements" — is Japan's conformity-labeling program for IoT products, run by the Information-technology Promotion Agency (IPA) under a policy METI published in August 2024, with four conformance levels (STAR-1 through STAR-4) running from vendor self-declaration at the base up to mandatory third-party evaluation at the top. It joins a growing family of national IoT device-labeling schemes alongside the UK's PSTI regime, Singapore's Cybersecurity Labelling Scheme (CLS), and the ioXt Alliance pledge — and, as of 2026, it has started actively cross-recognizing some of them rather than existing as a fully separate island.

This guide's facts come from IPA's own English-language JC-STAR pages, the STAR-1 Conformance Requirements and Assessment Methods document, METI's launch press release and the UK statutory instrument that recognises STAR-1, read 2026-11-11. Where independent secondary reporting (Foresight, IoT M2M Council) gives different dates, the text says so.

Key takeaways

  • IPA's own program page lays out four conformance tiers.
  • IPA's STAR-1 Conformance Requirements and Assessment Methods lists 16 requirements, S1.1-01 to S1.1-16, each with a document check and, for some, a device check.
  • IPA began accepting STAR-1 applications on 25 March 2025, a date given on IPA's own page and corroborated independently by METI's official press release announcing the scheme's launch.
  • JC-STAR is not described, in either IPA's or METI's own materials, as a blanket legal product-safety mandate the way the EU's Cyber Resilience Act is for the products it covers.

What are the four levels and two assessment methods?

IPA's own program page lays out four conformance tiers. STAR-1 is a unified, baseline set of requirements addressing minimum threats common to all in-scope IoT products — explicitly built to harmonize with international baselines like ETSI EN 303 645 and NIST's NISTIR 8425, rather than reinvent a Japan-only requirement set from scratch. STAR-2 adds category-specific requirements on top of STAR-1 for particular product types. Both STAR-1 and STAR-2 run on vendor self-declaration: IPA grants the conformance label based on a checklist describing the results of the vendor's own self-assessment against the scheme's published requirements and assessment procedures, rather than an independent audit. IPA balances that by reserving the right to inspect and revoke a label when doubts arise about conformance.

STAR-3 and STAR-4 step up to mandatory third-party evaluation, aimed at products headed for government agencies, critical-infrastructure providers, local governments and large corporations; IPA certifies these levels based on reports from independent evaluation bodies. The first two STAR-3 product categories are network devices (such as routers) and network cameras. IPA's own page dates the "STAR-3 Security Requirements" for both categories to 13 July 2026 and the "STAR-3 Conformance Requirements" to 2 September 2026; secondary reporting gave an earlier 12 June 2026 date, so use IPA's dates when planning. STAR-4 requirements had no published category set as of November 2026, and IPA's mutual-recognition pages state that only STAR-1 is currently operational.

Level Requirements Who assesses Status, November 2026
STAR-1 Common baseline for all IoT products Vendor self-declaration, IPA labels Applications open since 25 March 2025
STAR-2 Baseline + category-specific Vendor self-declaration, IPA labels Not operational (IPA, June 2026 update)
STAR-3 Higher level for critical systems Third-party evaluation body, IPA certifies Routers/network devices and network cameras published Jul–Sep 2026
STAR-4 Highest level for critical systems Third-party evaluation body, IPA certifies No category set published

What do the 16 STAR-1 requirements cover?

IPA's STAR-1 Conformance Requirements and Assessment Methods lists 16 requirements, S1.1-01 to S1.1-16, each with a document check and, for some, a device check. Physical tampering during operation and supply-chain tampering during development are explicitly out of STAR-1's scope.

Requirement Plain summary
S1.1-01 Authenticated access control to protected data over IP
S1.1-02 No common default passwords
S1.1-03 Users can change authentication values
S1.1-04 Brute-force protection on network login (non-constrained devices)
S1.1-05 Public vulnerability disclosure policy with contact and process
S1.1-06 Firmware is updatable, version is checkable and persists
S1.1-07 Updates are easy for users to apply
S1.1-08 Integrity check before installing network updates
S1.1-09 Documented policy for prioritising security updates
S1.1-10 Model number visible to the user
S1.1-11 Protected data stored securely, including on SD cards
S1.1-12 Protected data protected in transit
S1.1-13 Unneeded ports, Bluetooth and USB disabled; vulnerability scan with no exploitable findings
S1.1-14 Credentials and settings survive power or network loss
S1.1-15 Users can delete their data
S1.1-16 Security information for users, such as setup guidance and support period

Two practical notes come from the same document. Products already certified under Japan's Telecommunications Business Act terminal-equipment security standards ([T] or [A] mark) are deemed to meet S1.1-01 and S1.1-06. And S1.1-13 asks for an actual vulnerability scan of the product, so a firmware team needs scan evidence, not only documentation. Teams that already meet ETSI EN 303 645 will recognise most items, because the document lists the related ETSI EN 303 645, PSTI and NISTIR 8425 clauses under each requirement.

How do you apply, and what does it cost?

IPA began accepting STAR-1 applications on 25 March 2025, a date given on IPA's own page and corroborated independently by METI's official press release announcing the scheme's launch. IPA's Application & Reporting Process page sets out the rest:

  1. Assign a Japanese-speaking contactNew applications must be made in Japanese.
  2. Request an application numberthrough IPA's (Japanese-only) request form.
  3. Complete the self-assessmentusing the STAR-1 Assessment Guide and checklist.
  4. Email the application set(application confirmation, checklist, proxy letter if an agent applies) quoting the number.
  5. Pay the fee after acceptanceThe STAR-1 application fee is 198,000 yen including tax and is not refundable. Evaluation-body fees for STAR-3 and STAR-4 are separate.
  6. Plan for renewalA label is valid for up to two years from issue, at any level.

IPA also warns that claims such as "JC-STAR conformance to be acquired" are unauthorised representations unless an application has been accepted and a provisional ID issued. Secondary reporting adds that a discounted STAR-1 fee of 110,000 yen applied until 30 September 2025.

Is JC-STAR mandatory, or a procurement lever?

JC-STAR is not described, in either IPA's or METI's own materials, as a blanket legal product-safety mandate the way the EU's Cyber Resilience Act is for the products it covers. Its practical pull instead comes from government procurement: secondary reporting indicates Japan intends to require JC-STAR labeling in government IoT purchases, starting with STAR-1 and moving toward higher levels as the STAR-2/3/4 requirement sets mature and stabilize. IPA's own framing points the same way: STAR-3 and STAR-4 exist for products bought by government agencies and critical-infrastructure operators. A manufacturer with no interest in Japanese public-sector sales is not confirmed to face a direct legal obligation to hold a label, though retailer and enterprise-buyer preference for labelled products made the UK's PSTI regime and Singapore's CLS commercially relevant beyond their legal scope, and the same effect is plausible here.

How does mutual recognition with the UK PSTI and Singapore CLS work?

JC-STAR stopped being a purely domestic scheme in 2026, and IPA now publishes the precise scope of each arrangement.

UK PSTI. IPA's PSTI mutual-recognition page states that recognition started on 1 January 2026. A product with a PSTI statement of compliance is treated as meeting S1.1-02 (default passwords), S1.1-05 (vulnerability disclosure) and S1.1-16 (product information); the other 13 STAR-1 items still need self-assessment. Forms can be completed in English and the STAR-1 fee drops to 140,000 yen. In the other direction, UK Statutory Instrument 2025/1267, in force since 4 December 2025, lets a manufacturer whose product holds an unexpired JC-STAR STAR-1 label be treated as complying with the PSTI security requirements and the statement-of-compliance duty, provided the conditions in the instrument are met. IPA adds its own conditions, including English-language product and vulnerability information and an English vulnerability contact point.

Singapore CLS. IPA's CLS mutual-recognition page states that recognition with Singapore's Cybersecurity Labelling Scheme started on 1 June 2026 under a METI–CSA Memorandum of Cooperation covering STAR-1 and CLS Level 1. CLS-labelled products are exempt from the matching checklist items, with the same 140,000 yen STAR-1 fee. JC-STAR holders can obtain a CLS label through the MRA route on Singapore's GoBusiness portal for S$51, without engaging a test lab.

Route What it saves Fee
PSTI-compliant product → JC-STAR STAR-1 S1.1-02, -05, -16 checklist items; English forms 140,000 yen (standard 198,000)
JC-STAR STAR-1 label → UK market Deemed PSTI compliance under SI 2025/1267, if conditions met IPA administrative fee applies
CLS-labelled product → JC-STAR STAR-1 Matching checklist items; English forms 140,000 yen
JC-STAR label → CLS No test-lab engagement S$51

Worked example: carrying a PSTI-compliant camera into JC-STAR

Synthetic example for illustration; the product and company are invented.

A camera maker already sells an indoor Wi-Fi camera in the UK with a published PSTI statement of compliance and wants to supply a Japanese retailer.

  1. Choose the routeThe PSTI route covers S1.1-02, -05 and -16, so the team self-assesses the other 13 requirements.
  2. Gap checkThe camera's local login already locks out after repeated failures, which covers S1.1-04. The gap is S1.1-13: the UART console is closed, but a factory-test UDP port stays open in production builds. The team removes it and runs a vulnerability scan on the release build.
  3. EvidenceFor S1.1-08 they document signature verification before update install; for S1.1-11 they describe how Wi-Fi credentials are stored in the SoC's secure storage.
  4. ApplyThey submit the English PSTI-route application form and checklist with their statement-of-compliance URL and pay 140,000 yen after acceptance.
  5. CalendarThe label lasts up to two years, so renewal goes into the product's support-period plan, next to its PSTI support-period commitment.

What are the common pitfalls?

  • Relying on secondary dates. IPA's own pages are the record; news coverage has differed on STAR-3 dates.
  • Assuming full equivalence. PSTI recognition covers three of 16 STAR-1 items, not the whole checklist.
  • Advertising early. "JC-STAR ready" wording before IPA accepts the application counts as an unauthorised representation.
  • Documentation without testing. S1.1-13 needs a real vulnerability scan of the product.
  • Japanese-only support. Using a JC-STAR label for the UK requires English information and an English vulnerability contact.
  • Letting the label lapse. Under SI 2025/1267 only an unexpired STAR-1 label counts.

Where should a device maker start?

  1. Start with STAR-1 if Japan is a target market at allIt is the lowest-friction entry point (self-declaration, baseline requirements aligned to ETSI EN 303 645) and is the level Japan's government procurement is expected to require first.
  2. Budget for Japanese-language documentationNew applications must be submitted in Japanese; only the PSTI and CLS recognition routes accept English forms.
  3. Watch STAR-3 if you make routers or network camerasThose are the first two product categories IPA has published STAR-3 requirements for, and they're also categories that already draw CISA and ENISA attention elsewhere in this guide library.
  4. Use the PSTI/CLS mutual-recognition paths before re-doing work you've already doneIf you already hold a UK PSTI compliance statement or a Singapore CLS label, start from IPA's recognition pages and self-assess only the remaining items.
  5. Don't treat JC-STAR as a CRA substituteIt is a Japan-market, IPA-run labeling scheme with no confirmed legal link to the EU Cyber Resilience Act, RED/EN 18031, or any other EU conformity-assessment regime covered elsewhere on this site. For the US, compare the FCC Cyber Trust Mark.

SoftWSP's firmware scan supports the evidence side of a STAR-1 self-assessment: it builds a CycloneDX 1.6 firmware SBOM from the image and matches its components against NVD, CISA KEV, FIRST EPSS and CISA ICS advisories, with an AI-drafted, cited report reviewed by an engineer. That gives a known-vulnerability view of the release; it does not replace the device vulnerability scan S1.1-13 asks for, file the application, or grant a label. See Device & Firmware Security.

This guide draws on IPA's own JC-STAR program, application and mutual-recognition pages, IPA's STAR-1 requirements document, UK SI 2025/1267 and METI's official press release, cross-checked against independent secondary reporting. This guide is not a substitute for IPA's own published requirements or for regulatory/legal advice.

Put this guide to work

Frequently asked questions

What is JC-STAR, and who runs it?

JC-STAR — "Labeling Scheme based on Japan Cyber-Security Technical Assessment Requirements" — is a Japanese conformity-labeling scheme for IoT products, administered by Japan's Information-technology Promotion Agency (IPA) per IPA's own program page. It was established under the "IoT Product Security Conformity Assessment Scheme Policy," published by Japan's Ministry of Economy, Trade and Industry (METI) in August 2024, and IPA began accepting applications for the scheme's first level, STAR-1, on 25 March 2025 — a date corroborated by METI's own press release announcing the launch.

What do the STAR-1 through STAR-4 levels actually mean?

Per IPA's own program page, STAR-1 is a unified baseline addressing minimum common threats across all in-scope IoT products, explicitly designed to harmonize with international baselines like ETSI EN 303 645 and NIST's NISTIR 8425. STAR-2 layers category-specific requirements on top of that baseline for particular product types. STAR-1 and STAR-2 both use vendor self-declaration, reviewed and labeled by IPA based on a self-assessment checklist. STAR-3 and STAR-4 are higher levels requiring independent third-party evaluation, aimed at government and critical-infrastructure procurement; per secondary reporting (Foresight), IPA published STAR-3's specific requirements — initially scoped to network devices (such as routers) and network cameras — on 12 June 2026, with STAR-4 still under development as of November 2026.

Is JC-STAR mandatory for selling IoT products in Japan?

No — it is described as a voluntary labeling scheme, not a product-safety law with a blanket legal mandate. Its practical leverage comes from government procurement: secondary reporting indicates Japan intends to require JC-STAR labeling (starting with STAR-1) in government IoT procurement, progressively moving toward higher levels as the STAR-2/3/4 requirement sets mature. A manufacturer not selling to Japanese government buyers is not confirmed to face a legal requirement to hold a JC-STAR label, though the label can still function as a market-trust signal for commercial buyers, similar to the UK's PSTI mark or Singapore's Cybersecurity Labelling Scheme.

Does a JC-STAR label get recognized outside Japan?

Partially, and only through specific bilateral arrangements as of November 2026 — JC-STAR is not a globally harmonized label. Per secondary reporting (Foresight), mutual recognition between JC-STAR and Singapore's Cybersecurity Labelling Scheme (CLS) began on 1 June 2026, and IPA separately introduced application documentation for products already compliant with the UK's Product Security and Telecommunications Infrastructure (PSTI) regime, following government-to-government cooperation. The same reporting cautions that these arrangements reduce duplicate documentation and testing rather than eliminate market-specific obligations entirely — a manufacturer still needs to confirm what, if anything, each arrangement actually waives before assuming a Singapore CLS or UK PSTI mark alone satisfies JC-STAR, or vice versa.

Sources

  1. IPA: Japan Cyber-Security Technical Assessment Requirement (JC-STAR) — official program page (administrator, STAR-1 through STAR-4 levels, self-declaration vs third-party assessment, international harmonization)
  2. METI: Launch of IoT Product Security Labeling Scheme (JC-STAR) — official press release (METI policy basis, launch date)
  3. Foresight: Japan Expands JC-STAR IoT Security Labelling With STAR-3 Standards (STAR-3 publication date and scope, Singapore CLS and UK PSTI mutual-recognition details)
  4. IoT M2M Council: Japan launches IoT cyber label scheme (independent secondary reporting on scheme structure and application process)
  5. IPA: JC-STAR Application & Reporting Process (Japanese-language applications, STAR-1 fee, label validity)
  6. IPA: Regarding Mutual Recognition Application for PSTI Compliance Certification & JC-STAR
  7. IPA: Regarding Mutual Recognition Application for Singapore CLS & JC-STAR
  8. IPA: STAR-1 Conformance Requirements and Assessment Methods (requirements S1.1-01 to S1.1-16, PDF)
  9. UK SI 2025/1267: Product Security and Telecommunications Infrastructure (Security Requirements for Relevant Connectable Products) (Amendment) (No. 2) Regulations 2025 (deemed compliance via JC-STAR STAR-1 and Singapore CLS)
Was this guide helpful?

In this cluster

JC-STAR (Japan IoT security labeling), explained