Lesson 10 C Explain Data Handling Best Practices Flashcards
Regulated data
is information that must be collected, processed, and stored in compliance with federal and/or state legislation. If a company processes regulated data collected from customers who reside in different countries, it must comply with the relevant legislation for each country.
A breach is where confidential or regulated data is read, copied, modified, or deleted without authorization. Data breaches can be accidental or intentional and malicious. A malicious breach is also referred to as data exfiltration. Any type of breach of regulated data must normally be reported to the regulator and to individual persons impacted by the breach.
Personally Identifiable Information
Personally identifiable information (PII) is data that can be used to identify, contact, or locate an individual or, in the case of identity theft, to impersonate him or her. A cell phone number is a good example of PII. Others include name, date of birth, email address, street address, biometric data, and so on. PII may also be defined as responses to challenge questions, such as “What is your favorite color/pet/movie?” PII is often used for password reset mechanisms and to confirm identity over the telephone. Consequently, disclosing PII inadvertently can lead to identity theft.
Some types of information may be PII depending on the context. For example, when someone browses the web using a static IP address, the IP address is PII. An address that is dynamically assigned by the ISP may not be considered PII. These are the sort of complexities that must be considered when determining compliance with privacy legislation.
Personal Government-issued Information
Personal Government-issued Information that is issued to individuals by federal or state governments is also PII. Examples include a social security number (SSN), passport, driving license, and birth/marriage certificates. Data collected and held by the US federal government is subject to specific privacy legislation, such as the US Privacy Act.
Healthcare Data
Healthcare data refers to medical and insurance records plus associated hospital and laboratory test results. Healthcare data may be associated with a specific person or used as an anonymized or de-identified data set for analysis and research, such as in clinical trials to develop new medicines. An anonymized data set is one where the identifying data is removed completely. A de-identified data set contains codes that allow the subject information to be reconstructed by the data provider. Healthcare data is highly sensitive. Consequently, the reputational damage caused by a healthcare data breach is huge.
Credit Card Transactions
There are also industry-enforced regulations mandating data security. A good example is the Payment Card Industry Data Security Standard (PCI DSS) that governs processing of credit card transactions and other bank card payments. It sets out protections that must be provided if cardholder data—names, addresses, account numbers, and card numbers and expiry dates—is stored. It also sets out sensitive authentication data, such as the CV2 confirmation number or the PIN used for the card.
Regulations such as PCI DSS have specific cybersecurity control requirements; others simply mandate “best practice,” as represented by a particular industry or international framework. Frameworks for security controls are established by organizations such as the National Institute of Standards and Technology (NIST).
Data Handling Best Practice
Employees should be trained to identify PII and to handle personal or sensitive data appropriately. This means not making unauthorized copies or allowing the data to be seen or captured by any unauthorized persons. Examples of treating sensitive data carelessly include leaving order forms with customers’ credit card details on view on a desk, putting a credit card number in an unencrypted notes field in a customer database, or forwarding an email with personal details somewhere in the thread or in a Cc (copy all) field.
Data Retention Requirements
Another issue for regulated data is its retention on both file and database servers and in backup files:
- Regulation might set a maximum period for the retention of data. For example, if a company collects a customer’s address and credit card information to fulfill an order and the customer then makes no further orders, the company might be expected to securely destroy the information it has collected.
- Regulation might also demand that information be retained for a minimum period. In the credit card example, the company should log when and how the protected information was destroyed and preserve that log for inspection for a given period.
Prohibited Content
Employee workstations should only be used for work-related activity and data storage. In this context, prohibited content is any information that is not applicable to work. It can also specifically mean content that is obscene or illegally copied/pirated. The acceptable use policies built into most employee contracts will prohibit the abuse of Internet services to download games, obscene material, or pirated movies or audio tracks. Employees should also avoid using work accounts for personal communications.
End-User License Agreements
Prohibited content also extends to the unauthorized installation and use of software. When you install software, you must accept the license governing its use, often called the end-user license agreement (EULA). The terms of the license will vary according to the type of software, but the basic restriction is usually that the software may only be installed on one computer or for use by one single person at any one time.
An EULA might distinguish between personal and corporate/business/for-profit use. For example, a program might be made available as freeware for personal use only. If an employee were to install that product on a company-owned device, the company would be infringing the license.
License Compliance Monitoring
Software is often activated using a product key, which will be a long string of characters and numbers printed on the box or disk case. The product key will generate a different product ID, which is often used to obtain technical support. The product ID is displayed when the application starts and can be accessed using the About option on the Help menu.
A personal license allows the product to be used by a single person at a time, though it might permit installation on multiple personal devices. A company may have hundreds of employees who need the same software on their computers. Software manufacturers do not expect such companies to buy individual copies of the software for each employee. Instead, they will issue a corporate-use license for multiple users, which means that the company can install the software on an agreed-upon number of computers for its employees to use simultaneously.
It is illegal to use or distribute unlicensed or pirated copies of software. Pirated software often contains errors and viruses as well. Enterprises need monitoring systems to ensure that their computers are not hosting unlicensed or pirated software. There are two particular situations to monitor for:
- Valid licenses—A personal license must not be misused for corporate licensing. Also, matching the number of corporate-use licenses purchased with the number of devices or users able to access the software at a given time can be complex. Various inventory and desktop management suites can assist with ensuring that each host or user account has a valid license for the software it is using and that device/user limits are not being exceeded.
- Expired licenses—The software product must be uninstalled if the license is allowed to expire or the number of devices/user accounts is reduced. It is also important to track renewal dates and ensure that licenses do not expire due to a lack of oversight.
Open-source Licenses
Software released under an open-source license generally makes it free to use, modify, and share and makes the program code used to design it available. The idea is that other programmers can investigate the program and make it more stable and useful. An open-source license does not forbid commercial use of applications derived from the original, but it is likely to impose the same conditions on further redistributions. When using open-source software, it is important to verify the specific terms of the license as they can vary quite widely.
Commercial open-source software may be governed by additional subscription or enterprise agreements to supplement the open-source software license.
Digital Rights Management
Digital music and video are often subject to copy protection and digital rights management (DRM). When you purchase music or video online, the vendor may license the file for use on a restricted number of devices. You generally need to use your account with the vendor to authorize and deauthorize devices when they change. Most DRM systems have been defeated by determined attackers, and consequently there is plenty of content circulating with DRM security removed. From an enterprise’s point of view, this is prohibited content, and it needs monitoring systems to ensure that its computers are not hosting pirated content files.
A security incident could be one of a wide range of different scenarios, such as:
- A computer or network infected with viruses, worms, or Trojans.
- A data breach or data exfiltration where information is seen or copied to another system or network without authorization.
- An attempt to break into a computer system or network through phishing or an evil twin Wi-Fi access point.
- An attempt to damage a network through a denial of service (DoS) attack.
- Users with unlicensed software installed to their PC.
- Finding prohibited material on a PC, such as illegal copies of copyrighted material, obscene content, or confidential documents that the user should not have access to.
Incident response plan (IRP)
sets out procedures and guidelines for dealing with security incidents.