Manage Product Versions
When your product evolves—adding a new module, updating firmware, or releasing a hardware revision—you don't need to start from scratch. Product Security Hub lets you create new versions that clone everything from an existing product, so you only need to document the changes.
Before You Begin
- You have an existing product in Product Security Hub that you want to create a new version of
- The source product has the components, threats, requirements, and risks you want to carry forward
🔑 Key Concept: Why Create Product Versions?
Medical devices and connected products rarely stay static. You might release Version 2 that adds a Bluetooth module, or Version 1.1 that updates the firmware. Instead of recreating all your security documentation from scratch, Product Security Hub lets you:
- • Clone everything from an existing product version
- • Make targeted updates for only what changed
- • Manage versions independently once both are commercialized
Example: Your product Version 1 is on the market. Version 2 adds a Bluetooth module. Create a new version from Version 1—all your components, threats, requirements, and risks are copied over. Then just add the Bluetooth component and document its specific threats. You've saved hours of work.
What Gets Cloned
When you create a new version from an existing product, Product Security Hub copies all of the following:
Product Details
Name, description, settings
Architecture Diagrams
All diagram content
Components
All product components
Threats
Threat model with scores
Requirements
All requirements & responses
SBOMs
SBOM containers & components
Residual Risks
All documented risks
Vulnerabilities
All vulnerability records
Patches
Patch management records
💡 Independent After Creation: Once you create a new version, it becomes completely independent. Changes you make to Version 2 do not affect Version 1, and vice versa. This is essential for managing multiple commercialized products.
Two Ways to Create a New Version
Product Security Hub provides two methods to create a new product version:
From the Product Dashboard
The quickest way to create a new version when you're already viewing a product.
Navigate to Your Product
From the ProdSecDesigner Dashboard, find and click on the product you want to create a new version of.
Click the Version Button
In the product header area, look for the Ver button (next to the version number). Click it to open the version creation options.
Enter the New Version Number
Specify the version number for your new product (e.g., "2.0", "1.1", "Rev B").
Confirm and Create
Product Security Hub clones everything from the current product and creates your new version. You'll be taken to the new product version.
From the Add New Product Modal
Use this method when you're on the main dashboard and want to create a version of any existing product.
Open "Add New Product"
From the ProdSecDesigner Dashboard, click the Add New Product button to open the modal.
Check "Create a new product version"
In the PRODUCT DETAILS section, check the box next to Create a new product version. A dropdown will appear below.
Select the Source Product
Click the dropdown and select the product you want to create a new version of. The list shows all your products with their current version numbers.
Complete the Product Details
Enter the new version number and any other details. You can also modify the product name if needed.
Save to Create
Click Save to create the new version. Product Security Hub clones everything from the source product.
💡 Import Options Still Available
The Add New Product modal also shows Import From a File, Download Blank Template, and Download Pre-Populated Template buttons at the top. These are for creating products from Excel imports, separate from the version creation feature.
After Creating a New Version
Once your new version is created, you'll typically need to:
Add New Components
If your new version adds hardware or software components (like a Bluetooth module), add them on the Components page.
Update the Architecture Diagram
Add the new components to your diagram and update data flows as needed.
Run Threat Modeling
Generate threats for the new components. The existing threats from the cloned product are already in place.
Update SBOMs
Import updated SBOMs for new or changed software components and run vulnerability scans.
Review Requirements
Check if new components affect how you meet any requirements. Update the "How Will This Be Met" responses as needed.
Managing Multiple Commercialized Versions
Once both versions are on the market, you'll manage them independently. Here's how this typically works:
Independent Vulnerability Management
Each version has its own SBOM and vulnerability records. A vulnerability in Version 1's component doesn't automatically appear in Version 2 (and vice versa).
Separate Patch Tracking
Track patches independently. Version 1 might need different patches than Version 2, especially if they have different software components.
Version-Specific Requirements
If requirements change between versions (e.g., new regulations), you can update each version's requirements independently.
Dashboard Overview
View all product versions from the ProdSecDesigner Dashboard. Each version appears as a separate line item with its own maturity metrics.
Best Practices
Use consistent version numbering
Establish a naming convention (1.0, 2.0, etc. or Rev A, Rev B) and use it consistently across all your products.
Document what changed
Update the product description to note key differences from the previous version. This helps team members understand the scope of changes.
Create versions early
Create the new version as soon as development starts, not when you're ready to ship. This ensures security is tracked throughout development.
Review cloned content
After cloning, review the copied content to ensure it still applies. Remove any threats or components that are no longer relevant.
What's Next?
After creating your new product version:
- 1 Add New Components
Add any new components that differentiate this version
- 2 Update Architecture Diagram
Add new components to your diagram and update data flows
- 3 Run Threat Model
Generate and assess threats for the new components
Managing a complex product portfolio?
We can help you establish efficient workflows for managing multiple product versions and variants.