There are a lot of people who are familiar with a relational database and it is widely known under many guises in several different ways. Essentially it is data which is stored in delimited text files, also known as flat files.
For example, school records could be allowed to store details regarding everything from students to rows of benches to teachers with just a simple comma separating the various bits of data. Yet in a relational database, the columns signify attributes and the rows are considered to be tuples - each representing an object and the attribute values of that object.
An important factor of a relational database is that the order of the tuples and those of the attributes have no bearing on each other. One of the most crucial aspects of keeping database records secure is by limiting access to the database altogether. It is possible to ensure that only the particular authorised programs have access to the data and can be done in a number of ways.
Firstly, a database with sensitive information does not require being on a public server. This is because it can be put on a private network with requisite security controls. The database can also be programmed to respond to demands that are only from the authorised entity, therefore reducing chances of even being able to see the database. There are several levels of restriction and access control that can be configured by ensuring that even the server itself is protected. This is done by means of row-level security. This needs strict programming, and great teamwork between all elements of the IT infrastructure.
Row-level security restricts the access to the data by row. This means that if for any reason a user wants to have the chance of accessing data from a specific tuple, their credentials must match the ones stored in the row itself. This type of security is often implemented through the use of virtual private databases.
For example, school records could be allowed to store details regarding everything from students to rows of benches to teachers with just a simple comma separating the various bits of data. Yet in a relational database, the columns signify attributes and the rows are considered to be tuples - each representing an object and the attribute values of that object.
An important factor of a relational database is that the order of the tuples and those of the attributes have no bearing on each other. One of the most crucial aspects of keeping database records secure is by limiting access to the database altogether. It is possible to ensure that only the particular authorised programs have access to the data and can be done in a number of ways.
Firstly, a database with sensitive information does not require being on a public server. This is because it can be put on a private network with requisite security controls. The database can also be programmed to respond to demands that are only from the authorised entity, therefore reducing chances of even being able to see the database. There are several levels of restriction and access control that can be configured by ensuring that even the server itself is protected. This is done by means of row-level security. This needs strict programming, and great teamwork between all elements of the IT infrastructure.
Row-level security restricts the access to the data by row. This means that if for any reason a user wants to have the chance of accessing data from a specific tuple, their credentials must match the ones stored in the row itself. This type of security is often implemented through the use of virtual private databases.
