Posts

Showing posts with the label pci

RDP SSL Causes PCI Compliance to fail

Found another issue crop up with a firewall rule change that opened up and RDP availability RDP should be configured using strong encryption methods or use SSL as the privacy and integrity provider. To configure RDP encryption methods, launched in mmc.exe to run the  'Terminal Services Configuration' or 'Remote Desktop Session Host Configuration' snap-in. The 'Terminal Services Configuration' or 'Remote Desktop Session Host Configuration' properties dialog box General tab for the Encryption Level 'High' should be selected. See more here for Windows 2008 R2 basically Start> Administrative Tools> Remote Desktop Services> Remote Desktop Session Host Configuration Click on Connection Click General Tab Change Security FROM Negotiate to SSL(TLS 1.0) Click Encryption Level to “High” A restart may be required (hopefully you won't get kicked out)

How should I improve my funnel and which colors are best for conversion?

With reference to the following articles on conversionxl: http://conversionxl.com/which-color-converts-the-best/ http://conversionxl.com/ux-hacks-to-increase-revenue/  While it is not necessarily about whether Red is best or Green or Orange, it highlights that Call to action is more important than a colour A color is more important than having none From experience, I'd have to say if you can split test different colors separately to a different design then you will be able to choose colors you like ! With the improving of a checkout purchase funnel, it is fairly standard fair: Save Orders  Save Customers (though don't "make them" create an account - https://www.youtube.com/watch?v=3Sk7cOqB9Dk Save Credit Cards (be aware of your PCI requirements) Don't have cryptic error messages (break it down, is it wrong, invalid, unkown) Layout the screen in an appropriate manner for different devices (responsive is clear the best design pattern here).  Ma...

Ghost Records, Card Recon and PCI Compliance

As part of a PCI Compliance audit, I recently ran a scan on a database using software call Card Recon. A little odd thing occurred. At a point in the past, a row of data in a column, which had been dropped from the database schema, contained a single test credit card number. However, the Card Recon software showed that the data was still there in the database file (this was a SQL Database) in the form of a SQL Ghost Record. A Ghost Record can appear when running a delete or insert command and when running delete and insert in different queries but related by the same indexed data, you can read all about it over at Ghost "Rows" Buster in  SQL Server on Technet. It's basically a record somewhere in the database file, but not directly in a database table and is living in a bit of spare fragmented space somewhere and this needs to be cleaned up. Following this procedure managed to remove the Ghost Record: Convert the database to Simple (only so the transactio...

PCI Compliance, SSL, TLS and Crypto

 Poodle and SSL 3.0, TLS 1.2  In order to fix the Poodle issue; SSL 3.0 needs to be disabled. You'll loose an odd ancient Browser or 2 but it's just not worth it. FYi, this also enables TLS 1.2 and 1.1. Other protocols that should not be round are PCT 1.0 and SSL 2.0 Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\PCT 1.0] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\PCT 1.0\Server] "DisabledByDefault"=dword:00000001 "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client] "DisabledByDefault"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentContr...