Are One in Three Breaches Really Caused by Unpatched Vulnerabilities?

Oli Thordarson, CEO of Alvaka Networks, begs to differ... This is an interesting article I read in ZDnet, Cybersecurity: One in three breaches are caused by unpatched vulnerabilities, about software vulnerability patching. I found it interesting because I took some [...]

Are One in Three Breaches Really Caused by Unpatched Vulnerabilities?2019-11-03T21:10:45-08:00

Software Patching Best Practices – 18 Must Do Tips

There are many other benefits to applying software patches including in some cases adding features, fixing bugs that make the software run slow or not work right.  All software needs to be patched. Whether the software sits on a disk and runs on a server, resides on a chip within a firewall, or is an app that is in your tablet devices, it all needs to periodically be updated and patched in order to be secure.

The following list of 18 software patching best practices is what we follow at Alvaka Networks when delivering on our Patchworx(SM) Patch Management Service.  It is important to note that all these steps are important, but not always are all them utilized or they can be utilized in different ways depending upon the needs of the client. Like us, you will need to decide what your patch management plan needs to look like to best suit your needs.

18 recommended best practices for patching your software:

Software Patching Best Practices – 18 Must Do Tips2019-08-15T15:47:58-08:00

Why are Patch Management and Change Management Important?

Alvaka Networks has arguably the best and most sophisticated patch management process in the Orange County, Los Angeles County and possibly the US.  Not many firms can deploy vast quantities of patches to valuable high availability servers and PCs with smoke testing qualify control while following the sun globally during selected narrow service windows.

Change Management
Change management is vital to every stage of the patch management process. As with all system modifications, patches and updates must be performed and tracked through the change management system. It is highly unlikely that an enterprise-scale patch management program can be successful without proper integration with the change management system and organization.

Like any environmental changes, patch application plans submitted through change management must have associated contingency and backout plans. What are the recovery plans if something goes wrong during or as a result of the application of a patch or update? Also, information on risk mitigation should be included in the change management solution. For example, how are desktop patches going to be phased and scheduled to prevent mass outages and support desk overload? Monitoring and acceptance plans should also be included in the change management process. How will updates be certified as successful? There should be specific milestones and acceptance criteria to guide the verification of the patches' success and to allow for the closure of the update in the change management system....

Why are Patch Management and Change Management Important?2019-08-15T15:50:03-08:00

The Java Vulnerability May Not Be Fixed; A Tale for Two Browsers

It has been suggested that this update does not end the problems for Java. In fact, some experts on Java are recommending that Java not be used unless necessary.  If you require Java, here are two suggestions: Turn Java on [...]

The Java Vulnerability May Not Be Fixed; A Tale for Two Browsers2013-01-16T16:38:59-08:00

Who Is Guilty In A Hack? The Perpetrator Or The Victim?

This article is interesting not because the hacker is convicted, but because of the reader comments at the end. The first post defends the hacker and blames AT&T for their system not being secure enough and allowing a breach. The next poster says that is akin to blaming a bank if they are robbed because their doors are not secure enough. Another poster points out that both are to blame.

Who Is Guilty In A Hack? The Perpetrator Or The Victim?2012-11-22T05:02:00-08:00