The Overview of Data Integrity
HI Hi, Greetings! 
Festival April 
Today, I would like to share with you an article about the overview of Data Integrity. I hope this article has support for a security consultant. Let's move to the article and I will explain part by part.
PART 01:
Introduction of Data Integrity
Data integrity refers to the quality and consistency (validity) of data throughout its lifecycle. After all, organizations have little use for compromised data, let alone the hazards associated with sensitive data loss. As a result, many business security solutions place a high focus on data integrity.
The integrity of data can be harmed in a variety of ways. Data should be duplicated or moved in such a way that it is unaffected by subsequent changes. Error checking methods and validation procedures are often employed to preserve the integrity of data that is transferred or reproduced without the intent of tampering.
There are two approaches to data integrity. The phrase data integrity is also ambiguous because it can refer to either a state or a process.
Data Integrity as a state
If your data set is 'valid' and 'correct' at a given point in time, it is in this condition.
Data Integrity as a process
It's also an information security procedure, and it's about putting in place effective measures, restrictions, and best practices with the goal of assuring the 'validity' and 'accuracy' of a data set, or all data contained in a database, or data in other forms or structures, throughout their existence.
Data Integrity for databases
Data integrity, in its broadest definition, is a word used to describe the health and upkeep of any digital data. Many people associate the term with database management. In databases, there are four types of data integrity.
Entity Integrity:
There are columns, rows, and tables in a database. These elements should be as numerous as necessary for the data to be accurate in a primary key, but not more than that. None of these components should be identical, nor should any of them be null. A database of employees, for example, should have primary key data such as their name and a unique "employee number."
Referential Integrity:
In a database, a foreign key is a second table that can refer to a primary key table. Foreign keys are used to link data that is either shared or null. Employees may, for example, have the same job title or work in the same department.
Domain Integrity:
In a database, all categories and values, including nulls (e.g., N/A), are set. The usual techniques to input and read data in a database are referred to as domain integrity. Three decimal places will not be allowed in a database that contains monetary values such as dollars and cents.
User-Defined Integrity:
Outside of entity, referential, and domain integrity, there are collections of data created by users. This data would be categorized as "user-defined" if an employer created a column to input employee corrective action.
You are welcome to like and leave feedback in the comment area.
Link:
PART 02:
PART 03:
PART 04:
Source:
https://phoenixnap.com/blog/what-data-integrity
https://www.varonis.com/blog/data-integrity
https://heimdalsecurity.com/blog/data-integrity/
M M Zaheer Hussain
Stay Safe!
