Australia, Zurich, Yokohama
Integration
Your estate changes faster than your change records. Servers drift from their baseline, changes get made outside the process, and audit season means stitching together tickets, spreadsheets, and every supplier's word for it.
Guardian by Cloudhouse surfaces your live Guardian data on a native ServiceNow dashboard, compliance posture, unreconciled drift, node inventory, and the changes that need attention, inside the platform your teams already work in.
Key features
- See compliance and drift at a glance: one dashboard with compliance score, failed checks, nodes monitored, and a compliance-and-drift trend over time.
- Reconcile change, both ways: every Guardian-detected change links straight to its native ServiceNow change request, so approvers see the detected change and the record side by side.
- Run many estates from one place: point the app at more than one Guardian instance and switch between them from the dashboard header.
- Keep trend history under control: choose how many days of compliance-trend history to keep per instance; older snapshots are purged automatically by a daily job, or on demand by an admin.
- Find any node fast: the all-nodes list pages at your chosen size (10 to 100) with a clear "showing X to Y of Z" count and an instant filter that matches anywhere across a row.
- Deep-link into Guardian: users with a Guardian account jump from a node or change straight into the Guardian web UI for full detail; a change's ServiceNow link opens the record in the standard ServiceNow view.
- Reads, never rewrites: the app links to your ITSM data; it never changes it.
- Self-contained and restriction-friendly: a scoped application that loads no external code at runtime, suiting regulated and restricted instances.
Why it matters
- One authoritative view, inside ServiceNow: stop reconciling drift in one tool and change in another.
- Audit-ready evidence: Guardian monitors configuration against embedded CIS Benchmarks and your own policies, building a continuous trail for frameworks including FCA, SOX, DORA, and Cyber Essentials.
- Catch the change that skipped the process: configuration that diverges from the approved baseline surfaces before it becomes an incident.
Who it's for
IT operations, security, and compliance teams running hybrid estates on ServiceNow, particularly in regulated sectors such as financial services, government, and healthcare.
- Enable visibility of Change in the customer environment
- Visibility of Change reconciliation undertaken by Guardian natively in ServiceNow
- Enable ServiceNow users to see result of Guardian data natively in ServiceNow without needing Guardian system access
- View Configuration Drift Events
First Store release of Guardian by Cloudhouse for ServiceNow. It surfaces Cloudhouse Guardian's configuration-drift detection and compliance evidence natively in ServiceNow:
- Compliance-score donut, plus failed-checks and failing-nodes cards
- Compliance and drift trend (renders once five daily snapshots exist)
- Change reconciliation linking Guardian-detected change to native change requests
- Multi-instance switching across Guardian instances
- Per-instance trend retention with a daily purge job
- Paginated, filterable node inventory
- Opt-in Guardian drift-event deep-link on change rows (admin toggle, off by default, gated by the guardian_web_user role)
- Node deep-links via a configurable UI URL root
- Read-only to customer data, with a single declared read-only change_request cross-scope privilege used only to resolve the change number for the drift link
- API and secret keys masked on entry
- Light, Dark and System themes
- End-user confirmation dialogue before opening any external link (a Store security requirement)
Not applicable for this application version.
- Core ServiceNow platform only, no plugin activation and no other Store app required
- Platform KMF encryption context for the password2 fields (auto-provisions on licensed production instances)
- A reachable Cloudhouse Guardian instance with REST API access, plus an API key and secret
- Outbound HTTPS to the customer's own Guardian host (entered on the Configuration screen)
- Declared cross-scope privileges, including a read-only change_request privilege used only to resolve the change number for the drift link
- No inbound integrations