AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Security Updates

skill-beriberikix-zephyr-agent-skills-security-updates · by beriberikix

Secure boot and firmware update workflows for Zephyr RTOS. Covers MCUboot integration, production image signing, DFU protocols (MCUmgr), fail-safe rollback mechanisms, and mbedTLS crypto basics. Trigger when implementing over-the-air (OTA) updates, securing the boot process, or managing cryptographic keys.

No reviews yet
0 installs
36 views
0.0% view→install

Install

$ agentstack add skill-beriberikix-zephyr-agent-skills-security-updates

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-beriberikix-zephyr-agent-skills-security-updates)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Security Updates? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Zephyr Security & Updates

Build production-ready, secure embedded systems using Zephyr's modular security stack and MCUboot bootloader.

Core Workflows

1. MCUboot Integration

Set up the secure bootloader and define fail-safe flash partitions.

  • Reference: [mcubootintegration.md](references/mcubootintegration.md)
  • Key Tools: CONFIG_BOOTLOADER_MCUBOOT, fixed-partitions, Devicetree.

2. Image Signing

Ensure firmware integrity with production-grade digital signatures.

  • Reference: [imagesigning.md](references/imagesigning.md)
  • Key Tools: imgtool.py, ECDSA-P256, RSA.

3. DFU Protocols

Transport updates securely using MCUmgr or cloud-based OTA.

  • Reference: [dfuprotocols.md](references/dfuprotocols.md)
  • Key Tools: mcumgr, Golioth OTA, SMP transport.

4. Rollback Protection

Implement atomic swaps and image confirmation to prevent bricking devices.

  • Reference: [rollbackprotection.md](references/rollbackprotection.md)
  • Key Tools: boot_write_img_confirmed(), mcumgr image test.

5. Crypto Basics

Implement secure storage and cryptographic operations using mbedTLS.

  • Reference: [cryptobasics.md](references/cryptobasics.md)
  • Key Tools: CONFIG_MBEDTLS, TF-M, secure storage.

Quick Start (Kconfig for Secure Boot)

# Enable MCUboot support in application
CONFIG_BOOTLOADER_MCUBOOT=y
# Build with MCUboot using Sysbuild
west build -b nucleo_f401re --sysbuild samples/basic/blinky

Professional Patterns (Security-First)

  • Production Keys: Never use default MCUboot keys. Provision unique keys during manufacturing.
  • Heartbeat Confirmation: Only confirm a new image after the application has successfully connected to its cloud backend.
  • Version Integrity: Enable version monotonicity to prevent accidental or malicious firmware downgrades.

Automation Tools

  • [mcubootversionguard.py](scripts/mcubootversionguard.py): Enforce monotonic semantic version progression in update pipelines.

Examples & Templates

  • [mcubootprjfragment.conf](assets/mcubootprjfragment.conf): Starter secure-boot + image-management config fragment.

Validation Checklist

  • [ ] Signed image verifies at boot and unsigned/tampered image is rejected.
  • [ ] DFU flow completes end-to-end and boots into the new slot.
  • [ ] Rollback behavior triggers correctly when image confirmation is withheld.
  • [ ] Key handling and version policy prevent downgrade and test-key usage in production configs.

Resources

  • [References](references/):
  • mcuboot_integration.md: Partition layouts and setup.
  • image_signing.md: Key management and imgtool usage.
  • dfu_protocols.md: MCUmgr commands and cloud OTA.
  • rollback_protection.md: Swap mechanisms and confirmation code.
  • crypto_basics.md: mbedTLS and secure storage.
  • [Scripts](scripts/):
  • mcuboot_version_guard.py: Version monotonicity checker for release gates.
  • [Assets](assets/):
  • mcuboot_prj_fragment.conf: Secure-update config baseline.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.