IEC 62304 independent review practices and ISO 13485 design review requiring separation between those who design and those who verify.
Documented independence level per test type referencing Table A.1, covering six security test categories — some require external third-party testers depending on device class and test type.
Security test plan documenting tester independence level per all six categories — developers testing their own security implementations is a major finding, especially for penetration testing.
Maps to
IEC 81001-5-1: §5.7.5 Managing conflicts of interest between testers and developers
Requirement text
The manufacturer shall document means of ensuring objectivity of the test effort for: a) attack surface analysis; b) security requirements testing; c) threat mitigation testing; d) vulnerability testing; e) known vulnerability scanning; and f) penetration testing. See Table A.1 for required independence levels.
Why this clause exists
Security testing performed by the team that designed and implemented the security controls is systematically biased: testers who understand the design have tacit knowledge of its assumptions and tend to test those assumptions rather than challenge them. A developer who designed an authentication mechanism knows how it is supposed to work and will test paths that exercise that design; an independent tester without design knowledge will probe edges, attempt unexpected inputs, and challenge assumptions the designer took for granted. This bias is not a character flaw — it is a structural property of how domain knowledge shapes problem-solving. IEC 81001-5-1:2021 clause 5.7.5 requires tester independence from the development team for security testing activities, recognizing that the bias cannot be eliminated through effort alone but only through structural separation. The requirement does not mandate external third-party testing for all activities — independence can be achieved within the organization by separating the security testing function from the security development function — but it prohibits the same individuals or team from both implementing and independently verifying their own security controls.
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 recognized it as Consensus Standard 13-122 (date of entry December 19, 2022). FDA's February 2026 cybersecurity guidance, Section V, lists IEC 81001-5-1 among the "possible frameworks to consider" for secure product development, and FDA's recognition record for the standard notes that conformance "may not satisfy all the cybersecurity requirements outlined in Section 524B of FD&C Act".
EU MDR harmonization was originally targeted for May 2024 but postponed to May 2028.
Common gaps (what we see in audits)
- Developers testing their own security implementations — Security testing including penetration testing is performed by the same engineers who developed the security controls. IEC 81001-5-1 requires independence between testers and developers. Most manufacturers lack a separate internal security testing team.