PHYTEC’s phyHUB connects the software inventory to the devices still running it
Illustrative image: Harrison Broadbent on Unsplash
PHYTEC’s new phyHUB service connects software component monitoring with the devices running that software. The hosted platform combines lifecycle services and security updates with ML!PA’s L-IoT platform, including automated matching of disclosed vulnerabilities against device software bills of materials.
PHYTEC says it can manage electronics from other manufacturers as well as its own boards. Its fleet functions cover asset records, device health, software versions and over the air updates.
An SBOM match starts the maintenance work. The component version and build configuration help establish whether the affected code is present, while the way it is used determines whether the vulnerability can be reached. Treating every name match as an exploitable fault would fill the work queue without establishing which devices need urgent attention.
The deployed version is another part of the investigation. A corrected build may exist in the development system while older devices continue to run the affected release. Joining the inventory to fleet records can expose that gap, provided the device records reflect what is actually installed.
Following the fix into the fleet
An update package has to reach a compatible device and install successfully. Different board revisions, bootloaders and application configurations can require different images, so a record that an update was offered cannot confirm that the whole fleet has moved to it.
Version management and device health can help track the build through installation and the subsequent boot. They also identify units that remain on an older version, allowing the outstanding work to be tied to particular devices rather than an undifferentiated fleet total. Completing that chain depends on how the service is integrated and operated.
Alongside phyHUB, PHYTEC is presenting secure provisioning and BSP maintenance services, with the phyFLEX module family now spanning nine processor platforms. Managing director and CTO Bodo Huber says: “Secure availability, product maintenance, and software are becoming increasingly important for our customers.”
A module substitution can make the software history more complicated even when pin compatibility preserves the carrier board. Peripherals or the BSP may change, producing a different update image for a product that performs the same application functions. The fix needed on the original module may then differ from the build for its replacement. Keeping those relationships in the version record avoids treating every unit carrying the same product name as the same update target.
