Preventing Attacks

DevOps is the union of development, operations, and quality assurance -- but it's really the other way around.

As I write, we're in the midst of a big Ransomware attack. Millions of computers have been infected, with their data encrypted, held ransom pending an extortion payment or deleted. Supposedly.

Yesterday Amazon Web Services (AWS) had a major outage in their US-East datacenter, in Virgina. It made all sorts of national news, largely because it affected some major online services.

Richard asks:

Just a question after reading an article posted here back from January 21, 2016 on Drupal 8, why Freelock.com has not moved to Drupal 8?  Just wondering if there was a particular reason we should avoid before jumping in?  Thanks.

Yesterday the Drupal security team gave a dire warning about extremely dangerous security vulnerabilities in multiple contributed modules. The fixes, and the details, would be released at 9am Pacific Time today.

I'm sure many of you reading this may have heard that Drupal 8 has been released, may have even received some marketing emails.

Faster, more secure, more maintainable. Three nice benefits we get from our new standard Drupal server architecture.

We're starting to recommend Drupal 8 for some new upgrade projects, with the following notes...

Lately at Freelock, we've been improving our Drupal site assessment.

Apparently there's some FUD (Fear, Uncertainty and Doubt) being sown by a few Drupal shops who are spreading downright wrong information about Drupal 8, trying to encourage people to upgrade to 7 now.

Everybody is writing about Heartbleed this week. The reason? It probably affects more people than any other vulnerability we've ever seen. If you ever log into any web site, anywhere, your password might be revealed -- and that is just the start. The biggest problem?

It goes something like this:

(Client): I want to add a shopping cart to my site. I heard that xyz cart is free, can you add that for me?

(Developer): Sure! That looks easy.