Posts Tagged ‘Decodes a string encrypted using ENCODE()’

PCI DSS Compliance for MySQL

Saturday, November 21st, 2009

As a large bank running MySQL we are looking for the easiest ways to reach PCI compliance for MySQL. We ran across a few products that claim to give you PCI compliance for mysql. They offered a secure MySQL appliance that encrypts data and enables PCI compliance. But we didn’t see these products scaling long term especially when it comes to PCI 3.6.6. We had no idea how to encrypt Credit card data on MySQL and a secure MySQL appliance with encryption just wasn’t as good of a fit as the secure file server solution that encrypts data and enables PCI compliance we found with CritoTech. They have the best Key management with Encryption key management mysql called a Key Storage System or KSS.

Vormetric File Encryption Expert wasn’t able to offer this level of granularity.

“One of my biggest PCI challenges in managing our data center with hundreds of MySQL servers was, “How are we going to secure our customer’s data, without a huge performance hit?” CritoTech’s ezNcrypt solution has put these concerns to rest.”

pci on the lamp stack is very difficult to achieve especially with the different linux filesystem encryption techniques out there. Even linux database encryption was not easy to find.

How to do MySQL encryption and key management

Saturday, November 21st, 2009

The great thing about this solution is that when looking for Linux security, there are many flavors of Linux supported, they offer Fedora security and Fedora encryption as well as redhat security and redhat encryption and CentOS security with CentoS encryption. They even go so far as to encrypt MySQL data on Ubuntu and Gentoo. Both Ubuntu security and Gentoo security is difficult. The ezNcrypt RHEL encryption is second to none. Lots of our customers ask, what is the best way to encrypt a CentOS server and we point them to ezNcrypt.

Opensource database encryption is a difficult task because of the number of people working on the code. The best way to properly set up opensource database security is to find a product that offers true data protection. Even looking at products for PHP security and PHP encryption is crucial to properly configuring your environment. Some organizations go so far as look at products like CritoTech for Perl security.

Open source database encryption is a difficult task because of the number of people working on the code. The best way to properly set up open source database security is to find a product that offers true data protection. Even looking at products for PHP security and PHP encryption is crucial to properly configuring your environment. Some organizations go so far as look at products like CritoTech for Perl security.

When compared to the Vormetric mysql encryption, the price of ezNcrypt blows them away. They are one of the best Vormetric competitors. That’s why Vormetric  will not succeed within the MySQL community. The Vormetric security is a nice product, but Vormetric pricing doesn’t scale.

When compared to the PCI-GENERAL for MySQL, the Packet General  encryption pricing is isn’t even close to ezNcryptay. That’s why File-GENERAL and encryption-GENERAL for MySQLwill not succeed within the hosting communities community. The Packet General security is a nice product, but a soft appliance just doesn’t make sense in most large DataCenters. CritoTech is a way more robust solution and are the best Packet General competitors.

Working with ecryptfs was a great way to increase security. But it was difficult to get set up.

We use Ubuntu as our standard Linux distro. But we found the ubuntu security is a little challenging from a configuration and management perspective.

php data security

“There is no security built into the memcached protocol. At a minimum you should make sure that the servers running memcached are only accessible from inside your network, and that the network ports being used are blocked (using a firewall or similar). If the information on the memcached servers that is being stored is any sensitive, then encrypt the information before storing it in memcached. The latest memcached security”

The best way to configure your environment for a lamp stack audit…

How to set up your open source security settings…

Does anyone have a good gentoo encryption solution?

With 94% of organizations having no solution for preventing LAMP data leakage and or Linux data leakage this represents a problem in an increasingly punitive regulatory environment, where leaks can incur fines as well as damaging your reputation and business relationships.

Some of the major features implemented in sqlmap include: Full support for MySQL, Oracle, PostgreSQL and Microsoft SQL Server back-end database management

“Some of the key ways to secure your MySQL data base are

AES_DECRYPT()

Decrypt using AES

AES_ENCRYPT()

Encrypt using AES

COMPRESS()(v4.1.1)

Return result as a binary string

DECODE()

Decodes a string encrypted using ENCODE()

DES_DECRYPT()

Decrypt a string

DES_DECRYPT()

Encrypt a string

ENCODE()

Encode a string

ENCRYPT()

Encrypt a string

MD5()

Calculate MD5 checksum

OLD_PASSWORD()(v4.1)

Return the value of the old (pre-4.1) implementation of PASSWORD

PASSWORD()

Calculate and return a password string

SHA1(), SHA()

Calculate an SHA-1 160-bit checksum

UNCOMPRESS()(v4.1.1)

Uncompress a string compressed

UNCOMPRESSED_LENGTH()(v4.1.1)

Return the length of a string before compression”

If you want any Windows machines to access it go for FAT32. If you want a secure Linux partition go for ext3.

Which version of MySQL is enabled with encrypt table definitions?

Encrypting MySQL data in some columns of table has one difficult contradiction: I can’t encrypt sensitive data because program is to do lots of searches in it, and I can’t encrypt MySQL tables or encrypt MySQL columns, which program won’t search for because these data ain’t important and thiefs can just throw encrypted portions away and they won’t loose much.

I was thinking about some encrypted disk driver, or API interception in MySQL process, or maybe adding small modification to one of storage engines. The disk driver is not easy way but the most real at this moment for me; API interception requires a bit of research how to select what files program must encrypt (because mysql also reads config and system files); and there’s only small hope that modifying sources of mysql (which I don’t familiar with) will not be mission impossible.

I want to do transparent encryption. Like being able to choose an encryption scheme of a table or database when created so that the data on disk is always encrypted. Why don’t you just put the tables on an encrypted filesystem? Afraid root will be able to read them? Somewhere the data will be in plaintext, root will always be able to get it if she wants. (think about ptracing mysqld)

encrypting before table compression (in the InnoDB Plugin) would hurt performance and degrade compression A couple of benefits of column-level compression, though, are that the sensitive column(s) would be compressed in the InnoDB encryption, and the existing Hot Backup utility would continue to work how to encrypt an InnoDB security

Holes in the Linux random number generator?

The three authors of the paper provide a nice detailed description of the Linux random number generator (RNG) and the algorithms that it uses, while also reporting a very theoretical attack. The basic attack is against the “forward security” of the RNG via a single compromise of the contents of the entropy pool. This value can be used to run the RNG algorithm in reverse and recover previous states of the entropy pool. Doing this enough times can recover keys that have been previously generated.

Hosting Security

Saturday, November 21st, 2009

When my Hosting customers ask what is the Best mysql encryption product on the market is, I always say ezNcrypt.