<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Securing BIOS Passwords on Jon's Notes</title><link>https://www.configjon.com/series/securing-bios/</link><description>Recent content in Securing BIOS Passwords on Jon's Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 24 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.configjon.com/series/securing-bios/index.xml" rel="self" type="application/rss+xml"/><item><title>Securing BIOS Passwords in Unattended Deployments</title><link>https://www.configjon.com/securing-bios-passwords/</link><pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate><guid>https://www.configjon.com/securing-bios-passwords/</guid><description>&lt;p&gt;My Dell, HP, and Lenovo BIOS password and settings scripts all accept the BIOS password as a plain-text parameter. This keeps the scripts simple and broadly compatible, but it means that &lt;strong&gt;how you deliver the password to the script&lt;/strong&gt; is also how you secure the password. This post covers how to do that safely under Configuration Manager and task sequences, and how the built-in CMS support added in version 2.3.0 makes it easier.&lt;/p&gt;</description></item><item><title>Document Encryption Certificates for BIOS Password Management</title><link>https://www.configjon.com/bios-password-encryption-certificate/</link><pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate><guid>https://www.configjon.com/bios-password-encryption-certificate/</guid><description>&lt;p&gt;The CMS method described in &lt;strong&gt;&lt;a href="https://www.configjon.com/securing-bios-passwords/"&gt;Securing BIOS Passwords&lt;/a&gt;&lt;/strong&gt; relies on a document encryption certificate. The BIOS password is encrypted to that certificate&amp;rsquo;s public key, and only devices holding the matching private key can decrypt it. This post is a companion to that one. It covers how to create and manage the certificate itself: choosing between a self-signed certificate and one issued from an enterprise PKI, and handling the full lifecycle from creation through distribution, rotation, and removal.&lt;/p&gt;</description></item></channel></rss>