Summarize database table names

Question

We are going to go through a project where we will process highly sensitive data. Besides data encryption, I was thinking about obfuscating table names.

So, it tEmployeeswill become t58633B7A, for example. Would it be useful to add? after all, it's about creating security / prevention levels.

PS We will compare the names of the confusing tables with the real names in our Data Access Level

Answer 1

It seems completely redundant. If an attacker gained access to the database simply by not knowing the name of the table, this is a little protection in the great scheme of things. You should spend your time, if anything, on better intrusion detection and defense mechanisms.

Answer 2

Although you will hear over and over again that security through obscurity is bad, it helps raise the bar of attack, as long as you remember that this is not a solution.

In your particular case, I would say that the costs of maintaining, debugging, troubleshooting in your database will outweigh the benefits of a tiny amount of perceived security.

Answer 3

.

, ... , , TheDailyWTF.

Answer 4

, . - , , , .

Answer 5

PowerDesigner. ( , PDM), . Readable field, .

, EMPLOYEE ( table_1) :

    NAME     CODE     DATA TYPE
    ID       F1       INTEGER
    NAME     F2       VARCHAR(50)
    DOB      F3       DATE

SQLServer ( script Generate Database Menu)

CREATE TABLE table_1(
f1 int,
f2 varchar(50),
f3 date);

CREATE VIEW EMPLOYEE WITH ENCRYPTION
AS  
SELECT f1 ID,f2 NAME ,f3 DOB 
FROM table_1

WITH ENCRYPTION SQL-, .

EMPLOYEE table_1

:

insert into EMPLOYEE values('1','kevin','1972/11/24'); 
insert into EMPLOYEE values('2','ted sulivan','1969/06/12');
insert into EMPLOYEE values('3','wei meng lee','1974/04/17');

SELECT * FROM EMPLOYEE;

(. http://blog.sqlauthority.com/2009/04/28/sql-server-introduction-to-sql-server-encryption-and-symmetric-key-encryption-tutorial-with-script/)
, , , .
, , , PDM.
, . , , .