- Home
- Skills
- Legal & Compliance
- Registry Policy Auditor
Works with the AI Agents you already use
Registry Policy Auditor
Audit Windows registry exports against CIS-style security baselines with automated parsing and compliance reporting.
$2.99
Registry Policy Auditor
Example session with this skill installed
Audit my registry export 'host_audit.reg' against the CIS-level starter baseline. Provide a summary of failures and a compliance score.
- Read your context and instructions
- Compiled the registry policy auditor
I have completed the audit of host_audit.reg against the starter.yaml security baseline. The audit scanned 42 security-critical keys across networking, authentication, and system logging categories.
Registry Audit Results Summary
| Metric | Value |
|---|---|
| Total Keys Checked | 42 |
| Passed (Correct) | 38 |
| Failed (Mismatch) | 3 |
| Missing (Default) | 1 |
| Compliance Score | 90.4% |
Audit Findings
| Key Path | Value Name | Status | Expected | Actual | Severity |
|---|---|---|---|---|---|
HKLM\SYSTEM\CCS\Services\LanmanServer\Parameters | SMB1 | FAILED | 0 | 1 | High |
HKLM\SOFTWARE\Policies\Microsoft\Windows\LLMNR | EnableMulticast | FAILED | 0 | 1 | Med |
HKLM\SYSTEM\CCS\Control\Lsa | LimitBlankPasswordUse | PASSED | 1 | 1 | Low |
HKLM\SOFTWARE\Policies\Microsoft\Windows\EventLog | MaxSize | FAILED | >= 16384 | 4096 | Med |
HKLM\SYSTEM\CCS\Control\Lsa\WDigest | UseLogonCredential | MISSING | 0 | [Not Set] | High |
Analysis: The system fails critical SMBv1 and LLMNR checks, increasing the risk of lateral movement and credential relay attacks. The EventLog size is below the recommended hardening threshold.
Next steps
- Run the remediation script to disable SMBv1 and LLMNR on the host.
- Update the registry to explicitly set
UseLogonCredentialto0to prevent WDigest credential caching. - Re-export the registry and re-run the audit to verify the 100% compliance score.
Connects securely to your tools. The creator never sees your data.
About this skill
Registry configuration drift often goes unnoticed because Group Policy doesn't always reflect the actual state of the local hive. This skill audits .reg export files against security baselines to identify misconfigurations and missing hardening keys.
What it does
- Parses registry exports by handling REGEDIT4 and Version 5.00 formats including DWORD, QWORD, binary, and multi-string values.
- Validates against baselines using YAML or CSV specifications for key paths, value names, and expected data.
- Supports flexible comparisons including equality, inequality, and numerical range checks for versioning or threshold settings.
- Generates compliance reports that highlight missing keys, incorrect values, and successful matches with a calculated pass-rate score.
- Automates data collection via a provided PowerShell script that targets specific security-relevant keys for export.
How it works
- Export target keys using the included PowerShell script to create a focused
.regfile for analysis. - Select a baseline from the provided starter set covering CIS and Microsoft hardening standards or provide a custom YAML/CSV file.
- Execute the auditor via the CLI to compare the live export against the chosen security baseline.
- Review results in the console or export them to a CSV for audit evidence and remediation planning.
Frameworks & tools
The skill utilizes Python 3 for the core auditing engine and PowerShell for secure registry data extraction. It supports standard registry formats and works with YAML and CSV for baseline definitions.
Why this beats prompting it yourself
Manual analysis of registry exports is prone to parsing errors, especially with multi-string and binary types. This skill provides a structured comparison engine that handles type-casting and range checks that standard LLM prompts often hallucinate or miscalculate.
Use cases
- Post-hardening verification to ensure scripts or GPOs actually applied the intended registry changes.
- Shadow IT detection by auditing machines not joined to a domain or managed by central policy.
- Audit evidence collection for compliance frameworks requiring proof of local machine configuration.
Known limitations
Does not support live registry editing or direct HKLM\SAM and HKLM\SECURITY access. Requires manual export of .reg files before analysis.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Legal & Compliance.
Requires pre-exported .reg files. Does not audit SAM/SECURITY hives due to safety. Baseline comparison is limited to defined YAML/CSV fields.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago