PostgreSQL Secured by SG

The PostgreSQL Secured by SG  is a ready-to-deploy Shielded PostgreSQL Server instance designed to eliminate the need to build a patchwork security solution in order to protect the PostgreSQL data. Our VM uses advanced security techniques such as secure boot, vTPM, UEFI firmware, integrity monitoring at the virtualization layer and transparent encryption, extended access controls, tamper-resistant logs at the data layer in order to protect PostgreSQL data against unauthorized access. All Server General operations are logged on four different servers making it very challenging for an attacker to successfully launch a log tampering attack. You can deploy our PostgreSQL Secured by SG  instance in less than 10 minutes. Our automated scripts will install and configure the instance to provide you maximum security and performance. The PostgreSQL Secured by SG can enable you to achieve regulatory compliance without having to create a patchwork of security solutions. 

Server General solutions are trusted by some of the leading organizations based in the United States, Europe, and Japan to protect their data and to meet stringent data security requirements imposed by

Main Features

Reduced Attack Surface
The Operating System vendors design their products to support numerous applications to increase their usage. However, this approach results in a bloated operating system unfit to host any mission-critical application server securely. The PostgreSQL Secured by SG instance uses a trimmed down version of the OS thereby reducing the attack surface significantly. The entire footprint of our image is around 850MB.
Tamper-resistant Logs
Our secure instances log Server General activities at four separate locations (real-time). Even the administrators are unable to alter all four copies since three copies are stored outside of their administrative control. This essentially nullifies log tampering attempts. Most auditors appreciate this approach.
Protection Against Unauthorized Users
Off-the-shelf operating systems have a flawed notion of trust - the privileged user is implicitly trusted. This leads to a variety of security problems. Many attempts have been made to fix this issue including one within a topnotch United States military agency. However, these solutions have proven impractical for general business use. We use advanced access control measures that make it difficult for unauthorized users, including the “root” user, from accessing the protected data sets. The Server General trust model doesn’t include the traditional privileged user. Thus, the privileged user is not allowed to view data stored in a secure repository. We are quite aware of the fact that given enough time and money a motivated attacker can get around our controls but we are raising the bar for an attacker.
Transparent Encryption
The usual approach to data encryption within a cloud platform is to use a block-level encryption. It may allow you to get data encryption off your to-do list, however, such ad-hoc approaches do not fully address the need for data security. We make use of the encryption capability that is built into the Linux kernel to transparently encrypt data and extend the POSIX based access controls. Our implementation requires no changes to be made to the PostgreSQL client applications.
Virtual Instance Security
The instance uses "Secure Boot" to make sure that only authenticated software is installed at the OS layer.
Transitive Trust Model
We extend the transitive trust from OS the layer to the PostgreSQL server and to data it generates. We ensure that an authenticated PostgreSQL binary is running on our instance and we compute digital signatures when data is stored or retrieved from the disk in order to guarantee that the data has not changed while it was sitting on the disk.
Based On Open-Source
MySQL Secured By SG uses standard encryption functionality embedded within the mainstream Linux kernel. This functionality is based on a stackable file system that was developed by Erez Zadok, CTO, Server General Inc.
Role-Based Management
Many solutions cling to old security concepts that result in misplaced trust in the network/system administrator. This completely defies application’s access control logic as intended by the application vendor thereby exposing the application data to a whole host of attacks. MySQL Secured by SG segregates management responsibilities based on roles in order to safeguard data.
Integrity Monitoring
Remote attacks, privilege escalation and insider attacks are prevented with help of integrity monitoring.

How Does it Work?

  • Select Instance Type
    Change machine configuration
  • Install Instance
    Install your instance
  • Run Script
    License your instance
    Configure administrators
    Define a security policy
    Encrypt MySQL data
    Control access
  • Manage Your Instance
    Change temporary passphrases
    Start/Stop the security policy
    Rotate data encryption keys
  • Logs
    Server General administrative logs are stored locally and at three other servers
  • That’s It
    Your PostgreSQL is fully protected now.


The core components of MySQL Secured By SG are a data encryption engine, a key management engine, an access control engine, and a reporting engine. Each component performs a critical function in securing sensitive information and collectively they provide active countermeasures against various types of attack vectors.

A high-performance Data Encryption Engine is employed to provide strong encryption for all writes, and decryption for all reads. The application server data is encrypted at the file-system layer using the AES algorithm. This in- kernel data encryption is quick, transparent and you control the data encryption keys while we help you manage them.

Data encryption  protects against theft of media, data images – even if intruders are able to obtain physical or electronic copies of data. The stolen data would be unusable without the decryption keys. Any probing of files would only yield blocks of ciphertext. 

The Key Management Engine allows our customers to control their own encryption keys at all times. The encryption keys are stored in one or more key lockers deployed within the Server General global key management infrastructure. The encryption keys are themselves wrapped in another layer of encryption using a master key (a passphrase) that is only known to the data owner. This way only cipher blobs are stored in key lockers preventing other parties from deciphering them. The key management system allows customers to generate strong keys, rotate them on-demand, revoke any key at any time and store them in a secure location. Our security staff ensures their availability.

The Access Control Engine provides industrial strength identification and authentication mechanism that results in reduction of the ‘trust domain’. Only authorized Server General administrators are able to access administrative functions: this one measure reduces the risk posed by rogue systems administrators (or any other entity that has progressed beyond perimeter security). The access control engine allows only authorized users to access the protected data sets.

The Logging Engine logs every administrative operation related to Server General. The logs are stored at four different locations - on the host server and remotely within our cloud infrastructure. These logs provide crucial information during a security audit. In case of a regular server, an external or a malicious internal user may gain unauthorized access to the sensitive data – then perform acts to conceal the breach by removing or editing audit logs. However, this is not possible with Server General, as logs are stored outside the administrative domain of the compromised entity.

Data Security

VM Security

Start today

PostgreSQL Secured by SG