An Effective Proprietary Database Firewall Based on DBTwin Active-active Database Cluster

An Effective ProprietaryDatabase Firewall

Based on DBTwin Active-active Database

Cluster

Version 1.1

A powerful tool for preventing ransomware, other viruses and Trojans

The current rampant ransomware poses a serious threat to the

database systems of a large number of users. Once infected,

the database system will immediately crash and data cannot be

restored unless the extorted transfers money to the extortionist

to purchase decryption keys or uses backups for recovery. The

best way to avoid this type of virus is to proactively prevent it.

In addition to common firewalls and antivirus software, it is also

necessary to promptly apply patch packages provided by

operating system and database manufacturers. In addition, it is

necessary to do a good job in backing up the database system.

However, these methods are not only tedious and laborious, but

also ineffective. It is very often to hear news that a certain

company has been hit by ransomware again.

In response to this demand, our company provides another

unique and effective solution to prevent ransomware: using the

gateway of DBTwin active-active database cluster, combined with

the built-in firewall of Windows, to achieve a unique database

specific firewall function, 'physically isolating' the client's SQL

Server nodes, thereby preventing and isolating viruses and

Trojans, and avoiding significant damage to the database systems.

The working structure diagram is as follows.

Pic 1 Integrated with proprietary database firewall and active-active functions

Overview of Working Principle

By utilizing the built-in firewall technology of Windows, the two

database nodes are hidden behind the DBTwin gateway machine.

Except for a few machines with specific ip address, all access to

the database nodes must go through the DBTwin gateway and

cannot directly access the two database nodes in the cluster. In

this way, the two database nodes are physically isolated, and the

DBTwin gateway machine itself is also protected by the Windows

firewall, leaving only some specific ports for database access and

allowing one or two client machines to access for managing and

maintaining the cluster. That is to say, it is possible to further

infect and attack the database machines behind the gateway only

after the DBTwin gateway machine is infected with a virus or

Trojan (this probability is almost zero), which greatly reduces

the probability of infecting the database systems. Otherwise, if

the database nodes can be accessed by any client machine in

the intranet of the company, hundreds, even thousands of

computers on the intranet, whether pcs or servers, will pose a

great threat to the database machine as long as any one of them

is infected with a virus or Trojan, not to mention that some clients

will directly expose the database ip and port on the Internet.

If you have any interest, you are welcome to contact us:

https://www.zhetides.com