Endpoint data governance

Why does Coro only detect a small number of sensitive data occurrences within a file when a file scan is run?

The purpose of file scans (on endpoint device drives and in general) is to identify files containing sensitive information so that admin users are notified of potential risks and can take appropriate measures to protect the sensitive information in question, by either:

• Adjusting data governance permissions
• Taking measures prescribed by their organization's data governance policy

It is not necessary to detect all occurrences of each type of sensitive information within a given file for that, so Coro limits the number of such detected occurrences to optimize performance and (in the case of endpoint devices) improve end-user experience.

What social security number (SSN) pattern does Coro detect?

Coro recognizes US social security numbers (SSNs). Coro additionally detects SSNs on a predefined list of keywords if the SSN is in an unrecognized format.

Under what circumstances does Coro automatically close Endpoint Data Governance tickets?

Tickets containing sensitive information, but that do not require manual review by admin users, are automatically closed.

Such tickets are included in the Coro console ticket log for audit, monitoring, analysis, and to satisfy regulatory compliance requirements. They are typically triggered automatically by events such as the detection of sensitive information in an email, file, or file sharing. Some examples of this type of ticket include:

• Personal Identifiable Information (PII) : IP and MAC address.
• Nonpublic Personal Information (NPI) : Monthly payment (financial content) and email address.
• Protected Health Information (PHI) : Medical Records Number (MRN).

Why does Coro create multiple Endpoint Data Governance tickets related to the same event?

Coro can identify stored sensitive information on user devices that potentially violate one or more regulatory or data compliance standards. Such information falls into one of the following categories:

• Personally Identifiable Information (PII) : Information connected to a specific individual that can be used to uncover that individual's identity, such as full name, email address, passport number, or social security number.
• Payment Card Industry (PCI) : A set of security standards created by major credit card providers designed to ensure that all companies that accept, process, store, or transmit credit card information maintain a secure environment.
• Protected Health Information (PHI) : Data collected, stored, used, or transmitted during the provision of health care services. This data includes patient name, medical history, and health insurance information.
• Non-Public Personal Information (NPI) : Personal financial data that is collected and stored by financial institutions. NPI is a combination of PII and other indicators. For example, social security numbers are PII indicators, but in combination with credit card information, they are also classified as NPI.

The following table lists sensitive information detectors that Coro is able to identify and their respective categories:

What is a false positive Endpoint Data Governance ticket?

These tickets are most likely not false positives, but rather Coro is generating data monitoring tickets according to your enabled monitoring options under Endpoint Data Governance.

To configure Endpoint Data Governance data monitoring in Coro:

1. Select Control Panel from the toolbar:

   

2. Select Endpoint Data Governance :

   

3. Enable or disable each option as applicable to your needs.

Can I exclude certain indicators to limit the number of tickets generated by Coro?

Yes, you can exclude Endpoint Data Governance monitoring options.

To exclude Endpoint Data Governance monitoring options:

1. Select Control Panel from the toolbar:

   

2. Select Endpoint Data Governance .
3. Disable the desired monitoring options:

   

Is there a document available that details how Coro helps companies follow the National Institute of Standards and Technology (NIST) framework?

See the Federal Information Security Modernization Act (FISMA) compliance document.

FISMA aims to reduce the potential risk of unauthorized data use, and to develop, document, and implement an information security and protection program disclosure. The governed federal agencies need to comply with the information security standards guidelines, and mandatory required standards developed by NIST.

Does Coro exclusively create Endpoint Data Governance tickets from data that is in english, or does it also translate and create Endpoint Data Governance tickets from other languages?

Endpoint Data Governance tickets are only created from data in english.

Does Endpoint Data Governance work on scanned documents?

Endpoint Data Governance can process standalone image files but does not support scanned PDFs or images embedded in documents such as Microsoft Word files. The supported image formats are:

• jfif
• jpeg
• jpg
• png
• tiff
• webp
• x-portable-anymap
• x-portable-bitmap
• x-portable-graymap
• x-portable-pixmap

Can Endpoint Data Governance scan SQL code?

Endpoint Data Governance can analyze SQL code found in shared files; however, it cannot scan SQL code embedded in the stored procedures of database systems.