osquery With Every Scheduled Query Checked First

osquery from its own repository, the signing key pinned by fingerprint. Its config check reads JSON only, so each scheduled query is prepared by osqueryi first, and the check runs off the daemon's database, whose lock would otherwise refuse every later change. The live test creates an account and sees the schedule log it as added. Original role, live-tested on Rocky Linux 10.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

ansibleMulti-cloud & platform-agnosticSecurity & Identityv1.0.0live-tested

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A Suricata IDS With ET Open And A Canary Rule AIDE, A Baseline And A Timer That Notices A Change An LDAP Directory That Refuses Anonymous Reads Authelia SSO Portal, Secrets Kept Out Of The Config, Proven By A Login Bandit, A shell=True Call Found At High Severity Boundary, Run To The Controller's Door Twice ClamAV Scanning On Loopback, Signatures Kept Current Dockle, A Root-User Finding With An Exit Code

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "ansible_osquery" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-osquery/any"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.