Theatre

Containerized, cloud-enabled, and compliant: embedded DevSecOps at scale

Watch Now

33:16

EOC 2025

Login to Watch

Aaron Bauch

Aaron Bauch is a Senior Field Application Engineer at IAR Systems working with customers in the Eastern United States and Canada. Aaron has worked with embedded systems and software for companies including Intel, Analog Devices and Digital Equipment Corporation. His designs cover a broad range of applications including medical instrumentation, navigation and banking systems. Aaron has also taught a number of college level courses including Embedded System Design as a professor at Southern NH University. Mr. Bauch Holds a Bachelor’s degree in Electrical Engineering from The Cooper Union and a Masters in Electrical Engineering from Columbia University, both in New York, NY.

View full profile

IAR

Empowering your projects with the platform for modern software development teams — without vendor lock-in, with the assurance of industry-leading security and compliance, and the power to optimize every line of code for maximum efficiency.

Website LinkedIn

Session Slides

Download Slides (PDF)

Theatre

Containerized, cloud-enabled, and compliant: embedded DevSecOps at scale

Aaron Bauch

33:16 EOC 2025

Aaron Bauch

33:16

As embedded systems evolve and development scales across teams and geographies, maintaining quality, security, and compliance becomes a serious challenge. Manual workflows and fragmented toolchains no longer meet the demands of modern product development, especially when time-to-market and regulatory readiness are critical.

In this session, we’ll explore how engineering teams are implementing DevSecOps best practices to automate embedded CI/CD pipelines, reduce risk, and deliver secure, high-quality software, whether deploying in cloud, hybrid, or on-prem environments.

You’ll learn how containerized, cloud-enabled workflows help:

Support compliance with standards like ISO 26262, IEC 61508, and IEC 62304 using TÜV-certified tools
Integrate secure boot, encryption, and IP protection directly into development pipelines
Adopt architecture-agnostic toolchains across Arm, RISC-V, and more, minimizing vendor lock-in
Enable CI/CD automation using familiar tools like GitHub, GitLab, Kubernetes, and containers

Whether you're building safety-critical devices or scaling across multiple product lines, this session offers real-world strategies that embedded software teams are using today to modernize, secure, and accelerate development across any deployment model.

1 / 4

Please log in or create an account to test your knowledge and see the answers.

According to the talk, what is the primary benefit of using containerized builds (Docker images) for embedded CI/CD pipelines?

A They let each developer run a different toolchain so teams can optimize per-person workflows.

B They provide lightweight, repeatable environments that ensure reproducible builds and eliminate “works on my machine” failures.

C They replace the need for hardware-in-the-loop testing because containers can fully simulate embedded hardware.

D They are primarily useful because they run a full guest OS per job, like a virtual machine, improving isolation.

E They guarantee better security than any other deployment method by default.

Why did the speaker recommend using self-hosted or a cloud-hybrid runner approach for embedded CI/CD?

A Because self-hosted runners are always cheaper than shared cloud runners for every organization.

B Because hybrid/self-hosted runners give control needed for safety-critical, regulated, or hardware-dependent steps and let teams run hardware-in-the-loop or air-gapped jobs on-premises.

C Because using self-hosted runners removes the need to containerize environments.

D Because shared cloud runners cannot run any static analysis or license checks.

E Because a hybrid model forces all teams to centralize all hardware and remove local development machines.

What approach did Aaron Bauch recommend to simplify and accelerate functional safety certification (ISO 26262, IEC 61508, IEC 62304)?

A Rely on large manual audit teams and spreadsheets to demonstrate traceability after release.

B Use TÜV‑certified toolchains integrated into CI/CD so builds are reproducible, auditable, and produce certification-ready artifacts.

C Avoid using certified tools and instead run as many unit tests as possible to prove safety.

D Delay any safety validation until after product launch to speed time-to-market.

E Switch to a single-vendor proprietary toolchain per architecture to minimize certification scope.

What is the main advantage of adopting a DevSecOps (shift-left) approach in embedded development, as described in the webinar?

A It only speeds up build times by adding more parallel compile jobs.

B It pushes security and safety activities earlier in development so defects and dangerous patterns are caught sooner, reducing costly downstream rework and improving traceability.

C It requires hiring a full DevOps team before any improvements can be made.

D It means security can be ignored during development and only added by a specialist at the end.

E It eliminates the need for coding standards and static analysis because automation will catch everything later.

Formatting help

italics	surround text with asterisks
bold	surround text with two asterisks
hyperlink	[hyperlink](https://example.com) or just a bare URL
inline code	surround text with single `backticks`
code block (multi-line)	wrap on its own lines with three backticks: ``` your code here ```
~~strikethrough~~	surround text with ~~two tilde characters~~
quote	prefix with >

Upvotes Newest Oldest

SuziOrourke

Score: 0 | 11 months ago | no reply

This post has been deleted by the author

AaronBSpeaker

Score: 0 | 11 months ago | no reply

Thanks!

datamstr

Score: 0 | 11 months ago | no reply

Excellent presentation, Aaron!

Partners & Sponsors

CodeSecure

atym

embedd.it

IAR

Become a Sponsor