Guardian

Guardian: from policy to control to evidence

Guardian is Zennite’s product family for making policy operational. It is a control plane, not a chatbot: it turns written policy into machine-actionable controls, and will check those controls on real systems and show where policy and reality diverge.

Policy & governance

Guardian Nexus

Turn written policy into testable controls.

The policy layer. Structures requirements and resolves them to technical controls, reusing catalogue controls and specifying new ones where needed.

Explore Nexus
Endpoint validation

Guardian Angel

Check controls against actual system state.

The endpoint layer. Will evaluate approved controls beside the systems they govern, return evidence and deviations, and guard operator commands.

Explore Angel

What each component does

Guardian Nexus Guardian Angel
Purpose Turns written policy into reviewable technical controls Checks approved controls where systems run
Input Policies, regulations, baselines and a control catalogue Approved, versioned control definitions and local system state
Output Mapped and generated controls with source lineage and review state Findings, evidence references and candidate deviations

Guardian Nexus in detail · Guardian Angel in detail

How they work together

This is the target architecture. Nexus sends Angel approved control definitions. Angel sends Nexus evidence and findings.

  1. Policy in

    Nexus registers a policy, splits it into clauses and links each clause to its entities.

    Available to demonstrate

  2. Controls resolved

    Nexus maps each requirement to catalogue controls or specifies a new one, with provenance for review.

    Available to demonstrate

  3. Approved bundle

    Nexus packages reviewed, versioned controls for the systems they apply to.

    In development

  4. Local evaluation

    Angel runs only approved, applicable checks beside the system and records what it sees.

    In development

  5. Findings returned

    Angel returns results, evidence and candidate deviations, linked to control, asset, policy version and time.

    In development

  6. Governed response

    Nexus links each finding to its policy intent; people decide on remediation or an exception.

    In development

Standalone operation

Angel will also run without Nexus. Authorised staff supply a validated local control bundle and Angel assesses and reports within the same boundaries. Without Nexus, findings may not trace back to a source clause.

What Guardian does not claim

  • A mapped or generated control states what to check. It is not an executed check, a fix or proof of compliance.
  • Guardian does not replace GRC, IT service management or endpoint management tools. They remain the systems of record.
  • Live endpoint assessment, evidence collection, deviation management and the Nexus–Angel exchange are in development as products. Pilots run endpoint checks and evidence collection through a custom Angel deployment.