The Role of OSPO Manager for the Organization’s Success
summary
OSPO work at Siemens focuses on concrete practices not rhetoric: a 14 year program grows into 60+ experts and achieves 99% coverage by embedding OSS checks into milestones, maintaining an internal catalog and SCA pipelines, and contributing to Fossology and SW360. Deliverables include mandated SBoMs in simplified CycloneDX 1.6 format, file‑level clearing reports, code‑snippet matching against public sources and GitHub Copilot output, and an early risk indication tool tied to NVD vulnerability data.
AI-written summary · about
chapters (15)
- 0:00OSPO introduction
- 1:07OSPO manager role
- 3:59Daily OSPO challenges
- 6:27Open source compliance risks
- 8:55Software Bill of Materials and regulations
- 12:09OSPO manager responsibilities
- 17:27Legal and security collaboration
- 18:41AI code compliance
- 22:13Project roles in OSPO
- 23:59OSPO journey and policies
- 26:26OSPO success drivers
- 27:53Compliance in milestones
- 28:57OSPO tools and metrics
- 30:02Scans and audits timing
- 33:05Q&A
related talks
46mOSS Management & OSPO Ask Anything
26mLooking at Open Source Security from the Community Angle
37mYour OSPO’s Role in Ensuring Long-Term Business Viability
47mFive Key Requirements for a Successful OSPO
40mTODO Steering Committee - Management & OSPO Ask Anything
30mDemystifying OSPOs
30mApproaching OSPO: Steward or Damper?
26mNavigating Open Source: Establishing an OSPO for Organizational Success