Minimal Sysmon Config for a Host Sensor, with Validator

    1

    Sysmon ships with Windows 11 and will log far more than any one detector reads.

    $29

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Minimal Sysmon Config for a Host Sensor, with Validator

    Example session with this skill installed

    I need to validate my current Sysmon configuration file named production_config.xml to ensure it isn't collecting unnecessary event types or missing the LSASS scope.

    • Read your context and instructions
    • Compiled the minimal sysmon config

    The validator has processed production_config.xml. It identified three points of drift from the minimal sensor policy, specifically regarding revocation settings and unauthorized event collection.

    Sysmon Configuration Audit Report

    CheckStatusDetail
    Collected CategoriesFAIL8 categories found; WmiEvent is missing
    Suppression PolicyFAILImageLoad is enabled (should be empty include)
    LSASS ScopingPASSProcessAccess correctly scoped to lsass.exe
    Hashing AlgorithmPASSSet to SHA256
    Revocation CheckFAILCheckRevocation is enabled; must be disabled
    Schema VersionPASS4.91

    Summary: The configuration is currently too noisy for a minimal sensor and is missing WMI persistence tracking. The enabled revocation checks will cause per-event network traffic, which violates the minimal-impact policy.

    Next steps

    • Apply the templates/sysmon-minimal.xml to restore the nine-category baseline.
    • Run scripts/Set-SysmonLog.ps1 to ensure the Operational log channel is locked to 256MB.
    • Re-run the validator after deployment to confirm an OK status.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Sysmon ships with Windows 11 and will log far more than any one detector reads. A sensor that evaluates a fixed set of behaviours should collect exactly that set: every extra event type is local log volume nobody reads, and ImageLoad alone fills a Sysmon log in hours. This is a minimal configuration that collects nine categories and explicitly switches the rest off, plus a validator that fails if the config drifts.

    templates/sysmon-minimal.xml: collects process create (1), network connect (3), driver load (6), remote-thread injection (8), handle opens against the login process scoped to lsass (10), autorun-registry persistence scoped to the Run / Winlogon shell and userinit / Image File Execution Options keys (12-14), WMI persistence (19-21), DNS queries (22) and process tampering (25). Every other Sysmon event type is written out as an empty include rule, so its off state is explicit and reviewable rather than merely absent. SHA256 hashing, revocation checking off, schema 4.91.

    scripts/check_sysmon.py: parses the config with the standard library and enforces the policy: the nine categories present, every other known event type an empty include (collects nothing), ProcessAccess scoped to lsass and not a blanket collection, RegistryEvent present, SHA256 hashing, revocation off. It exits 0 with a one-line summary or exits 1 listing exactly what drifted: a missing collected category, an off type quietly turned on, a lost lsass scope, an unexpected collection. Run it in CI over your committed config so a well-meaning edit cannot silently widen collection.

    templates/Set-SysmonLog.ps1: sizes the Operational channel (256 MB default) with overwrite retention and applies a channel SDDL so only administrators, SYSTEM and the sensor account read it.

    Reference: why each of the nine categories is collected, why the two high-volume ones are scoped down, why writing every other type out as an explicit off is the point, and how the log sizing fits. 7 tests. Windows 11 Sysmon; Python 3.9+ standard library; no network. This is the collection policy and its validator, not a detector; what you do with the events is your sensor's job.

    Requires Administrator rights for installation. Schema 4.91 specific. Optimized for endpoint sensors, not full forensic capture. Does not include detection logic.

    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 18 days ago

    Requires

    Windows 11
    Python 3.9+
    PowerShell 7+
    Windows
    Python

    Permissions

    Terminal / Shell
    Read Files
    Listed18 days ago

    What's inside

    Frequently Asked Questions

    This skill provides a pre-hardened Sysmon XML template and a Python validator that limits logging to nine high-signal categories, preventing your host sensors from being overwhelmed by disk-filling background noise.

    You will receive a schema-compliant Sysmon configuration XML, a Python-based policy validator script, and a PowerShell utility for hardening and sizing the Event Log channel.

    The configuration is specifically optimized for Windows 11 using Sysmon schema 4.91; while it may work on older versions, full compliance with the validation script requires these specific versions.

    The included Python validator acts as a deterministic gatekeeper, checking your XML for policy drift and ensuring specific security boundaries—like restricted LSASS access—are actually enforced before deployment.

    Yes, the validator uses only the Python standard library, making it compatible with any AI agent or automation pipeline capable of executing Python 3.9+ scripts to audit system state.

    The skill focuses on telemetry collection and validation; it does not include pre-written detection rules or SIEM alerts for the events it captures.

    New in LLM Ops