Engineer working on a laptop connected to a device test rig, surrounded by wiring harnesses and test hardware

Firmware vulnerabilities & fixes

OWASP Firmware Security Testing Methodology (FSTM), explained

Last updated:

The OWASP Firmware Security Testing Methodology (FSTM) is a free, nine-stage firmware security testing playbook, published by the OWASP Internet of Things project since November 2019 under the Creative Commons Attribution Share Alike 4.0 International licence. First released in November 2019 by project lead Aaron Guzman (@scriptingxss), FSTM's own overview states it "comprises nine structured stages designed to help security researchers, software developers, consultants, hobbyists, and information security professionals conduct comprehensive firmware security assessments." Rather than a list of controls a device must have, FSTM is a sequence of concrete testing steps, with named tools and example commands, for going from a firmware image to evidence of exploitable vulnerabilities.

Key takeaways

  • Stage 3 decides whether extraction can work at all.
  • Stage 5 directs testers to search extracted filesystem contents for "legacy insecure network daemons such as telnetd...
  • Stage 9 is explicit that exploit development is a distinct skill from vulnerability discovery: "Developing exploit code requires programming experience in lower level languages (e.g.
  • Decide first how much of Stages 1–4 you want to pay for.

What are the nine stages?

Stage Name What it covers
1 Information gathering and reconnaissance Acquire technical and documentation details — CPU architecture, bootloader, schematics, datasheets, source location, third-party components, licences, changelogs, FCC IDs, threat models, prior pentest reports
2 Obtaining firmware Acquire the firmware image: from the vendor/manufacturer, update-server MITM, cloud storage exposure, hardware extraction (UART/JTAG), or chip removal as a last resort
3 Analyzing firmware Identify file characteristics, platform and possible encryption (via entropy analysis) using file, strings, binwalk and similar utilities
4 Extracting the filesystem Carve and unpack filesystem contents (squashfs, ubifs, romfs, jffs2, cramfs, etc.) for review, typically with binwalk -ev
5 Analyzing filesystem contents Statically analyze extracted configuration files and binaries for hardcoded credentials, insecure daemons, update-server endpoints and command-injection-prone startup scripts
6 Emulating firmware Emulate standalone binaries (user-mode) or the full firmware image, via QEMU, a real device, or a matching virtual machine
7 Dynamic analysis Test the running firmware/application interfaces — web/API testing, fuzzing, bootloader and firmware-integrity tampering
8 Runtime analysis Attach a debugger (gdb-multiarch) to a running process to find overflows and crashes in compiled binaries
9 Binary Exploitation Build a working proof-of-concept for an identified vulnerability, using techniques such as return-oriented programming (ROP) where runtime protections are present

FSTM's own note on sequencing: "Consider visiting the OWASP Internet of Things Project page and GitHub repository for the latest methodology updates and forthcoming project releases," signalling the document is actively maintained rather than frozen at its 2019 release — the current text adds static-analysis tooling (Cppcheck, Flawfinder, Clang-Tidy, CodeQL, Semgrep) and a Software Bill of Materials section referencing CISA's minimum SBOM elements, both absent from the original release. The current FSTM text also lists binwalk v3 (a Rust rewrite) and unblob among its extraction tools, and advises generating an SBOM "during initial firmware acquisition (Stage 2) to establish a baseline".

How do testers obtain and extract firmware (Stages 2-4)?

Stage 2 lists acquisition methods in roughly increasing order of difficulty: directly from the manufacturer or vendor support site; via man-in-the-middle capture of an update; through exposed cloud storage (with an explicit caveat to "follow local laws and regulations when downloading data from exposed cloud provider storage services"); from hardware debug interfaces such as UART or JTAG; or, as a last resort, by desoldering the flash chip. FSTM recommends requesting both debug and release builds "to maximize testing coverage... in the event debug code or functionality is compiled within a release." Stage 4 then carves the extracted image's filesystem with binwalk -ev, falling back to manual offset carving with dd when binwalk's signature database does not recognize the filesystem's magic bytes — the methodology walks through squashfs, cpio, jffs2 and ubifs extraction commands as worked examples.

Stage 3 decides whether extraction can work at all. FSTM notes the image may be bare-metal, an RTOS with a custom filesystem, or encrypted, and checks with an entropy plot (binwalk -E): low entropy means the image is "not likely to be encrypted", high entropy means it is likely encrypted or compressed. An encrypted update file is good practice, but it moves the test effort: testers then need the decrypted image from you, or a dump from a unit, before Stages 4 and 5 can start.

What happens in static and dynamic analysis (Stages 5-8)?

Stage 5 directs testers to search extracted filesystem contents for "legacy insecure network daemons such as telnetd... hardcoded credentials (usernames, passwords, API keys, SSH keys, and backdoor variants)... hardcoded API endpoints... [and] startup scripts for remote code execution," using tools such as firmwalker for pattern-based scanning and FACT or EMBA for automated component identification, CVE correlation and binary-mitigation detection (NX, DEP, ASLR, stack canaries, RELRO). From Stage 6 onward the testing shifts from static inspection to a running target: Stage 7's dynamic analysis covers embedded web-application testing (default credentials, directory traversal, injection in diagnostic pages), bootloader tampering (interrupting boot to reach a U-Boot shell, modifying bootargs to add init=/bin/sh), and firmware-integrity testing (uploading a custom image to check signature verification); Stage 8's runtime analysis attaches a debugger to the emulated or live binary to set breakpoints on functions like memcpy and strcmp and fuzz for overflows.

How does Stage 9 work, and how does FSTM fit with ISTG and ISVS?

Stage 9 is explicit that exploit development is a distinct skill from vulnerability discovery: "Developing exploit code requires programming experience in lower level languages (e.g. ASM, C/C++, shellcode, etc.) as well as background within the particular target architecture," and names return-oriented programming as the technique needed when NX/DEP/ASLR protections — uncommon in embedded systems, per FSTM's own observation, but not absent — block a straightforward shellcode injection.

FSTM is deliberately scoped to the firmware image alone. The methodology states its complementary documents cover the rest of a device's attack surface: the OWASP IoT Security Testing Guide (ISTG) "provides additional test cases for hardware interfaces, wireless protocols, network services, and user interfaces," while the OWASP IoT Security Verification Standard (ISVS) "defines WHAT security controls must be implemented, while FSTM defines HOW to test firmware components." OWASP's own recommendation is to use the three together — ISVS as the requirements checklist, ISTG for the device's broader surface, FSTM for the firmware binary — rather than treating any one as sufficient on its own. OWASP also maintains IoTGoat, a deliberately vulnerable firmware image used in FSTM's own worked examples, as practice material for applying the methodology end to end.

The ISTG test case catalogue is organised by device component. This is where FSTM's firmware focus sits inside it:

ISTG category Typical tests Covered by FSTM?
Firmware (ISTG-FW), installed firmware and update mechanism Image analysis, secrets, update integrity Yes, Stages 2–9
Data Exchange Services (ISTG-DES) Network services and APIs on the device Partly, Stage 7
User Interfaces (ISTG-UI) Web UI, local and companion interfaces Partly, Stage 7
Internal Interfaces (ISTG-INT), UART and I2C Console access, bus sniffing Only as a firmware source in Stage 2
Physical Interfaces (ISTG-PHY) External ports No
Wireless Interfaces (ISTG-WRLS) Radio protocols No
Processing Units (ISTG-PROC) and Memory (ISTG-MEM) Chip-level and storage tests Only as a firmware source in Stage 2

For the requirement side, see our OWASP ISVS guide and the OWASP IoT Top 10.

How should a device maker scope an FSTM-style test?

Decide first how much of Stages 1–4 you want to pay for. A black-box test spends days obtaining, decrypting and unpacking an image you already have. A grey-box test hands that material over, and the budget goes to Stages 5–9, where the findings are. FSTM's Stage 1 list doubles as a hand-over checklist:

Hand over Stage it shortens Note
Release and debug builds of the same version 2, 7, 8 FSTM asks for both to catch debug code left in release
Decryption keys or a decrypted image 3, 4 Without them, an encrypted image can stall the test
Component list or SBOM, licences, changelog 1, 5 Lets testers go straight to version-specific CVEs
Datasheets, schematics, boot and update design 1, 2, 7 Points testers to debug pads and the update path
Threat model and earlier pentest reports 1 Avoids re-testing closed findings
Two or three production-state units 6, 7, 8 Emulation does not always work; spare units cover bricking

Agree the rules too: which interfaces are in scope (only firmware, or the ISTG categories above as well), whether exploitation (Stage 9) is wanted or a confirmed crash is enough, and how findings flow into your PSIRT. See PSIRT setup for a hardware company.

What evidence does each stage produce, and which requirement can it support?

FSTM output is test evidence, and several regulations ask for exactly that kind of record. The Cyber Resilience Act, Annex I Part II (3), requires manufacturers to "apply effective and regular tests and reviews of the security of the product", and ETSI EN 303 645 V3.1.3 sets testable provisions. The mapping below shows where stage output can support a requirement; it does not make the test a conformity assessment.

Stage output Can support
Component list and SBOM (Stages 3–5) CRA Annex I Part II (1): identify and document components, including an SBOM
Known CVEs in identified components (Stage 5) CRA Annex I Part I (2)(a): made available on the market without known exploitable vulnerabilities
Hard-coded or shared default passwords (Stage 5) ETSI 5.1-1: passwords unique per device or set by the user
Legacy daemons such as telnetd, open debug consoles (Stages 5, 7) ETSI 5.6-1 and 5.6-4A: unused interfaces disabled, debug interfaces disabled or protected; CRA (2)(j) attack surface
Unsigned image accepted, U-Boot shell reachable (Stage 7) ETSI 5.7-1 secure boot; CRA (2)(f) integrity of programs
Fuzzing and injection results on web UI and APIs (Stage 7) ETSI 5.13-1A and 5.13-1B: validate input via user and network interfaces
Retest after fixes, per release CRA Annex I Part II (3): regular tests and reviews

See CRA Annex I explained, ETSI EN 303 645 explained and secure boot and hardware root of trust.

Worked example: what does an FSTM-style plan look like for one camera?

Synthetic example. The company, camera and plan are invented for this guide; no findings are reported.

A hypothetical maker of an embedded-Linux Wi-Fi camera commissions a grey-box test before a CRA release. The plan, by stage:

  1. Stages 1–2, hand-overRelease and debug images of firmware 2.4, the decryption key for the update package, the SBOM, the boot and update design note, and three production-state units.
  2. Stage 3Entropy check on the decrypted image, identification of the bootloader, kernel and root filesystem type.
  3. Stage 4Unpack the squashfs root filesystem and the web UI assets; record any partition that cannot be unpacked.
  4. Stage 5Search for credentials, keys and certificates; list network daemons started at boot; match component versions to known CVEs; check binaries for NX, stack canaries and RELRO.
  5. Stage 6Emulate the web server and the ONVIF service in user mode; fall back to a unit where emulation fails.
  6. Stage 7Test the web UI and API for injection and authentication bypass, fuzz the RTSP and discovery services, interrupt U-Boot on the UART, and try installing a modified, unsigned image.
  7. Stage 8Attach gdb-multiarch to any service that crashes under fuzzing to classify the crash.
  8. Stage 9Proof of concept only for findings rated high, to confirm exploitability.
  9. ReportEach finding with the stage, evidence, CWE, affected versions and a retest result after the fix.

Before commissioning, the team can rehearse on OWASP's IoTGoat, "a deliberately insecure firmware" that FSTM uses in its own examples.

What are the common pitfalls?

  • Stopping after the automated scan. FACT or EMBA output covers Stages 3–5; the exploitable issues usually surface in Stages 7–8.
  • Testing only the release build when a debug build would show code left in by mistake.
  • An encrypted image with no key handed over, so most of the budget goes on extraction.
  • Skipping a service because emulation failed instead of testing it on a unit.
  • Leaving the update path out of scope, although it is where signature checks fail.
  • Acquiring images from exposed cloud storage without checking local law, as FSTM itself warns.
  • One test per product life instead of a retest per release.
  • Findings that never reach the PSIRT, so fixed issues are not disclosed and tracked.

Why does this matter for device and firmware makers?

FSTM is a testing methodology, not a regulatory control — no regulation known to us names FSTM itself as a required step, so a claim that completing an FSTM-style assessment alone satisfies the EU Cyber Resilience Act, RED/EN 18031 or similar regimes should not be assumed. Where it is directly useful is as a structured way to generate the kind of technical evidence — hardcoded-credential findings, confirmed memory-corruption or command-injection vulnerabilities, exploitability proof — that a vulnerability-handling process or secure-development lifecycle narrative does need to produce. A firmware SBOM answers what components are inside an image; an FSTM-style assessment answers whether those components, and the glue code around them, are actually exploitable.

Where does SoftWSP fit in an FSTM-style assessment?

SoftWSP automates part of Stages 3–5: it extracts a software bill of materials from the firmware image as CycloneDX JSON and matches the components against NVD, CISA KEV, FIRST EPSS and CISA ICS advisories. An AI-drafted report cites each source, and an engineer reviews it before you receive it. It does not emulate, fuzz or exploit firmware, and it does not judge whether a matched vulnerability is reachable on your device; Stages 6–9 stay with your testers. See device & firmware security.

This guide summarises the public OWASP FSTM documentation (CC BY-SA 4.0); it does not constitute legal or compliance advice.

Put this guide to work

Frequently asked questions

What is the OWASP Firmware Security Testing Methodology (FSTM)?

FSTM is an OWASP Internet of Things project document that, per its own overview, "comprises nine structured stages designed to help security researchers, software developers, consultants, hobbyists, and information security professionals conduct comprehensive firmware security assessments." It was first released under OWASP in November 2019 by Aaron Guzman (@scriptingxss), who leads the project, and is published under the Creative Commons Attribution Share Alike 4.0 International licence. Unlike a compliance standard, FSTM is a testing playbook: a sequence of stages, with concrete tool commands, for examining a firmware image rather than a checklist of controls a product must have.

What are the nine stages of FSTM?

1) Information gathering and reconnaissance; 2) Obtaining firmware; 3) Analyzing firmware; 4) Extracting the filesystem; 5) Analyzing filesystem contents; 6) Emulating firmware; 7) Dynamic analysis; 8) Runtime analysis; 9) Binary Exploitation. The methodology's own description frames the arc as: "Acquire all relative technical and documentation details... Attain firmware... Examine the target firmware's characteristics... Carve filesystem contents... Statically analyze extracted filesystem configuration files and binaries for vulnerabilities... Emulate firmware files and components... Perform dynamic security testing... Analyze compiled binaries during device runtime... Exploit identified vulnerabilities discovered in previous stages to attain root and/or code execution."

How does FSTM relate to OWASP's ISTG and ISVS?

FSTM documents its own place in OWASP's wider IoT work directly: this firmware-specific methodology "complements the OWASP IoT Security Testing Guide (ISTG), which provides additional test cases for hardware interfaces, wireless protocols, network services, and user interfaces," while "the OWASP IoT Security Verification Standard (ISVS) defines WHAT security controls must be implemented, while FSTM defines HOW to test firmware components." The guidance is to use all three together: ISVS as the control checklist, ISTG for the device's non-firmware attack surface, and FSTM for the firmware image itself.

What tools does FSTM reference for each stage?

Named tools vary by stage: binwalk for identifying and carving firmware filesystems (Stage 3-4); firmwalker, Cppcheck, Flawfinder, Clang-Tidy, CodeQL and Semgrep for static analysis of extracted filesystem contents and source (Stage 5); QEMU-based partial or full-system emulation (Stage 6); OWASP ZAP, Burp Suite, Commix, AFL, Mutiny, boofuzz, kitty, Nmap, NCrack and Metasploit for dynamic testing (Stage 7); gdb-multiarch for attaching to running binaries (Stage 8); and ROPGadget for building exploit chains against identified vulnerabilities (Stage 9). FSTM also names FACT and EMBA as combined automated-analysis frameworks spanning extraction through dynamic analysis.

Does passing FSTM satisfy a regulation like the Cyber Resilience Act?

No. FSTM is an OWASP testing methodology, not a named control in the EU Cyber Resilience Act, RED/EN 18031 or any other regulation known to us as of this guide's publication; no regulation confirms that an FSTM-based assessment equates to regulatory conformity. What FSTM is useful for is structuring the technical testing work (and resulting evidence) that can feed a vulnerability-handling or secure-development narrative a regulation does require.

Sources

  1. OWASP Firmware Security Testing Methodology (FSTM) — scriptingxss.gitbook.io
  2. GitHub: scriptingxss/owasp-fstm (source repository, CC BY-SA 4.0 licence file)
  3. OWASP: Internet of Things project page (project home, licence, related resources)
  4. OWASP IoT Security Testing Guide (ISTG) project page
  5. GitHub: OWASP/IoT-Security-Verification-Standard-ISVS
  6. GitHub: OWASP/owasp-istg (IoT Security Testing Guide, test case catalogue)
  7. GitHub: OWASP/IoTGoat (deliberately insecure firmware)
  8. ETSI EN 303 645 V3.1.3 (2024-09): Cyber Security for Consumer Internet of Things: Baseline Requirements
  9. Regulation (EU) 2024/2847 (Cyber Resilience Act), Annex I

About this guide

SoftWSP Firmware Security Desk

Covers the Firmware vulnerabilities & fixes cluster: 131 guides.

Was this guide helpful?

All guides in this cluster: Firmware vulnerabilities & fixes

Avahi and mDNS/DNS-SD vulnerabilities in embedded Linux: find the responder and version, rank the CVEs, keep port 5353 on the local linkWhere avahi-daemon and other mDNS responders ship in devices, how to find the version, which Avahi CVEs matter and how to keep UDP 5353 on the local link.Bluetooth Low Energy (BLE) security for IoT devices: why pairing and open GATT are still the real riskBLE's own AES-CCM encryption is sound; real 2025-2026 CISA advisories and actual BlueZ/Zephyr CVEs show the exploitable gap is unauthenticated pairing and open GATT characteristics in firmware.BlueZ and Linux Bluetooth vulnerabilities in embedded devices: find the versions, rank the CVEs, harden and patchWhere BlueZ and the kernel Bluetooth stack ship, how to find both versions, which CVEs matter (BleedingTooth, CVE-2023-45866), how to harden and patch.BMC, IPMI and Redfish vulnerabilities in embedded firmware: identify the stack, rank the CVEs, lock down the management planeWhy a BMC is a privileged always-on computer, how to identify MegaRAC or OpenBMC in an image, which IPMI and Redfish CVEs matter, and how to fix them.BSIMM16: the Building Security In Maturity Model, explainedBSIMM is a descriptive model built from 111 real firms' software security practices — 128 activities across 12 practices and 4 domains. What BSIMM16 (2026) actually measures, how it differs from a prescriptive framework like OWASP SAMM, and what its own 2026 data says about AI's effect on software security programs.BusyBox vulnerabilities in embedded Linux firmware: identify, prioritise and fixWhy one BusyBox binary carries many CVEs, how to find its version and enabled applets in a firmware image, and how to prioritise and fix them.CIS Critical Security Controls v8.1, explainedCIS Critical Security Controls v8.1 explained: the 18 Controls, the 153 Safeguards, the cumulative IG1/IG2/IG3 Implementation Groups, and what changed from v8 to v8.1.CISA Cross-Sector Cybersecurity Performance Goals (CPGs), explainedCISA's Cross-Sector Cybersecurity Performance Goals, version 2.0: the GOVERN/Identify/Protect/Detect/Respond/Recover structure, how many goals exist, NSM-5 origin, and how CPGs differ from the NIST CSF.CISA and NSA's 'Deploying AI Systems Securely' guidance, explainedThe joint NSA/CISA/FBI/Five Eyes Cybersecurity Information Sheet published 15 April 2024: its deployment-environment, validation, access-control and monitoring best practices, who it's written for, and how the 2025 AI Data Security follow-up extends it.CISA/FBI Product Security Bad Practices, explainedThe CISA/FBI Product Security Bad Practices catalog (Version 2, January 2025): all 13 bad practices across product properties, security features and organizational process, the memory-safety roadmap deadline, and what changed since the October 2024 draft.CISA Secure by Design: the principles and the pledge, explainedCISA Secure by Design: the three core principles, and the seven measurable goals of the voluntary Secure by Design Pledge for software and device makers.CoAP security: the amplification risk built into a constrained-device protocolRFC 7252's CoAP runs over UDP with no security by default, and Shadowserver's internet-wide scans have repeatedly found hundreds of thousands of exposed CoAP hosts with a roughly 27-34x DDoS amplification factor. What CoAP's own security modes and OSCORE actually protect, and what real libcoap/Californium CVEs have found.CVSS v4.0 vs v3.1: what actually changed in vulnerability scoringFIRST CVSS v4.0 explained: Attack Requirements, Vulnerable vs Subsequent System impact, Supplemental metrics, and the CVSS-B/BE/BT/BTE labels vs v3.1.CWE Top 25 Most Dangerous Software Weaknesses, explainedMITRE's CISA-sponsored CWE Top 25 Most Dangerous Software Weaknesses: how the frequency × severity score is calculated, the current ranked list, and what changed in the 2025 methodology.DHCP vulnerabilities in embedded firmware: find the client and server, rank the CVEs, harden option handlingWhere udhcpc, dhcpcd, ISC DHCP, Kea and odhcpd ship in devices, why DHCP option parsing is pre-auth attack surface, which CVEs matter and how to fix them.Dnsmasq vulnerabilities in embedded firmware: identify, prioritise and fixWhich dnsmasq CVEs matter for routers and gateways (DNSpooq and the 2026 set), how to find the version and DNSSEC, DHCP and TFTP options, and how to fix them.Dropbear SSH vulnerabilities in embedded firmware: identify, prioritise and fixWhich Dropbear CVEs matter (Terrapin and more), how to find the Dropbear version and build options in a firmware image, and how to prioritise and fix them.Yocto and Buildroot SBOMs vs firmware image scanning: when do you need both?How Yocto, Buildroot, Zephyr west spdx and FreeRTOS produce an SBOM, how to cover vendor blobs from the shipped image, and why releases need both.Embedded TCP/IP stack vulnerabilities in RTOS firmware: identify, triage, patchHow to tell which TCP/IP stack an RTOS image ships, what Ripple20, AMNESIA:33 and NAME:WRECK showed, where fixes are published and how to patch.ENISA Baseline Security Recommendations for IoT (2017), explainedENISA's November 2017 Baseline Security Recommendations for IoT in the context of Critical Information Infrastructures: its asset taxonomy, threat taxonomy, seven high-level recommendations, and six security gaps — reproduction authorised provided the source is acknowledged.ENISA Good Practices for Security of IoT: Secure Software Development Lifecycle, explainedENISA's November 2019 Good Practices for Security of IoT report: the six-phase secure SDLC, its asset/threat taxonomy, and the 16-domain People/Processes/Technologies good-practice catalogue; reproduction authorised provided the source is acknowledged.ENISA's Multilayer Framework for AI cybersecurity, explainedENISA's June 2023 Multilayer Framework for Good Cybersecurity Practices for AI (FAICP): its three layers, the five ML-specific threats it names, its energy-sector guidance for industrial AI, and why it found national regulators' AI-security readiness low.ENISA Threat Landscape 2025, explainedENISA Threat Landscape 2025 (published October 2025) — methodology behind the 4,875 analysed incidents, the intrusion-vector and sectoral breakdowns, key cybercrime/state-nexus/hacktivism figures, and the top exploited-vulnerability weaknesses.ETSI EN 303 645: the consumer IoT security baseline, explainedETSI EN 303 645's 13 baseline provisions for consumer IoT devices, its version history, how it relates to UK PSTI, and what it does not formally cover.ETSI TR 103 621 (implementation guide to EN 303 645), explainedWhat ETSI TR 103 621 V2.1.1 actually provides: worked examples for every EN 303 645 cyber security and data protection provision, how it relates to TS 103 701 conformance testing, and when a recommendation can legitimately be skipped.ETSI TS 103 701 (conformance assessment for consumer IoT), explainedETSI TS 103 701 V2.1.1 (May 2025) — the companion test methodology for ETSI EN 303 645: the ICS/IXIT pro formas, Device Under Test / Supplier Organization / Test Laboratory roles, conceptual vs. functional test cases, and the PASS/FAIL/INCONCLUSIVE verdict rules.FIPS 140-3: Cryptographic Module Validation (CMVP), explainedNIST's FIPS 140-3 standard, its four security levels, the joint NIST/CCCS CMVP validation program, and the September 2026 move of FIPS 140-2 validations to historical status.NIST FIPS 203, 204, 205: the post-quantum cryptography standards, explainedNIST's three finalized post-quantum cryptography standards — ML-KEM (FIPS 203), ML-DSA (FIPS 204) and SLH-DSA (FIPS 205) — what each specifies, their parameter sets and key/signature sizes, and the 2030/2035 migration deadlines from NIST IR 8547.Firmware binary diffing and patch analysis: finding silently-fixed vulnerabilitiesHow binary diffing finds silently-fixed n-day vulnerabilities between two firmware images, what BinDiff and binwalk do, and where automated analysis stops.Firmware entropy analysis: detecting encryption, compression and packingHow Shannon entropy flags encrypted, compressed or packed firmware regions, how binwalk computes it, and why it matters for binary security review.Secure firmware OTA update design, explainedWhat makes a firmware OTA update secure: signed manifests verified before flashing, anti-rollback checks, and why TLS alone is not transport integrity.C library vulnerabilities in embedded firmware: glibc, uClibc-ng and muslHow to tell which C library and version a firmware image ships, why glibc, uClibc-ng and musl report CVEs differently, and how to triage and fix them.Google's Secure AI Framework (SAIF), explainedGoogle's SAIF: announced 8 June 2023, its six core elements for securing AI systems, the SAIF Risk Assessment self-assessment tool, and its relationship to the Coalition for Secure AI (CoSAI), the OASIS-hosted multi-vendor group Google helped found in 2024.GSMA IoT Security Guidelines (CLP.11/FS.60), explainedGSMA's IoT Security Guidelines document set — the CLP.11 overview (now reissued as FS.60), its Service/Endpoint Ecosystem split, risk-assessment approach, and CLP.12's tiered (Critical/High/Medium/Low) recommendation structure — read directly from the 2017 v2.0 PDFs.GSMA NESAS and 3GPP SCAS, explainedHow GSMA's Network Equipment Security Assurance Scheme (NESAS) and 3GPP's SCAS/SECAM specifications actually work: the two-part vendor-audit-plus-product-evaluation model, the TS 33.117 generic security requirements catalogue, and how NESAS feeds EU and national certification schemes.Hostapd and wpa_supplicant vulnerabilities in embedded firmware: identify, prioritise and fixWhich hostapd and wpa_supplicant CVEs matter for routers, APs and IoT clients (KRACK, Dragonblood, WPS, EAP, 2026), how to find build options and fix them.How to fix authentication bypass in embedded firmwarePractical steps for device and firmware teams to detect, fix, verify and disclose authentication bypass and missing authentication (CWE-287/CWE-306 and related CWEs) in embedded products, sourced to MITRE CWE.How to fix command injection in embedded firmwarePractical steps for device and firmware teams to detect, fix, verify and disclose OS command injection (CWE-77/CWE-78) in embedded products, sourced to MITRE CWE and OWASP.How to fix hard-coded credentials in embedded firmwarePractical steps for device and firmware teams to detect, fix, verify and disclose hard-coded passwords and keys (CWE-798/CWE-259) in embedded products, sourced to MITRE CWE and CISA.How to fix SQL injection, XSS, resource exhaustion and deserialization flaws in embedded firmwarePractical steps for device and firmware teams to detect, fix, verify and disclose SQL injection (CWE-89), cross-site scripting (CWE-79), resource exhaustion (CWE-400) and insecure deserialization (CWE-502) in embedded web UIs and management APIs, sourced to MITRE CWE and OWASP.How to fix memory corruption in embedded firmwarePractical steps for device and firmware teams to detect, fix, verify and disclose memory-corruption bugs (CWE-787/CWE-120 and related out-of-bounds, overflow and use-after-free CWEs) in embedded products, sourced to MITRE CWE and CISA.How to fix path traversal in embedded firmwarePractical steps for device and firmware teams to detect, fix, verify and disclose path traversal (CWE-22 and related CWEs) in embedded web UIs and file-handling code, sourced to MITRE CWE.How to fix weak cryptography in embedded firmwarePractical steps for device and firmware teams to detect, fix and verify broken ciphers, inadequate key strength, hard-coded keys and weak random number generation (CWE-327/326/321/330) in embedded products, sourced to MITRE CWE and CISA.IEEE 802.1AR DevID: what secure device identity means for OT and IoT devicesIEEE 802.1AR-2018 defines the Secure Device Identifier (DevID): a manufacturer-installed IDevID certificate behind BRSKI (RFC 8995), 802.1X and NIST's IoT onboarding guidance. What it is, IDevID vs LDevID, and where it fits OT/IoT hardening.The ioXt Alliance Security Pledge and certification programme, explainedioXt Alliance's 8-principle Security Pledge, its Base/Android/Mobile/Camera/Speaker/Lighting certification profiles, the self-certification vs. Authorized Lab paths — and its April 2026 selection as the FCC's new U.S. Cyber Trust Mark Lead Administrator.IP camera and NVR firmware vulnerabilities: why cameras get exploited, how to identify the SDK and build, and how to patch and hardenWhy IP cameras and NVRs get exploited, how to find the SoC SDK, web server and build in an image, which Hikvision and Dahua CVEs are in KEV, and how to patch.ISO/IEC 27001:2022 (information security management systems), explainedWhat ISO/IEC 27001:2022 actually requires: the Annex SL clause 4-10 structure, Annex A's 93 controls across 4 themes, the relationship to ISO/IEC 27002:2022, the certification cycle, and where it does and doesn't map to CRA/NIS2.ISO/IEC 27005:2022 (information security risk management), explainedWhat ISO/IEC 27005:2022 (4th edition) actually covers: the context/identification/analysis/evaluation/treatment process, its event-based and asset-based approaches, and how it supports (not replaces) ISO/IEC 27001's risk clauses.ISO/IEC 27035 (information security incident management), explainedWhat the ISO/IEC 27035 series actually covers: the five-phase incident management process (plan and prepare, detect and report, assess and decide, respond, learn lessons), how its 2023 revision of Parts 1-2 relates to ISO/IEC 27001/27002 and NIST SP 800-61, and where NIS2 guidance cites it.ISO/IEC 27402 (IoT device baseline requirements), explainedISO/IEC 27402:2023 — the 'horizontal' baseline ICT requirements for IoT devices, its two requirement clauses (policies/documentation and capabilities/operations), its place in the ISO/IEC 27400 family, and how it compares to ETSI EN 303 645 and NIST IR 8259A.ISO/IEC 42001:2023: the AI management system (AIMS) standard, explainedWhat ISO/IEC 42001:2023 actually requires: its Harmonized Structure clauses 4-10, the 38 Annex A controls across nine objectives, AI system impact assessment, how certification works, and where it fits next to the EU AI Act and NIST AI RMF.ISO/SAE 21434 (road vehicles — cybersecurity engineering), explainedISO/SAE 21434:2021's 15-clause structure, the TARA (threat analysis and risk assessment) process, Cybersecurity Assurance Levels (CAL), and how it relates to UN R155's CSMS mandate.JTAG/SWD debug port security for embedded devices, explainedJTAG/SWD debug-port security for embedded devices: why an open on-chip debug interface routinely exposes firmware and keys on real production hardware.libcurl vulnerabilities in embedded firmware: which CVEs matter, how to find them, how to fix themWhich curl CVEs matter for devices, how to find the libcurl version, protocols and TLS backend in a firmware image, and how to prioritise and fix them.libssh and libssh2 vulnerabilities in embedded firmware: find the library, rank the CVEs, patch or backportWhere libssh and libssh2 ship in device firmware, how to find the library and version, which CVEs matter and how to patch or backport them.Embedded web server vulnerabilities in firmware: lighttpd, GoAhead, Boa and uhttpdHow to find which lighttpd, GoAhead, Boa, uhttpd or mini_httpd build a firmware image ships, which CVE classes recur, and how device makers patch them.Linux kernel CVEs in embedded devices: triage by version, config and drivers, then fixWhy the kernel CNA publishes thousands of CVEs a year, how to triage them against a firmware image's kernel version, config and drivers, and how to fix them.LoRaWAN security: what the protocol actually protects in industrial sensor networksLoRaWAN secures the join process and application/network session traffic with AES-128 and a frame-counter replay check — but the LoRa Alliance's own spec leaves key provisioning out of scope, and ABP activation quietly drops the protections OTAA provides. What device makers and buyers need to verify before trusting a LoRaWAN sensor deployment.Manufacturer Usage Description (MUD, RFC 8520), explainedIETF RFC 8520, the Manufacturer Usage Description Specification (March 2019) — how a MUD URL is emitted via DHCP/LLDP/802.1AR certificates, what a MUD file and MUD manager do, and what it means for IoT device and firmware makers.Matter protocol security: what certification actually covers for connected devicesMatter builds PKI-based authentication and encryption into its spec, and the Connectivity Standards Alliance's Product Security program now certifies whole IoT systems, not just devices. What Product Security 1.1 actually requires, and why Matter certification is not the same claim as CRA, PSTI or Cyber Trust Mark compliance.Mbed TLS and wolfSSL vulnerabilities in embedded firmware: identify, triage, patchHow to find the Mbed TLS or wolfSSL version in a firmware or RTOS image, which CVE classes recur, where each project publishes fixes, and how to patch.MCP server security: the core risks, explainedModel Context Protocol (MCP) security — what MCP is, how hosts, clients and servers fit together, and the core attack classes (confused deputy, token passthrough, SSRF, local-server compromise) per the protocol's own security guidance.MiniUPnPd and UPnP vulnerabilities in embedded firmware: find, triage and fixFind MiniUPnPd, libupnp or a vendor UPnP stack in router and IoT firmware, triage SSDP, CallStranger and SOAP overflow CVEs, and keep UPnP off WAN.MITRE ATLAS case studies: real adversarial attacks on AI-powered security productsMITRE ATLAS case studies: adversarial ML attacks that bypassed Cylance, ProofPoint and Kaspersky's AI detection, and lessons for AI security tooling.MITRE ATLAS: the AI adversarial threat matrix, explainedWhat MITRE ATLAS actually is: its 16 tactics and 221 techniques for attacks on AI systems, its origin as the 2020 Adversarial ML Threat Matrix, how it relates to ATT&CK, and why prompt injection and MCP/agent-tool abuse now sit inside it.MITRE ATT&CK for Enterprise: the 15 tactics, explainedMITRE ATT&CK for Enterprise — the 15 tactics in the current v20 matrix, the 2026 split of Defense Evasion into Stealth and Defense Impairment, and how tactics, techniques and sub-techniques fit together.MITRE CAPEC: Common Attack Pattern Enumeration and Classification, explainedWhat CAPEC actually is: a CISA-sponsored, MITRE-maintained catalog of 559 attacker methods (v3.9), how it differs from CWE and ATT&CK, its abstraction levels, and the dedicated ICS attack-pattern view.MITRE D3FEND: the defensive countermeasure knowledge graph, explainedMITRE D3FEND — the NSA-funded, MITRE-managed knowledge graph of cybersecurity countermeasures: what the name stands for, its seven defensive tactics, the Artifact Ontology, and how it complements MITRE ATT&CK.MITRE EMB3D: the embedded device threat model, explainedWhat MITRE's EMB3D framework actually is: its three linked knowledge bases (properties, threats, mitigations), who built it, its version history through v2.0.2, and how it relates to ATT&CK, CWE and CVE.MQTT security: why the spec only says 'should,' and what happens when vendors skip itMQTT 5.0 recommends authentication and TLS but does not require either, leaving broker security entirely up to the implementer. What five 2024-2026 CISA ICS advisories against real MQTT-connected products found when vendors shipped it open anyway.SNMP agent vulnerabilities in embedded firmware: Net-SNMP and vendor agents, found and fixedNet-SNMP and vendor SNMP agents in routers, switches, PLCs and UPS cards: finding the agent and version, CVE classes, SNMPv3 USM/VACM and safe defaults.NIST AI 100-2e2025: the adversarial machine learning taxonomy, explainedNIST's taxonomy and terminology for adversarial machine learning (NIST AI 100-2e2025, published 24 March 2025): how it classifies attacks on predictive AI and generative AI, what changed from the 2023 edition, and why it matters for on-device models and embedded AI assistants.NIST Cybersecurity Framework (CSF) 2.0, explainedNIST CSWP 29's CSF 2.0: the six Functions incl. new GOVERN, the 22 Categories, Tiers and Organizational Profiles, and who the framework is for.NIST IoT device cybersecurity requirements: NISTIR 8259 and SP 800-213NIST's IoT Cybersecurity Program explained: the IoT Cybersecurity Improvement Act of 2020 mandate, NISTIR 8259 series baselines, SP 800-213/800-213A for federal buyers, and the 2026 shift from "devices" to "products".NIST SP 800-115: technical security testing and assessment, explainedNIST SP 800-115, the Technical Guide to Information Security Testing and Assessment: review vs. target identification/analysis vs. target vulnerability validation techniques, the four-phase penetration testing methodology, and overt vs. covert testing.NIST SP 800-121 Rev. 2 (Guide to Bluetooth Security), explainedNIST SP 800-121 Revision 2 (May 2017, updated January 2022) — the BR/EDR and low energy Bluetooth security modes, named threats like bluesnarfing and bluejacking, and the piconet security checklist for devices and firmware.NIST SP 800-128 (security-focused configuration management), explainedNIST SP 800-128 (August 2011, updated October 2019) — the four SecCM phases, the Configuration Item and baseline-configuration concepts, the SP 800-53 CM-family control link, and where SCAP fits into automated configuration monitoring.NIST SP 800-137: Information Security Continuous Monitoring (ISCM), explainedNIST SP 800-137's definition of Information Security Continuous Monitoring (ISCM), the six-step ISCM process, the three organizational tiers, and how ISCM maps to RMF Step 6 Monitor.NIST SP 800-147 (BIOS Protection Guidelines), explainedNIST SP 800-147 (April 2011, Final) — the authenticated BIOS update mechanism, optional secure local update, integrity protection and non-bypassability guidelines, plus the five-phase BIOS management lifecycle and how SP 800-193 later generalized the same model.NIST SP 800-150: cyber threat information sharing, explainedNIST SP 800-150 (October 2016) — the five types of cyber threat information, how to stand up a sharing relationship, the Traffic Light Protocol sharing designations, and who you actually share with (ISACs, ISAOs, CSIRTs).NIST SP 800-160: systems security engineering, explainedNIST SP 800-160's two volumes — Engineering Trustworthy Secure Systems (Vol. 1) and Developing Cyber-Resilient Systems (Vol. 2) — explained: what each covers, how they differ, and how they relate to SP 800-37 and SP 800-53.NIST SP 800-172A Rev. 3 (assessing enhanced security requirements for CUI), explainedNIST SP 800-172A Revision 3 (May 2026) — the "E"-suffixed determination statements, the examine/interview/test methodology shared with SP 800-53A, and how it assesses the 103 active enhanced requirements in SP 800-172 against the advanced persistent threat.NIST SP 800-193 (Platform Firmware Resiliency Guidelines), explainedNIST SP 800-193 (May 2018, Final) — the Protection, Detection and Recovery principles for platform firmware, the Protected/Recoverable/Resilient tiers, Roots of Trust, and the firmware update mechanisms the guidelines are built around.NIST SP 800-207: Zero Trust Architecture, explainedNIST's Zero Trust Architecture standard (SP 800-207, August 2020): the seven tenets, the policy engine/administrator/enforcement-point model, the four deployment approaches, and how CISA's maturity model builds on it.NIST SP 800-207A: zero trust for cloud-native, multi-cloud applicationsNIST's model for applying zero trust access control to cloud-native applications across multi-cloud and hybrid environments — identity-tier vs. network-tier policies, gateways, sidecar proxies, and SPIFFE.NIST SP 800-232: the Ascon lightweight cryptography standard, explainedWhat NIST SP 800-232 (August 2025) actually specifies: the four Ascon algorithms for constrained IoT, embedded and medical-implant devices, why they exist alongside AES-GCM and SHA-3, their security strengths, and the key-handling rules (R1-R7) implementers must follow.NIST SP 800-30: the Guide for Conducting Risk Assessments, explainedNIST SP 800-30 Rev. 1's risk assessment process — the prepare/conduct/communicate/maintain steps, the threat-vulnerability-likelihood-impact risk model, and how it feeds SP 800-39 and the SP 800-37 Risk Management Framework.NIST SP 800-34: Contingency Planning Guide, explainedNIST's Contingency Planning Guide for Federal Information Systems — the seven-step planning process, business impact analysis, alternate-site strategies, and how it differs from incident response.NIST SP 800-37: the Risk Management Framework (RMF), explainedNIST SP 800-37 Rev. 2's Risk Management Framework — the Prepare/Categorize/Select/Implement/Assess/Authorize/Monitor steps, what Revision 2 added in 2018, and how RMF relates to SP 800-53, SP 800-30 and SP 800-39.NIST SP 800-39 (managing information security risk), explainedNIST SP 800-39's three-tier risk management hierarchy (Organization, Mission/Business Process, Information System) and four-component process (Frame, Assess, Respond, Monitor), and how it relates to SP 800-37 and SP 800-30.NIST SP 800-40 Rev. 4: enterprise patch management planning, explainedNIST SP 800-40 Revision 4's enterprise patch management framework: the four risk responses, the patching life cycle, four risk-response scenarios, maintenance groups, and what changed from Rev. 3.NIST SP 800-53: the 20 security and privacy control families, explainedNIST SP 800-53 Rev. 5's control catalogue: the 20 control families, how SP 800-53B's low/moderate/high baselines and tailoring work, and how it relates to FISMA, the RMF and NIST CSF.NIST SP 800-53A Rev. 5 (assessing security and privacy controls), explainedNIST SP 800-53A Revision 5 (January 2022) — the examine/interview/test assessment methods, depth and coverage attributes, the four-step assessment process, and how it ties SP 800-53's controls into the RMF's Assess and Monitor steps.NIST SP 800-57 Part 1 Rev. 5 (key management recommendation), explainedNIST SP 800-57 Part 1 Revision 5 (May 2020) — the 19 cryptographic key types, cryptoperiods, the six key states and four key-management phases, and the security-strength table that says which algorithm/key-size combinations are still adequate.NIST SP 800-61 Rev. 3, explainedNIST SP 800-61 Rev. 3 explained: why the 2012 Computer Security Incident Handling Guide was withdrawn, how the new CSF 2.0 Community Profile reframes incident response, and what changed for incident handlers.NIST SP 800-63-4: Digital Identity Guidelines, explainedNIST's Digital Identity Guidelines (SP 800-63-4, July 2025): the three-volume A/B/C structure, Identity/Authenticator/Federation Assurance Levels, and what changed from the withdrawn SP 800-63-3.NIST SP 800-88 Rev. 2 (media sanitization guidelines), explainedNIST SP 800-88 Revision 2 (September 2025) — the Clear/Purge/Destroy sanitization methods, cryptographic erase, the sanitization-and-disposition decision flow, and what changed from the 2014 edition.NTP and chrony vulnerabilities in embedded firmware: identify the time client, rank the CVEs, harden time syncWhere ntpd, NTPsec, chrony, BusyBox ntpd and SNTP clients ship in devices, which CVEs matter, why wrong time breaks TLS, and how to harden time sync.OpenSSH vulnerabilities in embedded firmware: find the version, rank the CVEs, patch or backportWhere OpenSSH ships in devices, how to find its version and build options, which CVEs matter (regreSSHion, Terrapin, musl bypass) and how to patch.OpenSSL vulnerabilities in embedded firmware: find the version, check backports, fixWhy end-of-life OpenSSL 1.0.2 and 1.1.1 keep shipping in devices, how to find libcrypto's version in firmware, and how backports change CVE matching.OpenVPN, strongSwan and WireGuard vulnerabilities in embedded firmware: identify, prioritise and fixFind which VPN stack and version a router or gateway image ships, which OpenVPN, strongSwan, libreswan and WireGuard CVEs matter, and how to fix them.OWASP's Agentic AI threat model, explained: all 17 threats and their mitigationsOWASP's Agentic AI Threats and Mitigations v1.1 (Dec 2025): all 17 threats to AI agents, a verified real incident, and concrete mitigations.OWASP API Security Top 10 (2023), explainedOWASP's API Security Top 10 2023 edition — all 10 risk categories from Broken Object Level Authorization to Unsafe Consumption of APIs, what changed from the 2019 edition, and how the ranking methodology works.OWASP ASVS: the Application Security Verification Standard, explainedOWASP's Application Security Verification Standard (ASVS) 5.0.0: its three verification levels, roughly 350 requirements across 17 chapters, and how it differs from the OWASP Top 10 and OWASP SAMM.OWASP DSOMM: the DevSecOps Maturity Model's dimensions and levels, explainedOWASP DSOMM scores security practice across 6 dimensions, 24 sub-dimensions and 5 maturity levels — including a new Agentic AI dimension added in 2026 for securing AI coding agents. What the model actually measures, sourced from its own YAML model and GitHub history.OWASP IoT Top 10: the 10 risk categories, explainedOWASP's Internet of Things Top 10 list in full: all ten risk categories, how the 2018 edition was built, and how it relates to ETSI EN 303 645 and the Cyber Resilience Act.OWASP ISVS: the IoT Security Verification Standard, explainedOWASP ISVS v1.0.0-RC2's three verification levels, its five requirement categories spanning ecosystem, application, software-platform, communication and hardware controls, its new post-quantum requirements, and how it complements OWASP's ISTG and FSTM.OWASP Machine Learning Security Top 10, explainedOWASP's Machine Learning Security Top 10 catalogs ten ways a deployed ML model gets attacked — from poisoned training data to a model extracted wholesale through its own prediction API. It is a distinct OWASP project from the LLM Top 10, aimed at the model itself rather than the chat interface around it.OWASP MASTG (Mobile Application Security Testing Guide), explainedOWASP's Mobile Application Security Testing Guide (MASTG) v2.0.0: how it tests the MASVS controls, the MASWE weakness catalog that bridges the two, its modular test/technique/demo structure, and its license.OWASP MASVS (Mobile Application Security Verification Standard), explainedOWASP's Mobile Application Security Verification Standard (MASVS) v2.1.0: the eight MASVS-* control categories, the MAS testing Profiles (L1, L2, R, P), and how MASTG and MASWE fit alongside it.OWASP Top 10 Proactive Controls: the C1-C10 catalog, explainedOWASP's Top 10 Proactive Controls — the C1-C10 catalog of secure-coding practices for developers, how it differs from the OWASP Top 10 vulnerability list, and where ASVS and SAMM fit alongside it.OWASP SAMM: the Software Assurance Maturity Model, explainedOWASP SAMM v2's 5 business functions, 15 security practices, two streams per practice and 3 maturity levels — and how it compares to NIST SSDF.OWASP threat modeling: the four questions and core methodologiesOWASP's threat modeling guidance — the four-question framework from the Threat Modeling Manifesto, the structured steps, and how STRIDE, PASTA, Attack Trees and LINDDUN compare, per OWASP's own community page and Cheat Sheet.OWASP Top 10:2025: the 10 categories, explainedThe official OWASP Top 10:2025 categories, what changed from the 2021 edition, and the data behind the rankings — straight from OWASP's own published methodology and category pages.OWASP Top 10 for LLM Applications, explainedThe OWASP GenAI Security Project's Top 10 risks for large language model applications (2026 edition): the ten items, what changed from 2025, and how it fits alongside OWASP's other Top 10s.PCI DSS v4.0.1: the 12 requirements, explainedWhat PCI DSS v4.0.1 actually requires: the 6 goals, 12 requirements, and the 51 new requirements that became mandatory on 31 March 2025 — plus what changed from v3.2.1.PKfail: the UEFI Secure Boot test-key vulnerability, explainedBinarly's PKfail research (CVE-2024-8105, CERT/CC VU#455367): hundreds of UEFI devices shipped with a leaked AMI test Platform Key, defeating Secure Boot.pppd vulnerabilities in embedded firmware: find the version, rank the EAP bugs, patch or backportWhere pppd ships in routers, LTE modems and gateways, how to find its version and EAP build options, which CVEs matter (CVE-2020-8597) and how to backport.Prompt injection in AI-enabled IoT and embedded devices, explainedA growing share of cameras, robots, voice assistants and industrial sensors now embed an LLM or vision-language model directly. Prompt injection — OWASP's top-ranked LLM risk and a technique in 33 of MITRE ATLAS's 77 case studies — reaches these devices through the camera, microphone and sensor feeds they already trust, not just a chat box.Realtek SDK vulnerabilities in embedded firmware: spot the SDK build, rank the CVEs, ship fixed drops to every modelWhy one Realtek SDK flaw reaches hundreds of OEM routers and cameras, how to spot an SDK build in firmware, which CVEs matter and how to ship fixes.Samba vulnerabilities in embedded firmware: find the version and VFS modules, rank the CVEs, harden smb.confWhere Samba ships in NAS boxes and routers, how to find its version and VFS modules, which CVEs matter (SambaCry, vfs_fruit) and how to harden smb.conf.Secure boot and hardware root of trust, explainedWhat secure boot and a hardware root of trust actually are: how a chain of trust runs from immutable ROM through bootloader to OS/firmware image, where TPMs, secure elements, Arm TrustZone and TCG DICE fit, and how the pieces relate to NIST SP 800-193, SP 800-147 and CRA expectations.Securing AI coding assistants in the firmware SDLCCopilot's code was ~40% vulnerable per IEEE research, and LLMs hallucinate package names attackers register. What firmware teams should do about it.SQLite vulnerabilities in embedded firmware: finding the version, triaging CVEs and hardening the buildWhere SQLite ships in device firmware, how to read its version from a binary, which CVEs need attacker-controlled SQL, and how to harden and patch it.SSVC: Stakeholder-Specific Vulnerability Categorization, explainedCISA and Carnegie Mellon SEI's SSVC decision-tree model for vulnerability prioritization — the decision points, CISA's Track/Track*/Attend/Act outcomes, and how it differs from CVSS scoring.Thread protocol security: what the mesh actually protects, and where commissioning breaksThe Thread Group says Thread uses the same kinds of security technologies that protect banking transactions: a network-wide key, DTLS-protected commissioning and, since 2024, certificate-based TCAT. But a peer-reviewed test of OpenThread-based networks showed the commissioning step itself could be jammed and password-guessed. What device makers and Matter integrators actually need to verify.U-Boot bootloader security for embedded firmware, explainedHow U-Boot's FIT verified boot actually works, how to harden its console and environment variables, and real CVEs (CVE-2018-3968, CVE-2020-10648, CVE-2025-24857) that bypassed it.UL 2900-1 (software cybersecurity for network-connectable products), explainedUL 2900-1 (ANSI/CAN/UL 2900-1, Edition 2, December 2023) — its three requirement areas, what it explicitly excludes, the UL Cybersecurity Assurance Program (UL CAP) built on it, and its August 2017 FDA recognition for medical device premarket submissions.Zigbee security: AES-128 by design, and why the join moment is still where it breaksZigbee encrypts its mesh with AES-128-CCM and has spent a decade hardening how devices join, but the well-known default link key and the network-key handoff at join time remain the documented weak point. What CSA's own Zigbee 4.0 changes, independent research and real CVEs actually found.zlib, Expat and libxml2 vulnerabilities in embedded firmware: finding, triaging and patching themHow to find every zlib, Expat and libxml2 copy and version in a firmware image, which CVE classes matter, where fixes are published, and how to patch.

OWASP Firmware Security Testing Methodology (FSTM), explained