Upgrading the virtual network to use NSX is not a heavy or large task. It can be, depending on what you are doing, but the basics are fairly straightforward. These basics are not the wholesale replacement of your existing virtual network. They are not the inclusion of new forms or routing in your virtual environment. The are the addition of NSX on top of what you already have. Once you have NSX in place, then you can dream, plan, and adopt those better ways of managing and creating virtual networks. Continue reading vSphere Upgrade Saga: NSX in 8 Easy Steps
I have been creating a security operations center (SOC) specific to VMware vSphere using VMware vRealize Log Insight (vRLI). This SOC project shows the power of vRLI and the wealth of data available within vSphere 6.5. The original goal was to just gain visibility into my own environment. However, after showing the simple views to a few folks, it has grown from there and continues to grow.
In previous Foray into Jenkins, Puppet, Docker, and Photon posts, I was able to clone a Photon OS VM (part 1), deploy a Docker container into the Photon OS VM (part 2), and do automated load testing (part 3). Now it is time to look at improving the security of my Git repository. Given the number of scripts out there to look through GitHub for API keys, usernames, and passwords in order to rack up serious bills on Amazon and other cloud services, it behooves us to be extra vigilant.
In previous Foray into Jenkins, Puppet, Docker, and Photon posts, I was able to clone a Photon OS VM (part 1) and deploy a Docker container into the Photon OS VM (part 2). Now, it is time to do some automated load testing in order to load and security test the deployed application. Load testing is required to determine the upper limit of the load this one container can handle. Once I know that, I can properly scale out the environment. But I also need to ensure that known security holes do not exist. Continue reading Foray into Jenkins, Docker, and Photon: Part 3
There are a number of interesting attacks out there, and one of them is related to Genericons, which are used by the Twenty Fourteen theme. There are also serious performance issues with Genericons, so dumping them is a good idea. Here is how I did that without using a child theme. My whole goal for using Twenty Fourteen was to modify it without using a child theme. Not that hard to do, but it does take some forethought. Here is how I achieved this bit of magic and boosted performance at the same time!
In WordPress Hacked: Security Steps Take II, I wrote about the tools and steps to take to secure your WordPress installation. The current steps to take are the same. The tools, however, have changed significantly. Even as the steps changed from WordPress Hacked: Security Steps, now we look at the tools once more. I will reiterate the steps at the end of the post for completeness. However, let us begin by examining the tools. I have removed quite a few from my installs that I had previously recommended, and I will explain why below. Continue reading WordPress Hacked: Security Steps and Cleanup Take III