Oracle Database Masking and Security Management Application

Oracle Database Masking and Security Management Application

Institutions and companies take measures by configuring a firewall in the network against accesses and attacks from the Internet to protect their corporate data. However, measures for database security, which is the most important part of the internal security of the institution, need to be taken separately.

Beside the attackers, business and data losses occur due to security violations such as curiosity and sehven erroneous transactions, difficulties in complying with the regulations, difficulties in establishing security due to the database architecture, and preventing unauthorized access to the database.

For Oracle, it is possible to perform anonymization in accordance with both the security and audit system software and the Personal Data Protection Act No. 6698. With this new generation advanced product, compliance with regulations is ensured easily, and database security and inspection is performed effectively without any service.

infoFence is a new generation of advanced security and auditing software that works in an Oracle database environment.

Link Control
DDL / DCL Control
DML / INSERT Auditing
Database and Application Error Detection System
Custom Table Access Logging System
ISO-27001 Reporting
Oracle (10g, 11g and 12c) works as a product within the database, integrating with Database Triggers and Oracle Database Vault Option.

infoFence is a database that identifies users without changing any settings, distinguishes the same database users from their session information, enables them to work with different authorities, and controls their connections.

Maximum Security
infoFence is a security layer in Oracle databases.
All users connected to the database are identified with session information and re-authorized without changing existing oracle authorities.
With infoFence, users' access, definition changes, queries and data changes are easily controlled.
It allows analysis and logging with listening mode before blocking. In this way, uninterrupted operation of the production database is ensured.
infoFence naturally closes database security vulnerabilities and hidden backdoors.

Segregation of Duties
The infoFence Security Administrator limits the privileges of database administrators (DBAs).
Database administrators can be given different powers without being in the responsibility of each other. Access to critical data is blocked.

Link Control
If the user knows the database password, it can not be linked to the database if it is not authorized from infoFence.
DBS and even the most powerful user SYS (as sysdba) can not be attached to the database if infoFence is not authorized. There is no authorization from DBA and SYS for this.

DDL / DCL Control
DDL / DCL commands such as ALTER, DROP, CREATE, GRANT, REVOKE can be executed differently with infoFence
It is done within the authorities.
Even the most powerful user SYS (as SYSDBA) can not do DDL / DCL interception at all if not authorized from infoFence.
All DDL / DCL transactions are logged in the database, kept in source code history.
Database schema and objects are protected against DDL / DCL operations when requested.

DML / INSERT Auditing
Critical data is now relieved. DBAs and even the most powerful user of the Oracle database, SYS, are prevented from viewing and changing critical data. Unauthorized attempts are recorded.
In the database, INSERT, UPDATE, DELETE / TRUNCATE and SELECT operations are prevented, masked or dimmed (Redaction) in the tables specified by the users.
To analyze the present, the table to be rejected is first defined in the LISTENING mode. It is then passed to the SECURITY mode to enable blocking.

Error Detection Detector
Errors occurring in the Oracle database appear in the alertSID.log file. Both application and database errors working in the database are detected and logged with infoFence.
Whichever program is on which program, what error is taken is kept.
When database faults and application faults occur, automatic faults are enabled from infoFence if defined.
The user can write his own custom PL / SQL code to work on alarms. For example, automatic e-mail may be discarded if the table or view can not be found (ORA-00942).

logging description
Connection attempts, DDL, DCL, DML, SORGU access operations and error detection status are logged.
Optionally, table accesses of users are optionally logged. For example, table accesses of users connected directly to the database can be logged, and users from the Application server can not be logged.
There is checksum control in connection attempt and DDL / DCL operation logs. Encrypted states of logs are also stored.

LDAP OID Support
A user defined in Oracle Internet Directory (OID) can connect to the database using Enterprise User Security (EUS). At the user's infoFENCE