Engineers with a laptop at automation test rigs in a bright production hall

SBOM

ISO/IEC 20243 (O-TTPS): mitigating maliciously tainted and counterfeit products, explained

Last updated:

ISO/IEC 20243, "Information technology — Open Trusted Technology Provider™ Standard (O-TTPS)," is an ISO/IEC JTC 1 International Standard aimed at a specific, narrow supply-chain risk: a commercial off-the-shelf (COTS) ICT product arriving maliciously tainted (deliberately modified by an adversary somewhere in the supply chain) or counterfeit (not genuinely what it claims to be). Unlike broader supply-chain-risk standards that cover any kind of supplier risk, O-TTPS focuses specifically on this integrity question across a product's full life cycle — design, sourcing, build, fulfillment, distribution, sustainment and disposal — making it a natural companion to the SBOM and component-provenance work firmware and hardware teams already do.

Key takeaways

  • The standard did not start inside ISO.
  • Because requirements and assessment are separate jobs.
  • Part 1 defines two threats and groups its requirements into three areas.
  • SC_CTM.02 (counterfeit mitigation) and SC_MAL.02 (malware detection) were heavily revised and made mandatory.

How did it go from industry consortium standard to ISO/IEC standard?

The standard did not start inside ISO. The Open Group's Open Trusted Technology Forum (OTTF) formed out of an industry meeting in January 2010 and was formally announced later that year as a vendor-neutral forum for technology companies, customers, governments and suppliers to develop supply-chain security guidelines together. The OTTF released an O-TTPS Snapshot in February 2012, then the full O-TTPS 1.0 — "Mitigating Maliciously Tainted and Counterfeit Products" — in April 2013. On 1 September 2015, The Open Group announced that O-TTPS (as Version 1.1) had been approved as an ISO/IEC International Standard, published as the single-document ISO/IEC 20243:2015, under Joint Technical Committee ISO/IEC JTC 1.

Behind the standard sits a broader document, the O-TTPF (Open Trusted Technology Provider Framework). The preface of the 2023 edition describes it as "an evolving compendium" of supply-chain and product-integrity practices, first a White Paper in February 2011 and a Guide since September 2021; the O-TTPS picks the subset that can be assessed. Each ISO edition is adopted under the JTC 1 PAS procedure, which is why every ISO text is technically equivalent to an Open Group version.

Why is ISO/IEC 20243 split into two parts?

Because requirements and assessment are separate jobs. With the 2018 revision, O-TTPS Version 1.1.1 was published by ISO/IEC as two parts rather than one document:

Part Title 2018 edition What it covers
Part 1 Requirements and recommendations ISO/IEC 20243-1:2018 (32 pages, published February 2018, ICS 13.310/35.030) The mandatory ("shall") requirements and recommended practices a provider implements across the product life cycle to mitigate tainted/counterfeit risk
Part 2 Assessment procedures for the O-TTPS ISO/IEC 20243-2:2018 The procedures an assessor follows when conducting conformity assessment against Part 1's mandatory requirements, intended — per ISO's own abstract — "to ensure the repeatability, reproducibility, and objectivity of assessments"

Per The Open Group's own version history, both 2018 parts were technically equivalent to its own O-TTPS Version 1.1.1, while the original single-document 2015 edition had been equivalent to Version 1.1. The Part 1 introduction notes the document "cannot fully address threats that originate wholly outside any span of control of the provider," giving the example of a counterfeiter producing a fake circuit board with no link to the original manufacturer — O-TTPS is risk mitigation within a provider's own practices, not a guarantee against every tampering scenario.

What does Part 1 actually require?

Part 1 defines two threats and groups its requirements into three areas. The threats, quoted from the 2023 introduction: a maliciously tainted product "is produced by the provider and is acquired through a provider's authorized channel, but it has been tampered with maliciously"; a counterfeit product "is produced other than by, or for, the provider, or it is supplied to the provider by other than a provider's authorized channel and is presented as being legitimate even though it is not."

The requirements are organised as named attributes. The table uses the attribute titles from the 2018 edition's contents; the 2023 edition keeps the same three areas.

Area Attributes
PD — Product Development/Engineering Method PD_DES design process (software/firmware/hardware) · PD_CFM configuration management · PD_MPP well-defined development/engineering method · PD_QAT quality and test management · PD_PSM product sustainment management
SE — Secure Development/Engineering Method SE_TAM threat analysis and mitigation · SE_RTP run-time protection techniques · SE_VAR vulnerability analysis and response · SE_PPR product patching and remediation · SE_SEP secure engineering practices · SE_MTL monitoring changes in the threat landscape
SC — Supply Chain Security SC_RSM risk management · SC_PHS physical security · SC_ACC access controls · SC_ESS employee and supplier security and integrity · SC_BPS business partner security · SC_STR supply chain security training · SC_ISS information systems security · SC_TTC trusted technology components · SC_STH secure transmission and handling · SC_OSH open source handling · SC_CTM counterfeit mitigation · SC_MAL malware detection

The scope is the provider's own lifecycle plus the supply-chain practices it applies to third-party components, outsourced manufacturing and delivery. The 2023 scope also says it "does not apply to the operation or hosting infrastructure of online services," and that it complements product-security evaluations such as ISO/IEC 15408 (Common Criteria) rather than replacing them.

What changed in the 2023 edition?

The Open Group announced O-TTPS Version 1.2 on its blog on 5 September 2023: several requirements were clarified and "multiple requirements that were previously recommendations became mandatory." This revision became ISO/IEC 20243-1:2023 and ISO/IEC 20243-2:2023, both published in November 2023; ISO's lifecycle record shows the 2018 Part 1 withdrawn on 24 November 2023. The 2023 foreword lists the changes, including:

  • "component" now explicitly covers both hardware and software, and a definition of "security-critical" was added;
  • PD_DES.01 and PD_CFM.04 became mandatory;
  • the SE_VAR (vulnerability analysis and response) requirements were "largely reworked and reorganized," with a new mandatory requirement and several others made mandatory;
  • SE_PPR.02 and SE_PPR.04 (patching and remediation) became mandatory;
  • SC_RSM.05, SC_ACC.04, SC_ESS.02, SC_ESS.03, SC_BPS.02 became mandatory, and SC_ESS.04 was rewritten as mandatory;
  • SC_CTM.02 (counterfeit mitigation) and SC_MAL.02 (malware detection) were heavily revised and made mandatory.

For a device maker, the vulnerability-handling and patching changes are the ones most likely to expose a gap. The ISO catalogue title also changed: the 2023 Part 1 reads "...Part 1: Requirements and recommendations for mitigating maliciously tainted and counterfeit products," with the same scope.

How does O-TTPS certification work today?

The Open Group launched the program on 3 February 2014 as the O-TTPS Accreditation Program; it now runs it as the O-TTPS Certification Program, with The Open Group as Certification Authority. Key rules from the program's FAQ (January 2024):

  • It certifies organizations, not products. The organization declares a Scope of Certification in a public Conformance Statement — a product, a business unit or the whole organization.
  • Certification lasts three years. Based on the pilot program, The Open Group estimated 6–12 months to certify, depending on scope.
  • Evidence is of two kinds: process evidence (a documented process meets the requirement) and implementation evidence (the process was applied to each Selected Representative Product).
  • Work from other programs, such as a Common Criteria evaluation, may be credited if it is directly relevant.
  • Suppliers do not all need certification, but organizations must recommend O-TTPS-style practices to them.
Self-Assessed tier Third-Party Assessed tier
Who assesses The organization, via a Self-Assessed Assessment Summary; the Certification Authority does a high-level check An O-TTPS Recognized Assessor, following the Part 2 assessment procedures
Extra documents — Implementation Selection Criteria Application (ISCA) and Certification Package Document
Requirements met The same Conformance Requirements The same Conformance Requirements

On 12 November 2026 the Recognized Assessor Register listed four assessor organizations (atsec information security, GMS Registrar, Intertek EWA-Canada and NQA USA), and the Certification Register included hardware scopes such as enterprise printers, print cartridges and storage arrays. The program supports certification to Version 1.2 (ISO/IEC 20243:2023). IBM, a founding OTTF member, piloted the program and was accredited for its Application Infrastructure and Middleware (AIM) software.

Which buyers ask for ISO/IEC 20243?

US federal IT buyers are the clearest case. NASA's SEWP program keeps an ISO 20243 page listing contract holders with O-TTPS certification. For SEWP VI, the solicitation's Contract Data Requirements List (April 2024) asks contract holders for a C-SCRM plan with "an annual report noting certification with the current ISO 20243 standard including a copy of a valid active" O-TTPS certification. A component or device maker selling through such resellers may be asked for its own certification or for evidence that supports theirs.

How does O-TTPS fit next to SBOM and supply-chain risk work?

O-TTPS predates, and sits alongside rather than replaces, the SBOM-centric supply-chain practices SoftWSP guides already cover: it asks "could this specific unit have been tampered with or counterfeited in transit," a narrower question than the broader supplier-relationship risk management in ISO/IEC 27036 or NIST SP 800-161 (C-SCRM), and a different angle from the build-provenance focus of SLSA and in-toto attestations. A firmware or hardware maker already producing an SBOM and an HBOM holds part of the evidence an O-TTPS assessment would ask for — the standard adds a structured, assessable framework and a certification mark on top of that evidence.

What could a device maker's first certification scope look like?

Synthetic example, not a real company or assessment. A maker of managed network switches sells to US federal resellers and is asked for O-TTPS evidence. Its compliance lead works through the attributes:

  1. ScopeIt declares one product family (the switch line, hardware and firmware) rather than the whole company, because the cloud management portal is out of the standard's scope.
  2. TierIt starts with Self-Assessed, planning Third-Party Assessed once a reseller contract requires it.
  3. Evidence it already hasPer-release SBOMs (SC_OSH, SC_TTC), signed firmware with secure boot (SE_RTP, SC_STH), a PSIRT with a disclosure policy (SE_VAR, SE_PPR), and an approved-vendor list for flash and SoC parts (SC_CTM).
  4. GapsNo written counterfeit-parts procedure for the contract manufacturer, no malware scan of the factory programming station, no supplier security clauses (SC_BPS).
  5. PlanClose the gaps, map each attribute to a document in a simple evidence index, then file the Conformance Statement.

The attribute mapping in step 3 is the company's own judgement; the Part 2 assessment procedures decide what evidence is acceptable.

How should a device maker start?

  1. Confirm which edition you're being asked about— "O-TTPS," "ISO/IEC 20243:2015," "ISO/IEC 20243-1:2018" and "ISO/IEC 20243-1:2023" are all the same lineage at different revision points; a customer RFP citing an old edition number may still mean the current V1.2-equivalent text.
  2. Read Part 1 before Part 2— Part 1 sets the mandatory requirements; Part 2 only makes sense as the assessment procedure for those requirements, not a standalone checklist.
  3. Download The Open Group's free V1.2 texts, C225-1 (Part 1) and C225-2 (Part 2), published 5 September 2023 and free with a site login, before deciding whether to buy the ISO/IEC-branded text.
  4. Re-run any 2018-era gap assessmentagainst the list of requirements that became mandatory in 2023.
  5. Decide early which tier you need— buyers citing NASA SEWP-style requirements may expect a listing on the Certification Register, while many private buyers accept demonstrable adherence to the same practices.

What are the common pitfalls?

  • Calling a product "O-TTPS certified." Certification belongs to an organization's declared scope; the FAQ says claims may be made only for that scope.
  • Assuming suppliers are covered. Your contract manufacturer's practices count only as far as your own SC requirements reach them.
  • Treating an SBOM as the whole answer. It supports open-source handling and component evidence, not physical security, counterfeit-parts handling or employee integrity.
  • Using the 2018 checklist. More than a dozen entries in the 2023 foreword make a requirement mandatory or rework it.

SoftWSP can supply part of the vulnerability-side evidence: it extracts a CycloneDX SBOM from a firmware image, matches components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report that an engineer reviews. It is not an O-TTPS Recognized Assessor and does not certify anything: see device & firmware security.

This guide summarises ISO's and The Open Group's own published catalogue records, announcements, certification documents and the ISO/IEC preview pages; it is not a substitute for the purchased ISO/IEC text or the current Open Group V1.2 publication, and does not constitute compliance or legal advice.

Put this guide to work

Frequently asked questions

What is ISO/IEC 20243?

ISO/IEC 20243, "Information technology — Open Trusted Technology Provider™ Standard (O-TTPS)," is an ISO/IEC JTC 1 International Standard for mitigating the risk of maliciously tainted and counterfeit products across a commercial off-the-shelf (COTS) ICT product's full life cycle — design, sourcing, build, fulfillment, distribution, sustainment and disposal. It originates from The Open Group's own O-TTPS standard, first published by The Open Group in April 2013 and approved as an ISO/IEC International Standard (ISO/IEC 20243:2015) on 1 September 2015.

What's the difference between Part 1 and Part 2?

Since the 2018 edition, ISO/IEC 20243 has been split into two parts. Part 1 ("Requirements and recommendations") sets the mandatory and recommended practices a provider follows to mitigate tainted and counterfeit product risk. Part 2 ("Assessment procedures for the O-TTPS") gives the procedures an assessor follows to check conformance against Part 1's mandatory requirements, stated in ISO's own abstract as intended to "ensure the repeatability, reproducibility, and objectivity of assessments." The Open Group's own documentation describes Part 2 as the basis for demonstrating conformance with the requirements in Part 1's Clause 6.

How current is each part, and what changed in the latest revision?

The current editions are ISO/IEC 20243-1:2023 and ISO/IEC 20243-2:2023, both published in November 2023, technically equivalent to The Open Group's O-TTPS Version 1.2 (announced 5 September 2023). The Open Group's own release notes describe that revision as clarifying several requirements, converting "multiple requirements that were previously recommendations" into mandatory requirements, and adding refined evidence examples to Part 2. The prior 2018 editions (equivalent to O-TTPS V1.1.1) were formally withdrawn on 24 November 2023. The 2023 edition's full requirements text is paywalled; for the exact clause-by-clause changes, consult the purchased standard directly.

Is there a certification or accreditation program tied to this standard?

Yes. The Open Group operates the O-TTPS Certification Program, which it launched on 3 February 2014 as the O-TTPS Accreditation Program and, per The Open Group's own description, one of the first accreditation programs aimed at assuring the integrity of COTS ICT products and the global supply chain. An organization assessed as conforming can be listed on The Open Group's public O-TTPS Certification Register and identify itself as an "Open Trusted Technology Provider." IBM was a founding OTTF member and an early accredited organization, for its Application Infrastructure and Middleware (AIM) software line.

Is the standard text freely available?

Part 1's O-TTPS-equivalent text (Version 1.1.1, technically equivalent to ISO/IEC 20243-1:2018) is published by The Open Group as a free download, document number C185-1, 43 pages, dated 17 September 2018, requiring only a site registration/login. The ISO/IEC-branded PDFs of the current ISO/IEC 20243-1:2023 and -2:2023 editions sit behind ISO's normal purchase paywall; The Open Group publishes the technically equivalent Version 1.2 text as free downloads with the same login, documents C225-1 (Part 1) and C225-2 (Part 2), dated 5 September 2023.

Sources

  1. ISO: ISO/IEC 20243-1:2023 — Information technology — Open Trusted Technology Provider™ Standard (O-TTPS) — Part 1: Requirements and recommendations for mitigating maliciously tainted and counterfeit products (catalogue record, current edition)
  2. ISO: ISO/IEC 20243-2:2023 — Part 2: Assessment procedures for the O-TTPS (catalogue record, current edition)
  3. ISO: ISO/IEC 20243-1:2018 — Part 1: Requirements and recommendations (catalogue record, withdrawn 2023-11-24)
  4. ISO: ISO/IEC 20243-2:2018 — Part 2: Assessment procedures for the O-TTPS and ISO/IEC 20243-1:2018 (catalogue record, withdrawn)
  5. The Open Group: O-TTPS Version 1.1.1, Part 1 — Requirements and Recommendations (free PDF, document C185-1, 17 September 2018, technically equivalent to ISO/IEC 20243-1:2018)
  6. The Open Group Blog: "Announcing Version 1.2 of the Open Trusted Technology Provider™ Standard (O-TTPS)" (5 September 2023)
  7. The Open Group: "The Open Trusted Technology Provider™ Standard (O-TTPS) Approved as ISO/IEC International Standard" (announcement, 1 September 2015)
  8. Wikipedia: "Open Trusted Technology Provider Standard" (secondary summary, for the OTTF/accreditation program history cross-check)
  9. ISO/IEC 20243-1:2023 publisher preview (foreword, introduction, scope), via iTeh Standards
  10. ISO/IEC 20243-1:2018 publisher preview (contents with attribute titles), via iTeh Standards
  11. The Open Group: O-TTPS Version 1.2, Part 1 — Requirements and Recommendations (free PDF, document C225-1, 5 September 2023)
  12. The Open Group: O-TTPS Version 1.2, Part 2 — Assessment Procedures (free PDF, document C225-2, 5 September 2023)
  13. The Open Group: O-TTPS Certification Program
  14. The Open Group: O-TTPS Certification Program FAQ (January 2024)
  15. The Open Group: O-TTPS Certification Register
  16. The Open Group: O-TTPS Recognized Assessor Register
  17. NASA SEWP: ISO 20243 (SCRM)
  18. NASA SEWP VI solicitation 80TECH24R0001, Attachment D: Contract Data Requirements List (April 2024)
Was this guide helpful?

In this cluster

ISO/IEC 20243 (O-TTPS): mitigating maliciously tainted and counterfeit products, explained