Vulnerability & Lifecycle Management
Keep your connected products secure as software evolves and new vulnerabilities emerge. We help you track software components, assess relevant risks and act on what matters. By combining vulnerability monitoring with hands-on engineering, we support patch development, secure updates and long-term software maintenance – throughout your product’s operational life.
Keep security moving with your product
Launching a connected product is an important milestone. But from a cybersecurity perspective, it is also the beginning of a new phase.
Products can remain in operation for many years. During that time, new vulnerabilities are discovered, software components evolve and the threat landscape changes. Software considered secure when the product was released may therefore not remain secure forever.
We help companies create a structured approach to vulnerability management and long-term software maintenance. From knowing what is inside the product and monitoring relevant vulnerabilities to assessing their impact, developing mitigations and managing updates.
Because keeping a product secure is not a one-time task. It is a lifecycle responsibility.

Know what is inside your product
You cannot manage what you cannot see. Modern connected products often contain software from many different sources. There may be proprietary code, open-source libraries, operating systems, drivers and third-party components. That creates dependencies.
When a new vulnerability is discovered in one of those components, you need to understand whether it is present in your product – and whether it actually creates a risk.
A Software Bill of Materials (SBOM) provides a structured inventory of the software components included in a product. It creates an important foundation for identifying potentially relevant vulnerabilities and managing software over time.
But having an SBOM is only the beginning. It needs to remain relevant as the product changes, and the information needs to connect to a process for monitoring and handling vulnerabilities.
Visibility creates the starting point. Action creates the value.
A CVE has been found. What happens next?
Common Vulnerabilities and Exposures (CVEs) provide a standardized way of identifying publicly known cybersecurity vulnerabilities. Monitoring CVEs can help identify vulnerabilities associated with software components used in your product. But a match does not automatically mean that your product is vulnerable.
The next step is to understand the context. Is the affected component actually used? Is the vulnerable functionality enabled? Can it be reached or exploited in your product? What could the impact be?
And if action is required, more questions follow.
What mitigation is appropriate? Does a patch need to be developed? How should it be tested? How will the update reach products already in operation? What needs to be documented?
Finding the vulnerability is the signal. Understanding what it means – and acting on it – is the real work.
From detection to resolution
Detect
Monitor software components for newly identified vulnerabilities that may be relevant to the product.
Evaluate
Assess the vulnerability, its severity and whether it can affect the product in its actual configuration and use.
Escalate
Make sure relevant vulnerabilities reach the right people so decisions can be made within the required timeframe.
Resolve
Identify an appropriate response. This may involve mitigation, configuration changes, patch development or a software update.
Report
Support the preparation of relevant technical information and reporting where required.
Document
Keep SBOMs, test results and relevant compliance documentation aligned with changes made to the product.
explore
Cybersecurity Insights
- From cybersecurity requirements to a working medical product – the Ably Medical story
Rune Hillebo Wiinberg & Johan Callmyr

- Cybersecurity doesn’t end when your product leaves R&D
Rune Hillebo Wiinberg & Johan Callmyr

- Connected product? EN 18031 may be more relevant than you think
Rune Hillebo Wiinberg & Johan Callmyr

- Security by design – what does it actually mean for embedded products?
Rune Hillebo Wiinberg & Johan Callmyr

How we can help
CVE monitoring
Know when a new vulnerability may affect your product.
Monitor known vulnerabilities against the software components used in the product and create a structured flow for identifying issues that may require further investigation.
SBOM management
Maintain visibility as your software evolves.
Create and maintain a structured inventory of the software components used in your product. An up-to-date SBOM provides an important foundation for vulnerability monitoring and lifecycle management.
Vulnerability assessment
Separate relevant risks from background noise.
Not every identified CVE will have the same relevance to your product. We can support the engineering evaluation needed to understand whether a vulnerability affects the product and what its potential impact may be.
Mitigation & patch development
Turn identified risks into engineering action.
When action is required, we can help investigate appropriate mitigations and develop software changes or patches.
Update management
Get changes safely into products already in operation.
We can support the planning, implementation, testing and release handling needed to update embedded software and Linux platforms over time.
For machinery and safety-related systems, updates also need to be assessed for their impact on safe operation. We can connect cybersecurity changes with machinery safety expertise to help determine what needs to be verified and which risk assessments and technical documentation need updating.
Documentation
Keep the technical picture up to date.
Changes to a product can also require updates to SBOMs, test reports and relevant compliance documentation. We can support that documentation as part of the vulnerability handling process.
Long-term software maintenance
Plan for years, not only the next release.
Products often remain in operation far longer than individual software versions. A structured maintenance approach helps create continuity around software updates, vulnerability handling and platform evolution.
From vulnerability data to decisions
As the number of software components grows, manually keeping track of newly discovered vulnerabilities can become difficult.
Prevas Cyber Security Intelligence (PCSI) provides automated CVE monitoring based on a product's SBOM. The existing service offering describes daily automated CVE reporting, creating a structured way to identify newly reported vulnerabilities that may be relevant to a product.
But monitoring alone does not resolve the issue.
PCSI can be combined with engineering support for vulnerability evaluation, mitigation and software maintenance. This helps connect automated monitoring with the people and engineering capabilities needed to decide what to do next.
Less time searching for vulnerabilities. More focus on understanding and addressing the ones that matter.
Vulnerability management and the Cyber Resilience Act
The Cyber Resilience Act brings additional attention to how vulnerabilities in products with digital elements are handled throughout the product lifecycle.
For product companies, this increases the importance of having structured processes for identifying, evaluating, resolving and documenting vulnerabilities.
We can support technical and engineering activities across that process – including CVE monitoring, engineering evaluation, mitigation and patch development, and documentation.
Responsibilities still need to be clear. In the vulnerability handling model described in our current offering, the Product Owner remains responsible for approving and submitting required reports, while Prevas can support the underlying engineering and preparation.
Design today for maintenance tomorrow
Good lifecycle management actually starts before the product reaches the market.
Can the software be updated securely? Do you know which components are included? Is there a clear chain of trust? Can software changes be verified before deployment? Are responsibilities for maintenance clear?
Decisions made during product development can make vulnerability management easier – or much harder – years later.
That is why secure development and lifecycle management belong together.
Build for security today. Prepare for change tomorrow.
EXPLORE
Curious about our projects?
Long product life. Long security responsibility.
Long product lifecycles create a particular challenge for connected products.
The product may still work perfectly from a functional perspective while the software environment around it has changed significantly. Components may become outdated. New vulnerabilities may be discovered. Dependencies may no longer be maintained. New cybersecurity requirements may emerge.
Waiting until something happens can make these issues harder and more expensive to address.
A planned approach to software maintenance and vulnerability management helps create greater predictability – for development teams, product owners and customers.
The product may be built. The responsibility continues.
More than vulnerability monitoring
We can help do something about what we find. Monitoring systems can identify potential problems. They cannot redesign an architecture, develop a patch or test an updated product.
People and engineering expertise still matter. Our cybersecurity specialists can work alongside embedded software developers, Linux specialists and product experts to help evaluate vulnerabilities and turn decisions into technical action.
That connection between monitoring and engineering is an important part of our approach. Because knowing about a vulnerability is useful. Knowing what to do next is better.
Expertise that connects
Keeping products secure takes more than one capability. Depending on your product and challenge, vulnerability management can connect with expertise across Prevas.
Security doesn’t stop at launch. It evolves with your product.
Rune Hillebo Wiinberg, Head of Cyber Security

