1.

Stronger Integration of Secure Product Development Frameworks (SPDFs)

FDA emphasizes that SPDF processes are a primary mechanism to meet QS regulation requirements and to reduce vulnerabilities throughout the lifecycle. The 2025 version provides expanded recommendations on how SPDFs should tie into design controls, CAPA, and postmarket monitoring.

2.

Expanded Risk Management Requirements

Explicit distinction between safety risk management (ISO 14971) and security risk management (AAMI TIR57, AAMI SW96).

Manufacturers are now expected to provide a Security Risk Management Report in premarket submissions, documenting threat modeling, SBOMs, vulnerability assessments, and residual risk traceability.

3.

Greater Detail on Documentation Expectations

The guidance expands submission documentation tables (including IDE-specific recommendations) to help scale requirements based on device risk. FDA also provides explicit expectations for security architecture diagrams and architecture views.

4.

Reinforced SBOM and Transparency Requirements

FDA places greater emphasis on SBOM completeness and updateability, as well as labeling recommendations to communicate cybersecurity risks to users.

5.

Stronger TPLC and Post-Market Alignment

The 2025 guidance highlights the expectation that cybersecurity is managed throughout the product lifecycle, including coordinated vulnerability disclosure and end-of-life considerations.