![\"week\"](\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2014\/05\/05111245\/week1-1.jpg\")
<\/a><\/p>\nPoints-of-Sale<\/b><\/p>\n
Point-of-sale\u2013or PoS\u2013is just a fancy name for a cash register. Of course, we aren\u2019t talking about old-timey, bell ringing cash registers. We\u2019re talking about connected, electronic sale terminals that store and pass along payment information. A PoS system of one kind or another is present in nearly every retail location or restaurant that accepts debit or credit cards. Unfortunately, a new report finds that these systems, on which many of us very regularly conduct financial transactions, are facing an increasingly complex array of attacks<\/a>. Worse yet, most of them do not offer much in the way of security protections.<\/p>\n This reality really isn\u2019t all that surprising, given that a compromised PoS terminal could potentially yield all pertinent payment information about any credit or debit card processed in a transaction on that machine.<\/p>\n A recent Arbor Networks report named at least five separate pieces of malware designed exclusively for the purpose of attacking PoS systems. Furthermore, the Verizon data breach investigation report<\/a> noted there were 198 distinct PoS intrusions in 2013. Also, in case you were wondering, recent attacks on Target, Nieman Marcus, Michael\u2019s and other retailers were all PoS attacks and all spilt substantial consumer data.<\/p>\n What can you do about it? Well, you could burn all your credit and debit cards and conduct only cash transactions until this whole \u201cInternet\u201d thing blows over. That\u2019s pretty extreme, though. Your best course of action is to pay attention to the news and act fast when you hear about a breach at a company you\u2019ve patronized. You\u2019ll want to check your credit or debit card balances to make sure nothing is amiss and also contact your bank to cancel any potentially exposed cards and replace them with new ones.<\/p>\n Bitly Broken<\/b><\/p>\n The popular link shortening service Bitly was compromised late last week<\/a>. This means if you have or ever had a Bitly account, then you should consider the password you used for that account exposed. While the company believes that no user-accounts were or are at risk, it is still urging its customers to change their passwords. Bitly has also announced<\/a> that it is implementing two-factor authentication<\/a> as a result of the breach.<\/p>\n I will also urge you to change your Bitly account password if you have one. If you happened to use that same password for other accounts, then you are going to want to change the passwords for those services as well, which is why you should never use the same password on multiple accounts.<\/p>\n One last thing to point out, Bitly allows its users to link their Bitly account with their Facebook and Twitter accounts. This could have been problematic\u2013allowing an attacker with access to your Bitly account potential access to your social accounts as well, but Bitly smartly invalidated all of those connections. You will have to re-authenticate those connections if you would like to reconnect the accounts. Unfortunately, you will also want to change the password for any social account you had linked with Bitly.<\/p> Make sure you\u2019re up-to-date with the latest versions of your Microsoft and Adobe software and Chrome, too.<\/p>Tweet<\/a><\/blockquote>\n Patch Tuesday<\/b><\/p>\n Briefly, Patch Tuesday was this week, which means fixes for Adobe\u2019s and Microsoft\u2019s ubiquitous products, as well as patches for Google Chrome. Microsoft issued eight security bulletins<\/a>\u2013of which two were critical\u2013fixing some 13 security vulnerabilities in its Internet Explorer Web browser and more in its other software. Adobe fixed some critical bugs in its Reader, Acrobat, and Flash players. Google fixed three highly rated security vulnerabilities in its Chrome browser<\/a> (and paid $4500 to the researchers that found and reported the bugs).<\/p>\n While we\u2019re at it, in the off chance that you want to get into some real insider-baseball stuff, we may as well mention that there was a fix for a five-year-old vulnerability in the Linux kernel<\/a> and also a couple patches for some Yokogawa industrial infrastructure gear<\/a>.<\/p>\n Make sure you\u2019re up-to-date with the latest versions of your Microsoft and Adobe software and Chrome, too. You should also check on your Yokogawa systems and Linux distributions if you are into that sort of stuff.<\/p>\n","protected":false},"excerpt":{"rendered":" Bitly was compromised this week and is urging users to change passwords. Point-of-sale systems are poorly secured. And fixes from Microsoft on Patch Tuesday.<\/p>\n","protected":false},"author":42,"featured_media":3353,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[5],"tags":[632,543,97],"class_list":{"0":"post-3352","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-news","8":"tag-bitly","9":"tag-news-2","10":"tag-security-2"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/news-points-of-sale-under-attack\/3352\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/news-points-of-sale-under-attack\/3463\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/news-points-of-sale-under-attack\/3774\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/news-points-of-sale-under-attack\/3893\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/news-points-of-sale-under-attack\/4795\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/news-points-of-sale-under-attack\/3692\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/news-points-of-sale-under-attack\/4795\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/news-points-of-sale-under-attack\/4795\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/bitly\/","name":"bitly"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/3352","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/42"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=3352"}],"version-history":[{"count":2,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/3352\/revisions"}],"predecessor-version":[{"id":15781,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/3352\/revisions\/15781"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/3353"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=3352"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=3352"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=3352"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}