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 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 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 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 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.
- Organise Environments The top-level structure for your nodes.
- Scan Scan options Add the files and directories that matter to you.
- Automate Job schedule Change how often scans and other jobs run.
- Compare Configuration differencing See what differs between nodes, groups or files.
- Comply Policies Define the state you expect and check every scan against it.
- Comply Benchmarks Check nodes against CIS best practice.
- Act Events Track what happened and trigger actions.
- Report Reports View many nodes and node groups at once.
If something goes wrong#
Job History lists failed and partial jobs, with an error report for each. If you need more help, email helpdesk@cloudhouse.com.