SBC is a terminal-based security diagnostics and remediation dashboard for Windows systems. It is designed to audit, validate, and enforce critical UEFI Secure Boot certificate migrations (Legacy 2011 vs. Modern 2023 Keys) and DBX revocation updates.
- 📊 Real-Time Auditing: Instant identification of global Secure Boot status and legacy restrictions.
- 🛡️ Certificate Scanning: Deep analysis of the
dbandKEKfirmware structures for expiring authorities. - ⚡ Hardware Enforcement: Force DBX revocation updates directly into NVRAM via native CIM/WMI triggers.
- 🎨 ANSI Interface: High-contrast, boxed Unicode terminal design for pristine corporate scannability.
- UNC Safe Pipeline: Maps temporary drives and auto-elevates UAC to run safely from network shares.
- Direct Remediation: Cycle system updates or execute native Microsoft scripts from a single hub.
- Zero Overhead: No heavy frameworks required—runs instantly and completely out of the box.
Important
Encoding Requirement: The script file sbc.ps1 uses advanced Unicode/ANSI box characters. If you modify or save the script manually, it MUST be encoded as UTF-8 with BOM (Byte Order Mark). Saving it as standard UTF-8 or ANSI will break the parser and cause syntax errors (MissingExpressionAfterOperator).
- Clone or download the repository ensuring
start.batandsbc.ps1remain in the same folder. - Ensure File Encoding: Verify that
sbc.ps1is saved with UTF-8 with BOM encoding. - Right-click
start.batand select "Run as Administrator" (required to access live UEFI registers). - Use keys [1-6] for instant tools or navigating back to the main dashboard framework.
SBC utilizes a secure split-architecture to bypass command-line execution and environment limitations:
start.bat(Launcher): Network-safe launcher script (handles UNC paths and forces UAC Admin elevation).sbc.ps1(Engine): The main PowerShell core engine featuring the modern cyber dashboard menu. Requires UTF-8 with BOM encoding to render the UI properly.
Developed by Manuel Pollhammer | Release 2026
