Red Hat Insights - Security Information

Updated -

Introduction

Red Hat Insights provides a mechanism for customers to get actionable intelligence regarding suggested improvements to deployed Red Hat software. As part of this optional offering, Red Hat processes configuration data about a customer’s environment using Red Hat hosted and/or provided tools; this document covers the security measures Red Hat puts in place to provide secure transmission, processing, and analysis of this data by those tools.

Red Hat is committed to evaluating, implementing and monitoring the industry security standards for those tools as they continue to evolve.

Insights Client

On Premise Security

Security of customer systems is paramount and Red Hat Insights has made extensive efforts to ensure that our shipped software meets the highest standards.`

  • The Insights Client, which executes on premise, has been through a security review by Red Hat Product Security, which is the same team that addresses security concerns in all other products across the Red Hat portfolio.
  • Communication with Red Hat can be sent through secure proxies for audit and network ACLs.
  • Enrollment is opt-in, which means we’ll never collect data from systems without your explicit approval, and can be scheduled.
  • All communication with Red Hat occurs over encrypted channels using TLS using mutual certificate authentication.
  • Resource usage of the client is controlled via CGroup / Resource Constraints to minimize the impact data collection has on critical business processes on customer servers
  • The Insights Client is Open source.

Client Side On Premise Data Control

Insights-Client allows customers to have control of the information that is monitored for analytical purposes; and the Insights-Client makes it simple for subscribers to view the information which is monitored.

  • Insights-Client collects both targeted and minimal system information rather than entire logs.
  • Red Hat automatically attempts to remove critical security information such as passwords before uploading when stored in standard locations
  • Common types of sensitive information can be opted out of through pre-built configuration profiles
  • Subscribers can denylist any command, file, or piece of metadata that they prefer not be monitored by Red Hat Insights.
  • The commands, files, and metadata monitored by Insights-Client are listed in a single file that is GPG signed and available at any time for easy inspection.
  • Personally Identifiable Information is not targeted for collection.
  • Local payload inspection is available to allow for the collector to be ran locally and the data collected to be audited

Infrastructure and Architecture

Security of customer data in Red Hat is a priority and every effort is made to ensure that information is not unnecessarily persisted and that it is secured using industry standard best practices.

  • All customer data provided is stored within a secure data center with controlled access.
  • All volumes containing customer data at rest are encrypted with AES 256 bit encryption
  • All parts of the internal infrastructure transmit their logs to a centralized log aggregator for inspection and analysis.
  • Red Hat Security conducts regular architecture review of infrastructure
  • Data is always encrypted in transit.
  • All API calls for reading and writing data must be authenticated.

Maintaining Security

  • All software is analyzed with static code analyzers and all reported issues are fixed before code is deployed into production.
  • Code is peer reviewed.
  • Development teams follow an Agile software delivery lifecycle, which means that security related defects can be addressed rapidly, and software patches are regularly released as part of our continuous delivery model.
  • Patches that can impact end users will be applied as soon as possible, but may necessitate end user notification and scheduling a service window in some cases.
  • All infrastructure software components are continuously monitored for known vulnerabilities (CVEs) and proactively patched.
  • Penetration testing is conducted by both internal and external parties.
  • Access to systems that handle customer data is controlled via multi factor authentication and authorization controls. Access is granted on a need to know basis.

Related Resources


System information collected by Red Hat Insights
Obfuscating IP addresses
YAML-style deny list configuration for Red Hat Insights client