These terms are used throughout the Monopam documentation and user interface.
Term | Meaning |
|---|---|
Resource | A system people connect to: a server, a desktop, a network device, a database, a Kubernetes cluster, an application. |
Connection type | How Monopam talks to a resource: RDP, SSH, VNC, Telnet, SFTP, Database or Kubernetes. A resource can have several. |
Vault item | A secret Monopam keeps: a user name and password, an SSH key, secret text, an OTP seed, a token. A vault item is assigned to a resource with a connection type. |
Space | A container that groups resources and vault items, usually by team or environment. Access to a space is itself controlled by a policy. |
Policy | A rule that decides who may do what. Resource Access, Vault Access and Space Access policies grant access; Password Rotation, Discovery and Recording policies run jobs or set behaviour; Request policies publish what users may ask for. |
Request | An approval waiting for a decision: a connection, a password reveal, a database statement, a shell command, a certificate. An approved request grants access for a time window. |
Gateway | The service that opens sessions to resources and records them. |
Site | A location (a data center, a plant, a branch). Gateways and resources in the same site are paired automatically. |
Agent | Software installed on a machine so Monopam can manage it from the inside. |
Recording | The replayable record of a session: video for graphical sessions, a terminal replay for text sessions. |
Audit log | The searchable list of everything that happened in Monopam, by whom and when. |
Access key | A credential for programs and native clients, used instead of a person's sign-in. |
Tenant | An isolated Monopam environment with its own users and data. Most installations have one. |