- Démarrage
- Meilleures pratiques
- Modélisation de l'organisation dans Orchestrator
- Meilleures pratiques d'automatisation
- Optimisation de l'infrastructure Unattended à l'aide de modèles de machine
- Organisation des ressources avec des balises
- Exportation des grilles dans l'arrière-plan
- Appliquer la gouvernance de la connexion Integration Service au niveau de l'utilisateur
- Locataire
- À propos du contexte du locataire
- Recherche de ressources dans un locataire
- Gestion des Robots
- Connexion des Robots à Orchestrator
- Enregistrement des identifiants du Robot dans CyberArk
- Stockage des mots de passe de l’Unattended Robot dans Azure Key Vault (lecture seule)
- Stockage des informations d’identification de l’Unattended Robot dans HashiCorp Vault (lecture seule)
- Stockage des informations d'identification du robot Unattended dans AWS Secrets Manager (lecture seule)
- Suppression des sessions Unattended déconnectées et qui ne répondent pas
- Authentification du Robot
- Authentification du Robot avec les informations d'identification du client
- Configurer les capacités d’automatisation
- Solutions
- Audit
- Enforced encryption
- Intégration des magasins d'identifiants
- Gestion des magasins d'identifiants
- Accès au dossier du magasin d’informations d’identification
- Affectation de magasins d'informations d'identification à des dossiers
- L'Orchestrator Credentials Proxy
- Débogage d'Orchestrator Credentials Proxy
- Managing credential proxies
- Paramètres
- Registre
- Notifications
- Contexte des dossiers
- Processus (Processes)
- Tâches (Jobs)
- Apps
- Déclencheurs (Triggers)
- Journaux (Logs)
- Surveillance
- Index
- Files d'attente (Queues)
- Actifs
- À propos des actifs
- Gestion des actifs dans Orchestrator
- Gestion des actifs dans Studio
- Stockage des ressources dans Azure Key Vault (lecture seule)
- Stockage des ressources dans HashiCorp Vault (lecture seule)
- Stockage des ressources dans AWS Secrets Manager (lecture seule)
- Stocker des ressources dans Google Secret Manager (lecture seule)
- Connexions
- Règles métier
- Compartiments de stockage
- Passerelle d’agent
- Tests d'Orchestrator
- Service de catalogue de ressources
- Intégrations
- Résolution des problèmes
Enforced encryption
Enforced encryption in Orchestrator, covering which job, robot log, queue, and storage bucket data is encrypted at rest and how encryption affects search, reporting, and exported data.
Enforced encryption is a tenant-level configuration that makes Orchestrator store sensitive automation data encrypted at rest. When enforced encryption is enabled, Orchestrator encrypts job data, robot logs, queue items, and Orchestrator storage bucket content, and the option to store queues and Orchestrator storage buckets unencrypted is no longer available.
Enforced encryption adds application-level encryption (ALE) on top of the encryption that UiPath applies to all data: TLS 1.2 or higher for data in transit, and Transparent Data Encryption (TDE) with AES 256-bit encryption for data at rest. With enforced encryption, Orchestrator encrypts the data before storing it, using a key from the key management service (KMS).
For details, see Encryption and Customer-managed keys.
Disponibilité
Enforced encryption is available in Automation Cloud and Test Cloud for organizations on the Enterprise plan (Flex) or the Standard or Enterprise plan (Unified Pricing).
Enforced encryption is enabled on request by your technical account manager or UiPath Support, not from Orchestrator.
After enforced encryption is enabled, Orchestrator displays no setting for it.
Données chiffrées
The following table lists the data that Orchestrator encrypts when enforced encryption is enabled.
| Ressource | Encrypted fields |
|---|---|
| Tâches (Jobs) | Input arguments, Output arguments, Info, Environment variables |
| Job events | Info |
| Journal des évènements du Robot | All fields, except the fields listed in Unencrypted robot log fields |
| Éléments de file d'attente | Specific Data, Output Data, and the following processing exception fields: Reason, Details, Associated Image File Path. For the fields that stay unencrypted, see Unencrypted queue item fields. |
| Stockage Orchestrator | All content: Buckets, Packages, Job Attachments, Videos, Screenshots, Exports, Knowledge Bundles, Retention archives, Business rules |
Unencrypted robot log fields
The following robot log fields are not encrypted:
machineNamemachineIdwindowsIdentityrobotNameprocessNameprocessVersionjobIdfilenameinitiatedBytotalExecutionTimeInSecondslevellogTypeorganizationUnitIdqueueNametransactionIdtransactionStatetransactionStatustransactionExecutionTimeprocessingExceptionTypequeueItemPriorityqueueItemReviewStatus
Unencrypted queue item fields
The following queue item data is not encrypted:
AnalyticsDataReferenceProgressProcessingExceptionTypeProcessingExceptionCreationTime- Status, date, and key fields
- Queue item comments
- Queue item events. These contain no queue item payload data.
Queues and storage buckets
Queues and Orchestrator storage buckets have a Store in encrypted format option that lets you choose whether their data is encrypted.
With enforced encryption, this choice is no longer available, and all queues and Orchestrator storage buckets are encrypted automatically. The missing choice when creating a queue or an Orchestrator storage bucket is the only visible effect of enforced encryption in Orchestrator.
Enforced encryption applies only to storage buckets that use the Orchestrator storage provider. Storage buckets that use an external provider, such as Azure Storage, Amazon S3, or Google Cloud Storage, are not affected.
Limitations
Enforced encryption affects how you work with the encrypted fields:
- Search: Free-text search in robot logs and queue items works only on unencrypted fields. Encrypted fields, listed in Encrypted data, can't be searched.
- UiPath Insights: Encrypted data remains encrypted in UiPath Insights, so the encrypted fields are not available for reporting.
- Exported data: Orchestrator decrypts data when it leaves Orchestrator. Exported robot logs and webhook payloads contain decrypted data, so enforced encryption does not protect data after export.
- Audit logs: If enforced encryption has ever been enabled for a tenant, audit log entries for that tenant don't include job input arguments, output arguments, info, or environment variables.
- Healing Agent: Healing Agent is not available for tenants with enforced encryption. For details, see Healing Agent documentation.
For more information about encryption across UiPath services, see Encryption.