OneClickComply
    UL 2900-2-2Supported in OneClickComply

    Prepare your ICS products for UL 2900-2-2 security testing

    UL 2900-2-2 is the part of the UL 2900 series that sets particular cyber security requirements for network-connectable industrial control system products. It is applied together with UL 2900-1 and looks at product documentation, security controls such as authentication and remote access, secure development, and testing for vulnerabilities, malware, malformed input and software weaknesses. It was first published by UL as an Outline of Investigation in 2016.

    See the UL 2900-2-2 requirements
    UL 2900-2-2 Aligned
    Automated Evidence
    OneClickFix Enabled
    Continuous Monitoring
    In-House Audit Team
    Who needs UL 2900-2-2

    Is UL 2900-2-2 right for your organisation?

    UL 2900-2-2 is aimed at manufacturers of industrial control system components, including PLCs, distributed control systems, SCADA servers, RTUs, IEDs and HMIs. It is voluntary, but becomes important when utilities, manufacturers or other critical infrastructure buyers ask for independent evidence that a connected product has been security tested before purchase.

    Adopting it is voluntary, though customers and auditors often expect it.

    UL 2900-2-2 at a glance
    Issued by
    UL (Underwriters Laboratories)
    Document type
    Outline of Investigation, part of the UL 2900 series
    Edition
    First edition, 2016
    Used with
    UL 2900-1 general requirements
    Applies to
    Industrial control system components such as PLCs, DCS, SCADA servers, RTUs and HMIs
    Requirement
    Voluntary, often requested by ICS buyers
    Assessment route
    Product testing and evaluation by a testing laboratory
    Type
    Standard (voluntary)
    Region
    Global
    In OneClickComply
    Supported today
    How we help

    OneClickComply makes it simple

    UL 2900-2-2 is mapped in OneClickComply's control library and is available on request. We help you organise the organisational side of readiness, such as secure development policies, patch and vulnerability management processes, access control evidence and vendor risk records, and map them to controls you already run for frameworks like ISO 27001 and IEC 62443. Product testing and any UL certification remain with an accredited laboratory.

    Requirements covered

    Sections 4 to 19 that apply the UL 2900-1 structure to ICS products: product documentation, risk controls such as access control, remote communication and fail-safe behaviour, product management and secure development, and testing for known vulnerabilities, malware, malformed input, penetration and software weaknesses.

    Already working towards another framework?

    • SOC 270% of UL 2900-2-2 overlaps
    • NIST CSF65% of UL 2900-2-2 overlaps
    • GDPR2% of UL 2900-2-2 overlaps

    Evidence you collect once counts towards every framework it applies to.

    Manual UL 2900-2-2 vs. OneClickComply

    Manual UL 2900-2-2
    • Tracking secure development and patch integrity evidence across scattered tools and documents
    • Writing product security and development policies from scratch
    • Chasing engineering teams for screenshots of access control and authentication settings
    • Duplicating effort for UL 2900-2-2, IEC 62443 and ISO 27001
    • Discovering control gaps only when the testing laboratory starts its evaluation
    With OneClickComply
    • Evidence collected automatically from connected tools and stored in one place
    • Audit-ready policies generated from your real environment
    • The Companion AI browser agent gathers settings evidence from admin consoles
    • One set of controls mapped across UL 2900-2-2 and your other frameworks
    • Continuous monitoring flags drift before a laboratory evaluation begins
    Capabilities

    Everything you need for UL 2900-2-2

    UL 2900-2-2 mapped to your existing security controls, available on request

    AutoComplete policies for secure development, patching and access control

    Automated evidence collection from 13,000+ integrations

    Continuous monitoring with alerts when controls drift

    Vendor risk management for third-party software components

    Penetration testing and Ask an Auditor guidance from our in-house team

    How it works

    Three steps to UL 2900-2-2 compliance

    01

    Connect & scan

    Connect your cloud, identity and SaaS tools. OneClickComply checks them against UL 2900-2-2 and shows you exactly where you stand.

    02

    Fix & generate

    OneClickFix remediates technical gaps in one click, and AutoComplete generates UL 2900-2-2-aligned policies from your real environment.

    03

    Monitor & evidence

    Continuous monitoring keeps you compliant, and our in-house audit team is on hand when you need expert guidance.

    Requirements

    UL 2900-2-2 requirements

    The main sections of UL 2900-2-2 and its key ICS-specific sub-requirements, with short descriptive titles that follow the UL 2900 series structure.

    ReferenceRequirement
    4Product documentation
    5Product design documentation
    6Documentation for product use
    7Risk controls: general
    8Access control, user authentication and user authorisation
    8.2Remote access
    8.3Operating environment
    8.5Identity and access management
    8.6Authentication, authorisation and audit
    8.8Re-authentication
    8.9Authenticator management
    8.10Protection of authenticators and trusted path
    9Remote communication
    9.6Fail-safe operation
    10Sensitive data
    11Product management
    11.3Secure software development practices
    11.4Software patch integrity
    12Vendor product risk management process
    13Known vulnerability testing

    Always check the official UL 2900-2-2 text for the exact wording.

    UL 2900-2-2 FAQs

    What is UL 2900-2-2?

    UL 2900-2-2 is a UL Outline of Investigation that sets particular cyber security requirements for network-connectable industrial control system products. Published as its first edition in 2016, it is part 2-2 of the UL 2900 series and is used together with UL 2900-1, the general requirements, to test products such as PLCs, distributed control systems, SCADA servers, RTUs and HMIs for vulnerabilities, software weaknesses and missing security controls.

    Is UL 2900-2-2 mandatory?

    No. UL 2900-2-2 is a voluntary document, and no law requires ICS products to be tested against it. Manufacturers usually pursue it because asset owners, system integrators or procurement teams ask for independent evidence that a controller, gateway or HMI has been security tested. In practice it becomes a contractual requirement when a customer writes it into a tender or supply agreement.

    How is UL 2900-2-2 different from UL 2900-1?

    UL 2900-1 contains the general software cyber security requirements for any network-connectable product. UL 2900-2-2 is a product-specific part that applies those requirements to industrial control systems, adding particular requirements suited to operational technology, such as remote access, authenticator protection and fail-safe behaviour. A product evaluated to UL 2900-2-2 is assessed against UL 2900-1 together with the ICS-specific requirements in part 2-2.

    Who needs UL 2900-2-2?

    Manufacturers and vendors of industrial control system components are the main audience. That includes makers of programmable logic controllers, distributed control systems, SCADA servers, remote terminal units, intelligent electronic devices and human machine interfaces. It is most relevant when selling into critical infrastructure, utilities, manufacturing or building automation, where buyers want third-party evidence that connected products resist known attacks.

    How does UL 2900-2-2 relate to IEC 62443?

    Both address the security of industrial control system products, but they work differently. IEC 62443 is an international series covering security programmes, secure development and component and system security levels. UL 2900-2-2 is a UL testing document focused on evaluating a specific product for vulnerabilities, malware, malformed input handling, software weaknesses and security controls. Many ICS vendors treat IEC 62443 as the primary framework and use UL testing as supporting evidence.

    How do you comply with UL 2900-2-2?

    You prepare product and design documentation, implement the required security controls, and then submit the product to a testing laboratory for evaluation. Testing typically covers known vulnerability scanning, malware testing, malformed input or fuzz testing, structured penetration testing and software weakness analysis of source code or binaries. Evidence of secure development practices, patch integrity and a vendor risk management process is also reviewed alongside the product itself.

    Does OneClickComply support UL 2900-2-2?

    UL 2900-2-2 is mapped in OneClickComply's control library and is available on request, rather than being a live framework in the platform today. On request, the mapping links its documentation, secure development and product management expectations to controls you may already run for ISO 27001 or IEC 62443, so evidence is collected once. OneClickComply does not test products or issue UL certification.

    Get UL 2900-2-2 ready, not stressed

    Automate controls, gather evidence continuously and stay audit-ready, all on one platform.