This topic contains a Glossary of Terms related to Cloudhouse Guardian.
| A |
B |
C |
D |
E |
F |
G |
H |
I |
J |
K |
L |
M |
N |
O |
P |
Q |
R |
S |
T |
U |
V |
W |
X |
Y |
Z |
A
| Agent |
Similar to a Connection Manager, but installed and run locally on the node to be scanned. Agent-based and agentless scans perform the same scan steps. |
| Appliance |
The software and services required to run the Guardian platform. Guardian can host your appliance in our cloud or it can be deployed as a virtual machine behind your firewall or in your cloud provider.
|
C
| Configuration Item |
A piece of configuration data in a Guardian scan, represented in the scan by a grey box. |
| Connection Manager |
A small software component that performs agentless node scans. There are versions available for both the Windows and Linux/SSH platforms as each is intended to scan different kinds of nodes. Multiple Connection Managers can be deployed throughout your network to allow for fine-grained network access control. Using Connection Managers removes the requirements for the Guardian appliance to have direct access to your entire network. |
E
| EULA |
See End User Licensing Agreement.
|
| End-User Licensing Agreement |
The mandatory terms that cover the usage of Cloudhouse Guardian by an End Client. |
| Environment |
The organisational unit for nodes used in scan scheduling and reporting. A node can only be a member of one environment.
|
N
| Node |
A system, service, application, or device that is scanned in Guardian. We support a wide variety of systems and devices out of the box. If you need something that we don’t cover yet, we’re happy to work with you. |
| Node Group |
The basic organisational unit for nodes in Guardian. Node Groups are used for customising scan settings and can also be used for reporting. A node can be a member of an unlimited number of node groups.
|
S
| Scan |
A snapshot of a node’s configuration state at a point in time. Scans can be compared between nodes, or on the same node over time. |