Please note the below is a combination of AI generated and my own notes. Please find the slides I showed attached.
Regards
Dan.
Meeting summary
Quick recap
The meeting focused on several key topics related to Trusted Firmware and security initiatives. Dan provided updates on the PSA specification governance, emphasizing the goal to maintain long term momentum with wider participation. The discussion then shifted to the TF bug bounty program, which has seen a significant increase in submissions, leading to concerns about maintainability and the use of AI tools in submissions. Dan highlighted the challenges faced in managing the volume of reports and the need for more CVEs, which has been delayed due to responsiveness issues with Mitre. The group also discussed the launch of Core Collective, a new collaboration platform backed by Arm and Linaro, and its potential role in supporting various projects, including Trusted Firmware. David raised questions about the organization of working groups within Core Collective and its potential impact on existing project structures.
Next steps
* Dan: Send meeting slides to attendees after the meeting.https://tasks.zoom.us/?meetingId=WM9WhRFeRT2Qu%2BUdFs2eyA%3D%3D&stepId=2ebdaaf0-23bc-11f1-a3a3-6a6c0d273f77 * Dan: Pass on feedback and concerns about the bug bounty program to the Arm PSIRT team.https://tasks.zoom.us/?meetingId=WM9WhRFeRT2Qu%2BUdFs2eyA%3D%3D&stepId=2ebdb705-23bc-11f1-b4c4-6a6c0d273f77 * David and Dan: Discuss offline the possibility of using AI/automated tools for internal bug triage and analysis, and potentially test such tools.https://tasks.zoom.us/?meetingId=WM9WhRFeRT2Qu%2BUdFs2eyA%3D%3D&stepId=2ebdbada-23bc-11f1-913e-6a6c0d273f77 * David: Set up a call with Grant to discuss Zephyr backporting/LTS funding and Core Collective project structure.https://tasks.zoom.us/?meetingId=WM9WhRFeRT2Qu%2BUdFs2eyA%3D%3D&stepId=2ebdbdc9-23bc-11f1-99fa-6a6c0d273f77 * Dan: Lead or co-lead the confidential compute working group in Core Collective and organize a discussion in the next month to define scope and membership.https://tasks.zoom.us/?meetingId=WM9WhRFeRT2Qu%2BUdFs2eyA%3D%3D&stepId=2ebdc03a-23bc-11f1-9309-6a6c0d273f77
Summary Present Ben Vogel (QTI) Eric Finco (ST) David Brown (Linaro) KangKang (FutureWei) Michael Thomas (Renesas) Julius Werner (Google) Kamlesh Gurudasani (TI) Andrew Davis (TI) Dominik Ermel (Nordic) Joanna Farley (Arm) Dan Handley (Arm)
Zephyr Long Term Support (LTS) David explained how Zephyr is trying to change its LTS frequency from 5 years to 3. To date Zephyr has been pulling main branches from TF projects, which isn't great. Now plan to pull in TF LTS branches and if they go out of date for Zephyr, we can discuss how to address it in a public forum, maybe at CoreCollective. There was some discussion on there being a Zephyr Working Group (WG) at CoreCollective, but Zephyr has wider scope than just Arm architecture platforms. There is an Edge WG, which includes part of Zephyr in its scope. Joanna mentioned how TrustedFirmware-A related projects are released together, which helps to managed dependencies. David countered that this is harder across project ecosystems with different governance - one has to go first. Michael also mentioned difficulties managing versions in their product because some dependencies are using older versions of TF projects; they have to fix the dependencies themselves.
PSA Specification governance moving to Global Platform (GP)
The group discussed changes to the PSA specification governance, with David agreeing that making the specification more broadly applicable beyond ARM was a good idea, particularly given its use in Mbed TLS and other areas. Dan confirmed that the copyright and licensing would remain unchanged, and Andrew Thoelke would continue to manage the PSA APIs as working group lead. The discussion addressed concerns about implementation in TF, which would not change, and David suggested that PKCS11 could potentially be replaced in the future.
The team discussed the progress and potential for moving PSA API and FF-M specs to GP, though the timeline remains unclear.
TF Bug Bounty Program
Dan shared updates on the TF bug bounty program, which launched in December and has seen a higher volume of reports than anticipated, leading to changes in the program's rules to prevent automatic suspension due to budget constraints. Despite these challenges, the program continues to receive submissions, with 103 reports in March alone, raising concerns about the sustainability of the workload for maintainers.
The team discussed security vulnerability handling across different projects, with Dan noting that Mbed TLS and OP-TEE are experienced in managing high volumes of security issues, while TF-A has been more challenging due to lower volume historically. Dan mentioned that Hafnium is not yet live in the program but it probably should be added soon. Kamlesh inquired about TF-A bug types, clarifying that while platform-specific issues are out of scope, some may still be considered if reproducible in a platform context. The team also discussed the increasing use of AI tools in bug submissions, with Dan estimating over 90% of submissions now using such tools, and Kamlesh raised questions about bug bounty program payouts and effectiveness. David suggested using AI tools to analyze and triage bug reports, which could be a potential approach given the high volume of submissions. Eric asked whether the 10% rate of valid reports is the same across projects. Dan said we don't have that data but we expect so.
The team discussed challenges with AI-generated bug reports, noting that while some reports contain valid vulnerabilities, others are of low quality or incorrect. David and Dan agreed to discuss the issue offline, as they are two of the people managing the tools. Ben shared that the curl maintainer had to cancel their bug bounty program due to overwhelming low-quality submissions. The team considered implementing an invitation-only bug bounty program with a limited number of high-bounty issues to reduce AI submissions. Dan mentioned that the Intigrity and Arm PSIRT are currently filtering out most AI-generated reports, with only a few requiring deeper inspection.
CVE Allocation Challenges
The group discussed the delay in receiving CVEs from Mitre, which is taking over a month for allocation, making the process increasingly cumbersome. David and Dan discussed the admin challenges of the security teams generating CVEs themselves, highlighting the need to justify the training time and costs for already-stretched teams. They considered options such as using the existing TF budget surplus to cover training for someone to handle the task, though this could risk affecting other work.
Core Collective
Dan mentioned that Core Collective, launched by Linaro with backing from Arm, is a new collaboration platform that is free to join and has a governance structure similar to Trusted Firmware, but it is not intended to replace it. Dan clarified that the confidential compute working group is still in the planning stages, with Dan set to lead discussions on its scope and membership in the coming month.