Data Security & Encryption Flashcards
Data Corruption
Refers to any unintended or undesirable alteration or distortion of data, rendering it inaccurate, unreadable, incomplete, or unusable. It occurs when the actual data content no longer matches the expected or intended data structure or format
“Erasing” Data
Performing a ‘delete’ operation against a file
-Data is usually recoverable
“Clearing” Data
Preparing the media for reuse
Data cannot be recovered using traditional methods
“Purging” Data
A more intense form of “clearing” data for media reuse
Meant for less secure environments
Degaussing
Erasing data using a strong magnetic field
“Destruction” of Data
Most secure means of sanitizing media
This is the final stage in the lifecycle of data
Means more than just “deleted”
Needs to be completely unrecoverable
Record retention
Policy used for data that is a liability.
Sensitive data is destroyed after a certain amount of time (usually one year)
This applies specifically to PII
This is sometimes imposed by law
-In that case, you MUST delete it when it ages out or there will be severe fines
Tape Backup Security
Policy used for data that is critical to business/government operations
Helps prevent ransomware attacks
Data-Security Baseline Control
List of controls that an organization can apply as a baseline (the bare minimum, typically depends on the kind of data that they are responsible for)
The baseline can only be changed by:
1) Scoping
2) Tailoring
Definition of Controls in Data Security
Things you can do to prevent or mitigate a loss of data
Role of the Data Owner in Data Security
Responsible for collecting the PII.
Usually a member of senior management
Can delegate the maintenance tasks
But cannot delegate total responsibility
Role of the Data Custodian in Data Security
Responsible for the day-to-day management of the data (for the exam the keyword here is day-to-day)
Role of the Data Administrator in Data Security
In role-based access control, they are responsible for granting appropriate access to personnel.
Role of the “Data User” in Data Security
Any person who accesses the data via a computing system is a “data user”
Zero Trust Security
A framework in which no user/system (inside or outside the network) should be trusted by default. Represents a paradigm shift in cybersecurity that challenges the traditional approach of relying primarily on perimeter defenses to protect an organization’s network.
Trust is never assumed, and access to data is granted based on a strict need-to-know and “least privilege” basis
Even when you do grant access, you are watching the user’s every move and are ready to respond to anomalous behavior at all times.
Three main:
1) Secure Defaults
2) Fail Securely
3) Trust but verify
4) Principle of Least Privelige
Principle of “least privilege”
Users and systems are granted the minimum level of data access necessary to perform their specific tasks. Access rights are continuously reviewed and adjusted based on roles, responsibilities, and changes in requirements.
General Data Protection Regulation (GDPR)
Places stringent requirements on data containing PII coming in and out of the European Union(EU)
Protects individuals rights when it comes to their personal data
1) Users can request all the data an organization has collected on them
2) If a user asks an organization to delete all of the data they have collected on them, they have to do it
3) Requires Organizations to be completely transparent about their privacy policy
4) If an organization has a data breach, it must be disclosed in under 72 hours
Makes it more difficult to do business with companies overseas
Compliance is enforced by ridiculously huge fines (Up to €20 million or 4% of the annual global turnover, whichever is higher)
Two ways to reduce GDPR requirements:
1) Anonymization
2) Pseudonymization
Anonymization in Data Security
Removing any actual PII from the data. Makes it impossible to identify the data object (done properly
Can reduce the GDPR restrictions
Psudonymization in Data Security
Using aliases to represent data to reduce the exposure of PII.
Can reduce the GDPR restrictions
“Data Processor” in GDPR
Person /authority/agency that processes personal data on behalf of the “data controller” (another GDPR term)
“Data Controller” in GDPR
The person or entity that controls processing of the data
Four levels of data classification
Class 0: Public, no damage occurs if it gets out
Class 1: Some Damage would occur. This data gets the basic level of protection
Class 2: Serious Damage would Occur if it gets out
Class 3: Greatest amount of damage would occur if it gets out
Class 3 data in Data Security
Greatest amount of damage would occur if it gets out
Government Side: “Top Secret”
Civilian Side:
“Confidential/Proprietary”
Class 2 Data in Data Security
Serious Damage would Occur if it gets out
Government Side: “Secret”
Civilian Side:
“Private”
Class 1 Data in Data Security
Some Damage would Occur if it gets out
Government Side: “Confidential” (CIU)
Civilian Side:
“Sensitive”
Class 0 Data in Data Security
No Damage would Occur if it gets out
Government Side: “Unclassified”
Civilian Side:
“Public”
Personally Identifiable Information (PII)
Any information that can be used to identify/locate a “data object”
A “data object” in data security
Any person that can be identified by their PII
The Data Lifecycle
1) Create
2) Store
3) Use
4) Share
5) Archive
6) Destroy
Mnemonic Device:
Cyber Security Unifies Software And Data
Six Data Related Roles
- Data Owner
- Data Custodian
- Data Administrator
- Data User
- Business Mission Owners
- Asset Owners
SQL Injection (SQLi)
Malicious SQL code is injected into an application’s input fields, so that the attacker can send queries to the database. Attackers can modify, delete, or steal data, and in severe cases, gain control over the entire database.
Cross-Site Scripting
Injecting malicious scripts into a website, which can then be executed by other users. These scripts can potentially steal authentication tokens or credentials, leading to unauthorized access to the database.
Cross-Site Request Forgery (CSRF)
CSRF attacks trick authenticated users into unknowingly executing unwanted actions on a website they are logged into. This can lead to unauthorized changes in the database or other malicious actions.
Brute Force Attacks
Attackers attempt to gain unauthorized access to the RDBMS by repeatedly trying different username and password combinations until they find the correct credentials. Brute force attacks can be mitigated by implementing account lockout policies and using strong, unique passwords.
Credential Sniffing
Attackers use various techniques to capture plaintext usernames and passwords as they traverse the network. Once obtained, these credentials can be used to gain unauthorized access to the RDBMS.
Denial of Service (DoS) and Distributed Denial of Service (DDoS)
DoS and DDoS attacks overwhelm the RDBMS with a flood of traffic, causing it to become unavailable to legitimate users. This disrupts database access and can lead to data unavailability during the attack.
Zero-Day Exploits
Exploits targeting vulnerabilities unknown to the vendor (zero-days) can be used to compromise the RDBMS. Attackers may gain unauthorized access, escalate privileges, or exfiltrate data using these unpatched vulnerabilities.
Time of Check (TOC) attack
In a TOC attack, an attacker exploits a timing window between the check (verification of permissions, privileges, etc.) and the actual use of the resource or action. The attacker gains unauthorized access by manipulating the conditions after the check is performed but before the action is executed.
For example, in a file access scenario, the application checks if a user has permission to read a file at a specific location. However, before the actual reading occurs, an attacker could replace or modify the file, changing its contents.
Time of Use (TOU) Attack
A TOU attack involves an attacker modifying or manipulating a resource after a check is performed, but before the resource is used. The attacker exploits the delay between the time of the check and the time the resource is used to maliciously alter the resource or conditions, potentially leading to unauthorized actions.
For instance, consider a financial transaction system where the balance is checked before a transfer. An attacker could modify the balance after the check is performed but before the funds are transferred, allowing them to manipulate the amount transferred.
Two Modes of Data Creation
1) Data created by users (specifically deliberately entering/uploading information)
2) Data Created by the system (ie the system is logging/monitoring user behavior)
Data Classification
(technically part of the data lifecycle that comes right before data storage)
Data needs to be given a classification as soon as possible to ensure that it is handeled or stored properly
Data Archival
Penultimate step in the data lifecycle
This is often required to comply with “data retention” laws
Defensible Data Destruction
Destroying Data in a way that complies with standards/regulations
Scoping a data-security baseline
Removal of baseline recommendations that do not apply
Three primary types of security controls
1) Preventative
2) Detective
3) Corrective
Preventive Security Controls
Act as a deterrent to an attack
Detective Security Controls
Help you identify when they Confidentiality/Integrity/Access of your data is compromised, as quickly as possible
Corrective Security Controls
Help you mitigate the effects of an attack
International Association of Privacy Professionals (IAPP)
Global organization dedicated to supporting professionals in the field of privacy and data protection. It provides resources, education, certification, networking opportunities, and advocacy for individuals and organizations involved in managing privacy risks and compliance with privacy laws and regulations.
Symmetric Cryptography v. Asymmetric Cryptography
Symmetric Cryptography:
- Uses a single secret key for both encryption and decryption.
Efficient and faster for processing large amounts of data.
- Key management is critical, and secure distribution of the key is essential.
- If the key is compromised, all encrypted data is at risk of decryption.
- Primarily used for encrypting bulk data like files and securing network communication.
- Speed and efficiency make it suitable for high-volume data encryption.
Asymmetric Cryptography:
- Uses a pair of keys: a public key for encryption and a private key for decryption.
- Slower and computationally more intensive compared to symmetric cryptography.
- Public key can be openly shared, but the private key must remain secret.
- Even with the public key, it is computationally infeasible to derive the private key.
- Key exchange, digital signatures, and secure communication are primary applications.
- Security relies on the complexity of mathematical problems and the secrecy of the private key.
Cryptography Schemes that can stand up to quantum-drive code breakers
Symmetric (shared key) cryptography schemes
The only exception is “Lattice”, which is the only asymmetric scheme that cannot be broken by a quantum computer
Keys in Cryptography
Just a piece of information that is used to control the transformation of plaintext (original, readable data) into ciphertext (encrypted, unintelligible data) during encryption, and vice versa during decryption. Keys are essential to ensuring the security and confidentiality of the data.