Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Registry Policy Auditor

    1

    Audit Windows registry exports against CIS-style security baselines with automated parsing and compliance reporting.

    $2.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Registry Policy Auditor

    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

    MetricValue
    Total Keys Checked42
    Passed (Correct)38
    Failed (Mismatch)3
    Missing (Default)1
    Compliance Score90.4%

    Audit Findings

    Key PathValue NameStatusExpectedActualSeverity
    HKLM\SYSTEM\CCS\Services\LanmanServer\ParametersSMB1FAILED01High
    HKLM\SOFTWARE\Policies\Microsoft\Windows\LLMNREnableMulticastFAILED01Med
    HKLM\SYSTEM\CCS\Control\LsaLimitBlankPasswordUsePASSED11Low
    HKLM\SOFTWARE\Policies\Microsoft\Windows\EventLogMaxSizeFAILED>= 163844096Med
    HKLM\SYSTEM\CCS\Control\Lsa\WDigestUseLogonCredentialMISSING0[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

    1. Run the remediation script to disable SMBv1 and LLMNR on the host.
    2. Update the registry to explicitly set UseLogonCredential to 0 to prevent WDigest credential caching.
    3. 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

    1. Export target keys using the included PowerShell script to create a focused .reg file for analysis.
    2. Select a baseline from the provided starter set covering CIS and Microsoft hardening standards or provide a custom YAML/CSV file.
    3. Execute the auditor via the CLI to compare the live export against the chosen security baseline.
    4. 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.

    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. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    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

    Permissions

    Terminal / Shell
    Read Files
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill bridges the gap between Group Policy and reality by auditing the actual local registry state. It identifies 'configuration drift' where settings may have been manually altered or failed to apply, providing a definitive compliance report that standard GPO reports might miss.

    The skill includes the core Python auditing engine, a library of CIS-style security baseline templates in YAML format, and a dedicated PowerShell script to automate the export of security-relevant registry keys.

    Yes, you can easily create custom baselines using simple CSV or YAML files. This allows you to audit proprietary software settings or internal corporate security standards alongside the standard CIS benchmarks.

    The auditor is designed to handle standard `.reg` files, including REGEDIT4 and Version 5.00. It correctly parses complex data types like DWORD, QWORD, and multi-string values that often cause errors in manual or LLM-only analysis.

    For security reasons, this skill does not have write access to your registry. It is a read-only auditing tool designed to identify risks; any necessary remediations must be applied manually or through your existing configuration management tools.

    New in Legal & Compliance