As a SaaS ITOM platform, the confidentiality, integrity, and availability of critical data are ensured.
A standards-based security architecture is implemented, which guarantees the highest levels of security, control, availability, and scalability.
Security is implemented in the following areas:
Agents and gateways
Agents are installed on customer target resources on a private network. There are two kind of Agent installations:
- Proxy Agent: The agent needs outgoing communication with the Gateway on port 3128, the HTTP proxy server. Using the proxy server, the agent establishes a connection with OpsRamp and uses a secured tunnel based on TLS 1.2.
- Direct Agent: The agent establishes a connection with OpsRamp and uses a secured tunnel based on TLS 1.2.
Gateways are virtual appliances that collect data from the managed environment, which have the following characteristics:
- Sit in a client internal environment with a private IP behind the firewall.
- Establish a secure connection to the Cloud over the internet using a secured tunnel based on TLS 1.2.
|Function||A lightweight agent that runs on Windows and Linux systems in the managed environment.|
|Form factor||Windows and Linux binaries:|
|Access controls||All configuration updates for the Gateway are pushed from the cloud using an encrypted channel created by the Gateway.|
|Operating System||Hardened configuration of Ubuntu Server. Hardening includes the following measures:|
|Form Factor||Gateway is a virtual appliance that runs on a hypervisor.|
The requirements for connectivity include:
|Outbound||Agents and gateways require outbound network connectivity to the cloud. If your organization has firewall policies to limit outbound access to specific IP addresses, agents and gateways must have access OpsRamp IP addresses.|
|Inbound||N/A - OpsRamp does not impose inbound connectivity requirements.|
The following diagram shows the configuration options:
- Agent and Gateway each have a direct connection to the cloud.
- Each agent has an HTTP proxy connection to the gateway and each gateway has a direct connection to the cloud.
- Each agent has an HTTP proxy connection deployed on a standalone server and each gateway has a direct connection to the cloud.
Agents work with standard HTTP Proxy.
OpsRamp collects and stores only the data needed for IT operations management functions on the devices it manages.
OpsRamp does not collect and store data from monitored applications, including data in database tables, application transaction contents, and user credentials.
|Data Type||Data Collected||Data Storage and Security|
|Performance statistics||System-level information needed to monitor the performance and health of managed devices:||Device performance statistics are stored only in the cloud. The Agent and Gateway collect and transmit this data to the Cloud.|
|Events and SNMP traps||Operating System events and traps generated by SNMP agents.||The Gateway and Agent process events and traps locally and send resulting alerts to the Cloud using a secure channel. Raw event data is not stored in the Cloud.|
|Resource configuration and metadata||System-level information needed to asset device configuration status:||The Gateway and Agent send configuration data to the Cloud using a secure channel|
|Device Credentials||Credentials (username/password) needed to discover devices, access performance and configuration data, and log into devices to run automation scripts.||The IT administrator provides device credentials to OpsRamp using its user interface. Device credentials are stored in the Cloud, using industry-standard 2048-bit RSA encryption.|
|Data classification||OpsRamp collects and stores only data required for IT operations management on managed devices and applications. Data that OpsRamp collects is limited to device performance metrics, performance and failure events, and configuration information.|
|Data isolation||OpsRamp implements strict multi-tenancy controls to ensure strict data isolation between customers.|
|Data encryption (in-flight)||All data transmitted between the Agent/Gateway and the Cloud are encrypted with TLS v1.2 standards.|
|Data encryption (at-rest)||Resource credentials stored in the Cloud are encrypted using 2048-bit RSA encryption.|
|Authentication||Cloud offers SAML and OAuth2 based authentication. OpsRamp also supports third-party authentication services such as OneLogin, Okta, and ADFS. The Cloud supports two-factor authentication.|
|User access management||OpsRamp has extensive role-based access controls. OpsRamp access controls are granular to the managed device, user, and feature.||APIs||OpsRamp provides REST APIs for integration with the cloud. OpsRamp REST APIs are backed by OAuth2 based authentication.||Regulatory and Compliance Requirements||OpsRamp does not collect personally-identifiable information (PII). OpsRamp is hosted in co-location facilities provided by two United States-based data center providers. Each provider has its own security certifications including SAS and SSAE.|
OpsRamp supports an extensive set of security features to ensure that management data is accessed only by authorized users.
|Encryption||All sensitive data is encrypted in OpsRamp. Customer data, including inventory, metrics, alerts, and tickets, is logically partitioned and stored under the tenant. Customer data is accessible only to authorized tenant users.|
|Role-based access control||OpsRamp supports comprehensive role-based access controls. User access to devices and actions in OpsRamp is controlled by fine-grained permissions. Permissions are assigned based on user roles.|
|Identity management||OpsRamp provides multiple options to manage user identity:|
|Authentication||OpsRamp supports two-factor authentication using Yubico YubiKey.|
|Passwords||OpsRamp follows standard practices for passwords:|
On contract expiration, OpsRamp inactivates the tenant in the OpsRamp platform. An inactive tenant’s instance inventory, metrics, and alerts data are available in the passive state in the platform, but monitoring, alerting, and other management functions are no longer available.
Based on mutual agreement between OpsRamp and the customer, OpsRamp deletes all tenant information from the Cloud. The data archival retention policy provides that deleted tenant data is available in the archival repository for ninety days.
Role-based access controls support fine-grained access control based on user and user groups, device and device groups, specific features, and resource credentials.
Operations and development processes follow methodologies that ensure the managed data security.
OpsRamp is SOC 2 Type II certified.
|Infrastructure management||The platform infrastructure is managed according to industry-standard practices:|
|Audit processes||Customers can run their own security audit on the Agent, Gateway, and publicly facing OpsRamp URLs. The Cloud is managed using another instance of OpsRamp. Audit recordings of management activities on OpsRamp can be provided as needed.|
Production access controls
Physical access to the production area is controlled by biometric and smart card access. Access to data centers is restricted to authorized personnel with 24×7 security monitoring and CCTV surveillance across facilities.
OpsRamp production environments are protected by 24×7 automated network-level intrusion prevention systems. IP and port-based firewalls continuously monitor authentication logs on Linux servers. Inbound and outbound traffic at various entry points is monitored and vulnerability checks are regularly performed on servers. In the event of a breach, more firewall rules are used to block the specific IP ranges, and passwords, encryption keys, and algorithms are changed.
All passwords stored with OpsRamp are encrypted. User passwords in OpsRamp are a one-way hash for secure password storage. OpsRamp ensures two levels of password security for data in transit:
- All communication between cloud and providers takes place over TLS.
- Sensitive information in transit is encrypted by unique keys.