# Mitigating Cyber Risk with Secure by Design

Page: https://stenobird.com/podcast/software-engineering-institute-sei-podcast-series-389154/mitigating-cyber-risk-with-secure-by-design
Text version: https://stenobird.com/podcast/software-engineering-institute-sei-podcast-series-389154/mitigating-cyber-risk-with-secure-by-design.md
Podcast: [Software Engineering Institute (SEI) Podcast Series](https://stenobird.com/podcast/software-engineering-institute-sei-podcast-series-389154)
Published: 2025-07-14T16:56:00+00:00
Episode link: https://cmu-sei-podcasts.libsyn.com/mitigating-cyber-risk-with-secure-by-design
Audio file: https://traffic.libsyn.com/clean/secure/cmu-sei-podcasts/Touhill_SecurebyDesign.mp3?dest-id=762491
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/software-engineering-institute-sei-podcast-series-389154/episodes/mitigating-cyber-risk-with-secure-by-design
Duration seconds: 1949

## Resource

Software enables our way of life, but market forces have sidelined security concerns leaving systems vulnerable to attack. Fixing this problem will require the software industry to develop an initial standard for creating software that is secure by design. These are the findings of a recently released paper coauthored by Greg Touhill, director of the Software Engineering Institute (SEI) CERT Division. In this latest SEI podcast, Touhill and Matthew Butkovic, director of Cyber Risk and Resilience at CERT, discuss the paper including its recommendations for making software secure by design.

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/software-engineering-institute-sei-podcast-series-389154/episodes/mitigating-cyber-risk-with-secure-by-design/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/software-engineering-institute-sei-podcast-series-389154/mitigating-cyber-risk-with-secure-by-design.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.