I’ve been asked a few times now if there is a way to use encrypted MySQL connections in Magento. Most of the time it is when merchants are selling medical products and HIPAA requirements come into play. I am not an expert in HIPAA, nor do I want to be, but with the cost of vulnerabilities on the rise it made sense to at least look into it and get a good answer on how to do it.
I saw a tweet today concerning authentication. Monaco, at White House cybersecurity summit at Stanford, calls for replacing passwords with more secure technologies. — Paul Krill (@pjkrill) February 13, 2015 When reading that the first thing that came to my mind was “with what?” When will that one be hacked and then replaced by something else, which will then be hacked and replaced by something else? For all of its faults a good password is already stored in the most secure storage repository around; your brain. The problem, however, is that
I read a post tweeted by Chris Cornutt today. The basic gist of the article is that your security is only as strong as your most ethically-challenged developer. That got me thinking that we spend so much time trying to prevent intrusions when detection might be a better priority. Some tactics, such as SQL Injection, are useful because they protect not just against intruders but people who tend towards single-quote usage as well. I would argue that SQL Injection is just as much about inadvertent data entry as it is
Found this list of things “to do” on Twitter this morning. I went over the list and saw that there was one item that was missing, which I feel is very important to do. I saw it in another post on Local File Inclusion for which it seems like there was a local file inclusion vulnerability in Joomla (I think. I didn’t read that far into it). The thing on the list that was missing was securing your local file system when installing Magento. The default installation asks for certain
I don’t talk much about security. This is mostly because it’s such a moving target. I’m also horrified that I might give bad advice and someone will be hacked because of me. But in researching the second edition for the IBM i Programmer’s Guide to PHP Jeff and I decided to include a chapter on security since we really didn’t talk much about it in the first edition. I’m talking about cross site request forgeries right now and I wanted to make sure that what I was going to suggest
Chris Dale recently posted a horrifying article on his blog. It is called “Why it’s easy being a hacker – A SQL injection case study“. The most horrifying part of the post was that when you type in the Google search “How to use PHP with MySQL” a significant number of the results come back with some VERY poor examples. Most of them were vulnerable to SQL injection. That means that people new to PHP are getting really, really bad advice on how to connect to the database. With that
A little while ago I had come upon the problem of having to store sensitive data in a user session. The solution that I (and several others came upon) was creating a mechanism for storing encrypted data in a session. But what we wanted to do was build something that didn’t have a single point of failure. We also wanted to build something portable. What we built was a simple Zend Framework session handler for storing sensitive data.