• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer

Microcontroller Tips

Microcontroller engineering resources, new microcontroller products and electronics engineering news

  • Products
    • 8-bit
    • 16-bit
    • 32-bit
    • 64-bit
  • Applications
    • 5G
    • Automotive
    • Connectivity
    • Consumer Electronics
    • EV Engineering
    • Industrial
    • IoT
    • Medical
    • Security
    • Telecommunications
    • Wearables
    • Wireless
  • Learn
    • eBooks / Tech Tips
    • EE Training Days
    • FAQs
    • Learning Center
    • Tech Toolboxes
    • Webinars/Digital Events
  • Resources
    • Design Guide Library
    • DesignFast
    • LEAP Awards
    • Podcasts
    • White Papers
  • Videos
    • EE Videos & Interviews
    • Teardown Videos
  • EE Forums
    • EDABoard.com
    • Electro-Tech-Online.com
  • Engineering Training Days
  • Advertise
  • Subscribe

Securing devices for the IoT – FIPS 140-3 and common criteria

February 19, 2024 By Jeff Shepard Leave a Comment

For developers of IoT devices and networks, the Federal Information Processing Standard (FIPS) 140-3 and the Common Criteria (CC) serve different but complementary functions. FIPS 140-3 is designed for validating software and hardware in cryptographic modules, while CC is designed to evaluate security functions in IT software and hardware. In both cases, there are related standards from the International Standards Organization (ISO) and the International Electrotechnical Commission (IEC).

FIPS testing is a prerequisite for CC certification since all security products covered by CC include hardware cryptographic modules. FIPS 140-3 aligns with the ISO/IEC 19790 standard for Security Requirements for Cryptographic Modules, and ISO/IEC 24759 specifies the test methods to be used to confirm that a cryptographic module conforms to ISO/IEC 19790.

When FIPS 140-3 was published in 2019, a five-year sunset period was announced for FIPS 140-2 certificates. FIPS 140-3 includes enhancements in several areas, including cryptographic module specifications, cyber-attack mitigation requirements, self-tests, operational environment requirements, and firmware security (Figure 1).

Figure 1. FIPS 140-3 key changes (Image: SignMyCode).

The four FIPS 140-3 levels include:

  • Level 1: Uses externally tested algorithms and production-grade equipment.
  • Level 2: Adds role-based and physical tamper-evidence authentication.
  • Level 3: Adds tamper-resistance and identity-based authentication. This level also requires the module to detect and react to out-of-range voltage or temperature, called environmental failure protection (EFP), or alternatively undergo environmental failure testing (EFT).
  • Level 4: Increases the severity of the physical security requirements, including the ability to be tamper-active, and erase the contents of the device if it detects various forms of environmental attack. It must have EFP, protection against fault injection, and multi-factor authentication.

Common criteria
Each country has its own CC authority. In the U.S., CC is administered by the National Information Assurance Partnership (NIAP). CC and the Common Methodology for Information Technology Security Evaluation (CME) are the technical basis for the international CC Recognition Arrangement (CCRA).

CC is formalized in ISO/IEC 15408, Common Criteria for Information Technology Security Evaluation, a security standard that can achieve comparability between the results of independent security evaluations of IT products. Key concepts in CC include:

  • Target of Evaluation (TOE) is the product or device being evaluated.
  • Protection Profile (PP) identifies security requirements for a class of security devices.
  • Security Target (ST) describes the security properties of the TOE and can require conformance with one or more PPs.

CC is based on a general security model that’s described in ISO/IEC 15408 (Figure 2). The model assumes that TOE owners want to implement countermeasures to minimize cyber risks. PPs are used to describe the security needs of a class of TOEs, like client virtual private network (VPN) applications. TOE developers publish their security claims in the form of STs. A CC evaluation determines if the ST is compliant with a specific PP.

Figure 2. ISO/IEC 15408 CC general security model (Image: A Structured Comparison of Security Standards).

Summary
FIPS 140-3 and CC are complementary standards for IoT cyber security. FIPS 140 is focused on validating software and hardware in cryptographic modules, while CC focuses on security functions in IT software and hardware. Both are based on a series of ISO/IEC standards, and FIPS testing is a prerequisite for CC certification.

References
A Structured Comparison of Security Standards, ResearchGate
Common Criteria, Wikipedia
Common Criteria Portal
FIPS 140-2 Vs 140-3, SignMyCode
FIPS 140-3 certification, Thales
FIPS 140-3 Security Requirements for Cryptographic Modules, Encryption Consulting
ISO/IEC 15408-1:2022: Information security, cybersecurity and privacy protection – Evaluation criteria for IT security, ISO
What is FIPS 140-3? Entrust

You may also like:


  • Securing devices for the IoT — IEC 62443, SESIP, and…

  • Securing devices for the IoT — managing memory

  • Securing devices for the IoT – firmware, software, and OTA

  • Securing devices for the IoT — minimize the attack surface

  • Matter 1.2 is here — what does that mean for the…

Filed Under: Applications, FAQ, Featured, IoT, Security Tagged With: FAQ

Reader Interactions

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

Featured Contributions

Five challenges for developing next-generation ADAS and autonomous vehicles

Securing IoT devices against quantum computing risks

RISC-V implementation strategies for certification of safety-critical systems

What’s new with Matter: how Matter 1.4 is reshaping interoperability and energy management

Edge AI: Revolutionizing real-time data processing and automation

More Featured Contributions

EE TECH TOOLBOX

“ee
Tech Toolbox: Internet of Things
Explore practical strategies for minimizing attack surfaces, managing memory efficiently, and securing firmware. Download now to ensure your IoT implementations remain secure, efficient, and future-ready.

EE Learning Center

EE Learning Center

EE ENGINEERING TRAINING DAYS

engineering
“bills
“microcontroller
EXPAND YOUR KNOWLEDGE AND STAY CONNECTED
Get the latest info on technologies, tools and strategies for EE professionals.

RSS Current EDABoard.com discussions

  • Lightbox circuit help
  • 12VAC to 12VDC 5A on 250ft 12AWG
  • Battery sensing circuitry for coin cell application
  • Input impedance matching network
  • Voltage Regulator Sizing Question

RSS Current Electro-Tech-Online.com Discussions

  • Lightbox circuit
  • Kawai KDP 80 Electronic Piano Dead
  • Python help with keystroke entries
  • Do resistors fail like dominoes?
  • Fuel Auto Shutoff

DesignFast

Design Fast Logo
Component Selection Made Simple.

Try it Today
design fast globle

Footer

Microcontroller Tips

EE World Online Network

  • 5G Technology World
  • EE World Online
  • Engineers Garage
  • Analog IC Tips
  • Battery Power Tips
  • Connector Tips
  • DesignFast
  • EDA Board Forums
  • Electro Tech Online Forums
  • EV Engineering
  • Power Electronic Tips
  • Sensor Tips
  • Test and Measurement Tips

Microcontroller Tips

  • Subscribe to our newsletter
  • Advertise with us
  • Contact us
  • About us

Copyright © 2025 · WTWH Media LLC and its licensors. All rights reserved.
The material on this site may not be reproduced, distributed, transmitted, cached or otherwise used, except with the prior written permission of WTWH Media.

Privacy Policy