IEC 62304 coding guidelines and software development standards already referenced in the software development plan.
Language-specific secure coding standard (OWASP, CERT, or equivalent), maintenance cadence with annual review, and version history demonstrating ongoing currency.
Dated, technology-specific secure coding standard with review history — generic or undated standards without language-specific rules do not satisfy Annex A.4.
Maps to
IEC 81001-5-1: §5.1.3 Secure coding standards
Requirement text
The manufacturer shall establish and maintain secure coding standards consistent with current best practices related to the design and implementation of secure software systems. See Annex A.4.
Why this clause exists
Secure coding standards that exist only as a reference document in a shared drive provide no assurance about the code that actually ships. Without a formal adoption process that includes developer training, tooling configuration to enforce measurable rules, and an integration into code review, the standard may as well not exist — developers default to familiar patterns, and reviewers lack objective criteria for identifying violations. IEC 81001-5-1:2021 clause 5.1.3 requires that secure coding standards be planned and established as a formal activity, not merely documented as a reference. The planning requirement means the standard must be adopted in advance of development, not appended at code review. FDA inspection observations related to cybersecurity frequently include findings that organizations have a secure coding standard document but no evidence it was applied to the product under review — no training records, no tool configuration, no review checklists. The standard's connection to implementation review in clause 5.5 creates a closed loop: the standards established in planning must be verifiable in implementation.
What changed
IEC 81001-5-1:2021 is the first standalone cybersecurity standard purpose-built for health software and medical device software. Published in December 2021, it was adapted from IEC 62443-4-1 (industrial control systems security) to address the unique safety and regulatory context of medical devices — adding health-specific requirements that account for patient safety, clinical workflows, and the manufacturer-HDO relationship.
The standard mirrors IEC 62304's lifecycle structure but adds security-specific activities at every phase — planning, development, testing, release, and maintenance. It requires security risk management to be integrated with ISO 14971 safety risk management, not treated as a separate IT concern. FDA formally recognized it as Consensus Standard 13-122 on December 19, 2022 and references it as providing one acceptable framework for satisfying the cybersecurity requirements of Section 524B(b)(2), which requires manufacturers to design, develop, and maintain processes and procedures to provide a reasonable assurance that cyber devices and related systems are cybersecure.
EU MDR harmonization was originally targeted for May 2024 but postponed to May 2028. Despite this delay, Notified Bodies and Competent Authorities universally recognize it as "state of the art" for health software cybersecurity under MDR GSPR Annex I, Section 17.2. Missing or inadequate cybersecurity documentation is already a top cause of Notified Body major non-conformities for SaMD. A December 2025 Interpretation Sheet (ISH1:2025) clarified software item classification into maintained, supported, and required software categories, affecting risk transfer and post-market obligations.
Common gaps (what we see in audits)
- Secure coding standards generic or absent — Manufacturers reference generic coding standards (MISRA, CERT) without tailoring them to the specific technology stack, threat model, and security requirements of their medical device software.