Originally published on June 19, 2017 on TechTarget. Alvaka’s COO and CISO, Kevin McDonald, examines the real-world damage caused by CIA and NSA data leaks, putting dangerous government cyberweapons in the hands of hackers. WikiLeaks' CIA data dump shook a [...]
And Why Executives Should Care... Threats to network security seem to get announced weekly. Global ransomware attacks like WannaCry cause havoc around the world and billions of dollars in losses. Businesses are actually shuttering due to network attacks that disable, [...]
I was stunned to learn that Aerojet, a division of Rocketdyne, set legal precedent three weeks ago in the Federal District Court for the Eastern District of California. The heart of the matter is an allegation that Aerojet made false [...]
Article originally posted on TechTarget. Alvaka's COO and CISO, Kevin McDonald, discusses the type of questions you should ask MSPs to ensure they have the correct security systems in place in order to protect your organization against outsourcing IT risks. [...]
A Timely Warning About Fake Communications and Persuasion Methods As many of us have experienced, there are people in the world who want to steal from us, our company or employer. In some cases, they want to pretend to be [...]
Blog written by Mimi Grant of ABL Organization. Originally published on April 3, 2019. Mimi discusses three common IT problems that physicians face and how to deal with them, including insights on ransomware attacks by Alvaka's CEO, Oli Thordarson. While [...]
Many organizations continue to find themselves between a rock and hard-place when it comes to consistently applying security updates or “patches” across their environments. On one hand, they recognize their unpatched software exposes them to risk of a disruptive and [...]
Today, industrial control system cybersecurity is mainly focused on securing networks, and efforts generally ignore process control equipment that is critical for plant safety and reliability, which leaves it woefully vulnerable. As the number and severity of attacks on our [...]
Warning!!! We have entered a new, even more malicious, era for ransomware that is hitting mid-market companies particularly hard. The two stories I share below are chilling… For the last five years or so, ransomware could be described as a [...]
Written by Kevin McDonald, COO and CISO of Alvaka Networks. Originally published December 2018 on TechTarget. Kevin explores what Moody's new cyber-risk ratings could mean for enterprises and the infosec industry. Having access to credit is critical for any healthy company, [...]
Smoke testing is a term used to describe the testing process for servers after patches are applied. The process typically involves making sure servers are rebooted in the right order, making sure they have completely rebooted, restarting applications in the right order, and then testing to be certain everything is working properly when users return to work in the morning.
This typically takes 30 minutes per server, depending upon your environment.
PCs are not typically smoke tested, or if so, not all of them.
Estimating an average time for patching servers and PCs can be a bit tricky. It can vary from one month to the next, depending upon the number and complexity of the patches released by your software vendors. You must consider all versions of operating systems and have a complete inventory of all your application software to do this job correctly. Our experience has shown that manual patching of systems takes on average of about 1.5 hours each.
There are many variables to consider. Some are:
You want to enter in a fully burdened labor rate for this field. What that means is that you want to take the base hourly rate, plus 25-30% for employer payroll taxes, benefits, vacation/holiday time, etc.
For example, someone making $80,000 per year will typically work 52 weeks of 40 hours, or 2080 hours. $80,000 divided by 2080 is $38.46/hour. Multiply that hourly rate by 1.3, and you get $50.00/hour. Of course, rates of pay, taxes and benefits will vary from city, state and company; but 30% is usually a good number to use. Don’t forget to account for time-and-a-half or after-hours rates of pay if patching is being done in the late evening, early morning, or weekends (in order to avoid impacting user productivity).
This is a basic cost calculator for you to compute your typical monthly cost for patching your servers, PCs, laptops, tablets and associated application software. It also forms the basis for you to begin calculating your Return on Investment for software patching, or for comparison with alternatives to the manual process of patching operating systems and application software—such as Patch Management as a Service, also known as Vulnerability Management as a Service.
If you are presenting to management for a budget, and using this calculator as the basis for a Return on Investment (ROI), you will need to do more homework. An ROI measures as a ratio of the cost of investment against its expected benefit. For patching, calculating benefit can be very difficult to determine. How do you measure the cost of a system breach you have not yet had? You can estimate what expenses, penalties, and losses a company might incur when a breach occurs; but there is no certainty of a breach event and what those costs actually are. There are also regulatory compliance issues and/or potential fines for not patching, but those, too, can be vague. For calculating these potential risks and costs, it is advisable to enter into a discussion with your management team.