---
title: "Get started with Guardian Classic"
description: "Three stages from choosing where Guardian runs to your first scanned nodes."
product: "Guardian"
edition: "Classic"
type: "get-started"
url: "https://docs.cloudhouse.com/guardian/classic/getting-started/"
---
# Get started with Guardian Classic

Guardian tracks the configuration of your infrastructure, in the cloud and on-premises, so you can see what changed and check it against the state you expect. Getting it running takes three stages, usually done by different people.

Applies to: `Guardian Classic` `Cloudhouse-hosted` `On-premises`

New to the terms? [Guardian concepts](https://docs.cloudhouse.com/guardian/classic/getting-started/concepts/index.md) explains instances, Agents, Connection Managers, nodes and the rest.

## Plan your instance

Choose where Guardian runs, get your instance deployed, and work out which scanning services you need and where. You'll do this with your Cloudhouse representative. If Cloudhouse hosts your instance, there's nothing to install for this stage.

[Plan your instance](https://docs.cloudhouse.com/guardian/classic/getting-started/plan-your-instance/index.md) About 2 minutes · for whoever owns the Guardian roll-out

## Prepare your network

Put scanning services in place, give them service accounts, and open the firewall ports they need. This applies whether your instance is hosted or on-premises, because the scanning services run on your network.

[Prepare your network](https://docs.cloudhouse.com/guardian/classic/getting-started/prepare-your-network/index.md) About 3 minutes · a checklist for your infrastructure team

## Add and scan your first nodes

Add nodes one at a time, in bulk or through an integration, then scan them and see the results.

[Add and scan your first nodes](https://docs.cloudhouse.com/guardian/classic/getting-started/add-and-scan-nodes/index.md) About 2 minutes · for the people who'll use Guardian day to day

## Where next

Once your nodes are scanning, these features let you organise them, shape scans and act on what Guardian finds.

- [*Organise* **Node groups** Group similar nodes for scan options, policies and jobs.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/node-groups/node-groups/index.md)
- [*Organise* **Environments** The top-level structure for your nodes.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/environments/environments/index.md)
- [*Scan* **Scan options** Add the files and directories that matter to you.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/scan-options/scan-options/index.md)
- [*Automate* **Job schedule** Change how often scans and other jobs run.](https://docs.cloudhouse.com/guardian/classic/control/job-schedule/job-schedule/index.md)
- [*Compare* **Configuration differencing** See what differs between nodes, groups or files.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/configuration-differencing/configuration-differencing/index.md)
- [*Comply* **Policies** Define the state you expect and check every scan against it.](https://docs.cloudhouse.com/guardian/classic/control/policies/policies/index.md)
- [*Comply* **Benchmarks** Check nodes against CIS best practice.](https://docs.cloudhouse.com/guardian/classic/control/benchmarks/benchmarks/index.md)
- [*Act* **Events** Track what happened and trigger actions.](https://docs.cloudhouse.com/guardian/classic/control/events/events/index.md)
- [*Report* **Reports** View many nodes and node groups at once.](https://docs.cloudhouse.com/guardian/classic/reports/reports/index.md)

## If something goes wrong

[Job History](https://docs.cloudhouse.com/guardian/classic/control/job-history/job-history/index.md) lists failed and partial jobs, with an error report for each. If you need more help, email [helpdesk@cloudhouse.com](mailto:helpdesk@cloudhouse.com).