Ticket types for Endpoint Data Governance¶
To learn more about how Coro protects an organization's endpoint data, see Introducing Endpoint Data Governance. To learn more about what information constitutes these sensitive data types, see Regulatory sensitive information types.
Coro generates tickets relating to endpoint data governance when incidents are identified that involve the following sensitive data types and the Admin user has enabled Privacy sensitive data settings in Control Panel > Endpoint Data Governance:
Endpoint drive with NPI¶
Coro detected unauthorized exposure of NPI (Non-Public personal information) data on the device (see Regulatory sensitive information types.) Tickets are classified as suggested for review and are automatically closed after the review period of two weeks.
| Action | Outcomes |
|---|---|
| Close ticket | Close this ticket as considered remediated and take no further action. Note: When a device is removed from protection, all open tickets associated with the device are automatically closed. |
| Encrypt drive | Encrypts the hard drive of the device. A record is added to the Activity Log: "Drive encryption was requested on <device name> of user <user> (drive: '<drive >')" When drive encryption is complete, a record is added to the Activity Log: "Drive was encrypted on <device name> by <user>" Encryption keys are stored on both the device (by BitLocker) and on the Coro servers. |
Endpoint drive with PCI¶
Coro detected unauthorized exposure of PCI (Payment card industry) data on the device (see Regulatory sensitive information types.) Tickets are classified as suggested for review and are automatically closed after the review period of two weeks.
| Action | Outcomes |
|---|---|
| Close ticket | Close this ticket as considered remediated and take no further action. Note: When a device is removed from protection, all open tickets associated with the device are automatically closed. |
| Encrypt drive | Encrypts the hard drive of the device. A record is added to the Activity Log: "Drive encryption was requested on <device name> of user <user> (drive: '<drive >')" When drive encryption is complete, a record is added to the Activity Log: "Drive was encrypted on <device name> by <user>" Encryption keys are stored on both the device (by BitLocker) and on the Coro servers. |
Endpoint drive with PHI¶
Coro detected unauthorized exposure of PHI (Protected health information) data on the device (see Regulatory sensitive information types.) Tickets are classified as suggested for review and are automatically closed after the review period of two weeks.
| Action | Outcomes |
|---|---|
| Close ticket | Close this ticket as considered remediated and take no further action. Note: When a device is removed from protection, all open tickets associated with the device are automatically closed. |
| Encrypt drive | Encrypts the hard drive of the device. A record is added to the Activity Log: "Drive encryption was requested on <device name> of user <user> (drive: '<drive >')" When drive encryption is complete, a record is added to the Activity Log: "Drive was encrypted on <device name> by <user>" Encryption keys are stored on both the device (by BitLocker) and on the Coro servers. |
Endpoint drive with PII¶
Coro detected unauthorized exposure of PII (Personally identifiable information) data on the device (see Regulatory sensitive information types.) Tickets are classified as suggested for review and are automatically closed after the review period of two weeks.
| Action | Outcomes |
|---|---|
| Close ticket | Close this ticket as considered remediated and take no further action. Note: When a device is removed from protection, all open tickets associated with the device are automatically closed. |
| Encrypt drive | Encrypts the hard drive of the device. A record is added to the Activity Log: "Drive encryption was requested on <device name> of user <user> (drive: '<drive >')" When drive encryption is complete, a record is added to the Activity Log: "Drive was encrypted on <device name> by <user>" Encryption keys are stored on both the device (by BitLocker) and on the Coro servers. |