How HP Insights protects your data: security and data flow
When you evaluate a cloud print platform, the questions that matter most are about data. What leaves your network? How is it protected, where is it stored, and how long is it kept? This page answers those questions for HP Insights and explains the controls you have over each one.
In summary
- Secure Print Direct jobs typically stay on the local network.
- Secure Print jobs are encrypted in transit and at rest.
- Authentication remains with your identity provider.
- Data residency and personal-data collection are configurable.
- Encryption keys can be managed by HP Insights or by your organization.
What leaves your network (and what doesn’t)
HP Insights handles two kinds of data, and treats them differently depending on the workflow. Job content is the document itself, the file a user prints. Job metadata is information about printing: who printed, when, how many pages, in color or mono, on which device. Metadata powers analytics and policy enforcement. Depending on your Data Privacy settings, personal fields within metadata can be collected, hashed, or not collected. Content only exists so a held job can print when it’s released.
| Data type | Where it goes | How it’s protected |
|---|---|---|
| Job content (documents) |
Secure Print Direct jobs go from the workstation straight to the printer, so they normally stay on your network. If cloud-based delivery is turned on and the workstation can't reach the printer directly, the job is sent through HP Insights instead. Print Scout encrypts it with Zero Knowledge Encryption (ZKE) before uploading it, so it's already encrypted when it reaches cloud storage, and it's deleted once it's released. See Off-Network Secure Print Direct through the Cloud. Secure Print jobs are held encrypted until they're released, and where they're held depends on how they were submitted. For jobs sent from a computer through Print Scout, the Cloud Storage setting decides. With it turned off, which is the default, jobs are stored only on the user's workstation. With it turned on, they're stored on the user's workstation and in HP Insights. Jobs submitted from a mobile device are the exception, because they're always stored in the cloud, even when Cloud Storage is turned off. See Secure Print settings. |
Print Scout encrypts print jobs with AES-256 on the workstation, and also encrypts them with zero knowledge encryption before upload unless the Cloud Connector and Cloud Release are both on. Jobs are also encrypted in transit (TLS) and at rest in cloud storage (server-side encryption (SSE-S3), plus your own key as a separate layer if you use Enterprise Key Management). See Advanced encryption. Deleted on release or expiry. |
| Job metadata | Sent to the platform for policy, cost tracking, and analytics. | Encrypted in transit. Personal fields can be configured for anonymization before storage. |
| User identity | Authentication happens against your identity provider. Secure Print receives identity assertions, not passwords. | SAML / OIDC federation. Per-field anonymization (collect, one-way hash, or don’t collect). |
| Device data | Device Scout sends printer make, model, status, and meter reads to populate fleet inventory and Insights. | Encrypted in transit. No document data is involved. |
A detail your firewall team will care about: Scouts and connectors make outbound HTTPS connections to the platform. No inbound firewall rules are typically required, and users don’t need a VPN.
How print jobs are protected
On the workstation
Print Scout always applies Zero-Knowledge Encryption (ZKE) to print jobs stored on the workstation, so a job is always encrypted while it waits on the user's computer. The copy uploaded to cloud storage also has ZKE, except when both Cloud Connector and Cloud Release are enabled.
When both Cloud Connector and Cloud Release are enabled, job content encryption (ZKE) is turned off automatically, because the job is delivered to the printer from HP Insights rather than through Print Scout, and only Print Scout can decrypt ZKE-encrypted job content. The job is still encrypted in transit using TLS and at rest in cloud storage using AES-256, with an additional encryption layer if EKM is enabled. The difference is that HP Insights can access the job content to deliver it to the printer.
Job name encryption is a separate setting and isn't affected. It stays as your administrator set it in Print Job Name. See Advanced Encryption.
The key that Print Scout uses is protected by the operating system rather than stored as plain text on the workstation:
- On Windows, Print Scout protects it with the Windows Data Protection API (DPAPI), at the computer level.
- On Mac, Print Scout 3.0 and later store it in the macOS System Keychain. Earlier versions protected it with a key based on the computer's ID, so update Mac Print Scout to 3.0 or later to use the System Keychain.
In transit
Everything that moves between your environment and the platform (Print Scout submissions, release commands, console sessions, mobile submissions) travels over TLS-encrypted HTTPS.
At rest
HP Insights encrypts every print job it stores in the cloud with server-side encryption (SSE-S3) by default, however the job was submitted. If your organization needs to control the key itself, Enterprise Key Management adds a second layer with your own key from your AWS account; it does not replace the first:
| Protection | How it works | Best for |
|---|---|---|
| Server-side encryption (always on) | Cloud storage encrypts each job with server-side encryption (SSE-S3). You don't need to set anything up. | Every organization. |
| Enterprise Key Management (bring your own key) | HP Insights encrypts each job with a key you own and control in your own AWS KMS account before it's stored, so the job is encrypted twice: with your key and with server-side encryption. If you revoke the key, access to encrypted job content is no longer possible. | Regulated industries and zero trust security programs that require customer-held keys. |
When Cloud Storage is turned on, the layers on a job sent through Print Scout depend on whether Cloud Release and Enterprise Key Management are turned on. Server-side encryption (SSE-S3) applies in every case. See On the workstation.
| Cloud Release | Enterprise Key Management | Encryption on the job in cloud storage |
|---|---|---|
| Off | Off | ZKE and server-side encryption |
| Off | On | ZKE, EKM and server-side encryption |
| On | On | EKM and server-side encryption |
| On | Off | Server-side encryption |
Jobs submitted from a mobile device don't go through Print Scout, so they don't have ZKE. They have server-side encryption, plus EKM if it's turned on.
Where your data lives
Data residency is configured, not assumed. With Data Privacy and Regional Document Storage, you choose the region or regions where held job documents are stored. An EU organization can keep EU users’ documents in an EU region while US documents stay in a US region. You can run several regions side by side, each with its own rules, and route users to the right one.
Each region also has its own rules for personal information. For each field (username, email, full name, phone number, department, location, and so on) you pick one of three treatments:
Collect
The field is stored as-is and available in reporting. Use this where you need print accountability by named user.
One-way hash
The field is irreversibly hashed before storage. Reports can still distinguish users and count activity, but no one, including HP Insights, can recover the original value.
Don’t collect
The field is omitted entirely and never reaches the platform.
Keeping job content out of cloud storage
Regional Document Storage chooses which cloud region held jobs are stored in, and it applies to Secure Print jobs only. It doesn't keep job content on your own servers. If your organization doesn't want job content in cloud storage at all, leave Cloud Storage turned off, which is the default. Jobs sent from computers through Print Scout then stay encrypted on users' workstations until they're released.
Jobs submitted from a mobile device are still stored in the cloud, and features that release jobs from the cloud, such as Cloud Release, need Cloud Storage turned on. See Secure Print settings.
How long data is kept
Held print jobs are temporary. Released jobs are deleted immediately, unless the user chooses to keep the job for reprinting, where your settings allow it. A kept job stays available for release until it’s deleted or its lifetime expires. If an immediate deletion operation fails, the job becomes inaccessible once its configured lifetime expires and is permanently removed by an automated storage lifecycle process within seven days, so uncollected documents don’t pile up in storage. Job records (metadata) are retained separately for analytics and are not deleted when content is purged. You set the job lifetime for your organization with the Purge jobs after setting. It can be set from 1 hour up to 7 days, and it's 2 days by default. See Secure Print settings.
Analytics data is kept longer, since trend reporting needs history. See Fleet Analytics data retention and Print Analytics data retention for the current periods.
Identity and Zero Trust
HP Insights follows Zero Trust principles: no request is trusted because of where it comes from or what network it’s on. Every request — a user releasing a job, a Scout reporting in, an API integration pulling data — is authenticated and authorized independently, with access scoped to least privilege for that specific operation. There is no implicit trust based on network location.
Identity itself is not duplicated. HP Insights consumes your identity provider’s authentication decisions rather than maintaining a separate credential store. For how federation, single sign-on, and account provisioning work, see How users are identified.
Security FAQ
| Question | Answer |
|---|---|
| Do users need a VPN? | No. |
| Are inbound firewall rules required? | Typically no. Scouts and connectors make outbound-only connections to the platform. |
| Does HP Insights store passwords? | No. Authentication federates to your identity provider; HP Insights receives identity assertions, not passwords. |
| Can I use my own encryption keys? | Yes, with Enterprise Key Management. |
| Can I keep data in a specific region? | Yes, with Data Privacy and Regional Document Storage. |
| Can I avoid storing personal information? | Yes. Per-field controls let you choose to collect, one-way hash, or not collect personal fields. |
What this means for your evaluation
For a security review, it comes down to this: documents either never leave your network (Secure Print Direct), or they’re encrypted with keys you can own, stored in regions you choose, and deleted on a schedule you control. Personal data collection is a per-field policy decision, not a platform default you have to accept. And identity stays with your identity provider; HP Insights consumes it rather than duplicating it.