Skip to main content

New year, New Vulnerabilities, Old problem...

Happy New Year to everyone! May 2018 provide you with interesting problems and the patience to solve them :)
On to the recent kerfuffle about the Intel processor bugs.

 These vulnerabilities were identified in early January by Google 
(original Google security post) 

 CVE-2017-5715 
CVE-2017-5753
CVE-2017-5754

 These vulnerabilities have been named "Spectre" and "Meltdown" and are causing a certain amount of anxiety in some environments. 
IBM has produced an excellent write up of the vulnerabilities and includes information about the impacts and includes the CVE ratings:

 https://exchange.xforce.ibmcloud.com/collection/c422fb7c4f08a679812cf1190db15441
Of course new vulnerabilities are bad, and often require work and remediation, but this should be part of your environment's standard vulnerability assessment and remediation program. It's not sufficient to just apply patches from a single vendor (e.g. Microsoft) on a monthly basis and consider the job "done". 

 You need to understand your environment's exposure to all vendors and technologies (hardware and software) and the monitor for new vulnerabilities, and have an internal process for reviewing and assessing the impact of these vulnerabilities. This assessment should then lead to validation via scanning or inventory, and then remediation (based on the risk level identified during the assessment and taking other controls and work arounds into consideration).

 This all flows nicely into the recommended controls that you should have in place from the first five of the CIS Critical Controls V 6.1
https://www.cisecurity.org/controls/

 If your organization is "freaked out" about these new vulnerabilities, you might want to consider developing a more standardized or formalized approach for these controls.

Comments

Post a Comment

Popular posts from this blog

Requirements for Information Security

If you want to get into Information Security you HAVE to be a/have this skill... Why this is total BS. Almost daily I see someone posting on twitter, trying to be helpful to folks who are looking to get into InfoSec. Often I see "If you want to be in Information Security (Cyber Security) then you HAVE to be a programmer" or "If you want to be successful you have to be a hacker/have a criminal record/have abused systems without permission" etc. While having technical capabilities (such as programming) and having the ability to compromise a system shows a specific skillset neither are required. When talking to people who are interested in Information Security I often refer to it as a cake, there are tons of slices, many flavors, many pieces and parts you can sample, choose to focus on, will be expected to know something about, etc. Incident Response and Forensics (my current focus) is not the only part of Information Security, and certainly not the only part tha...
Post a Comment
Read more

Privacy considerations for home users

In light of the recent new stories regarding the recently signed legislation allowing ISP's to be able to sell your data http://www.vox.com/new-money/2017/3/29/15107110/republican-isp-data-privacy Here are a couple ideas and tips about privacy in general. Don't panic - a lot of the info was already being gathered, this isn't that large of a change regarding scope, it's more of a change to who can profit or sell it (which is a shift for sure). Remember a lot of the services you use today already gather your browser, activity, and search info (google, bing, yahoo, facebook, etc.). ISP's haven't implemented this yet, expect to see new terms of service in an upcoming bill, or an email sent to you, etc. If you would like to take some steps to try to preserve your privacy, here are some ideas and examples: VPN (Virtual Private Network) - this in essence creates an encrypted tunnel between two points on the Internet. One point being your system...
Post a Comment
Read more
Weekly recap and why you should be concerned about "attackers" even if you have "nothing to hide" Why you should be aware of, defend against, and prevent attackers... even at home: I often hear from future victims "well I don't have anything to hide/anything of value/why would they target me!?" It's really not about you, usually the attackers aren't looking for your data (if they get it, or have easy access to it, they may try to profit from it, but the people doing the compromising aren't usually the same folks that monetize). What the attackers want are compromised systems they can use to do what they want at scale. So if they can compromise 50 systems, they can send 50X the amount of SPAM... 100 systems, 100X, etc. Some operations get paid based on the number of emails they can send per day. Of course the email will likely not just be SPAM, but may also be malicious (ransomware, etc.). http://thehackernews.com/2017/09/linux-ma...
Post a Comment
Read more