Wednesday, 1 March 2017

Cyber Security Roundup for February 2017

Earlier in the month of February, a grey hat hacker named "Stackoverflowin" ran a simple script which resulted in over 150,000 printers, mainly in businesses, printing out pages with some nice ASCII art and a message saying the printer was owned. Many in the media pointed the blame as a printer security issue, but the main reason was horrendously poor firewall configuration. These printers were made vulnerable due to the presence of a highly insecure rule in their network's firewall, which allowed internally networked printers accessible across the entire internet. It didn't matter if the printers were large sophisticated multi-functional devices or simple till receipt printers, they all received rogue print jobs directly from the internet thanks to terrible firewall management. Makes you wonder what else is vulnerable on these business' networks as a result of poor firewall configuration and without the security management safety net of regular network vulnerability scanning and firewall rules review.
Image result for Stackoverflowin
Printing outs sent Printers open on the Internet

Third party cloud security comes into question after CloudFlare, a popular content delivery network used by more than 5.5 million sites, accidentally leaked customers' sensitive information for months. If you are a CloudFlare customer I strongly advise to change your passwords. The Yahoo’s sale to Verizon has dropped by $350m following Yahoo’s recently reported data breaches. And Sports Direct came in for criticism for not advising its 30,000 staff that their personal details had been hacked.

Back on the technical security front, Google researchers illustrated security weakness in SHA-1. The cryptographic hashing algorithm has not been considered secure since 2010, so the research is a poignant reminder to never use SHA-1 on new configurations, and to review and phase all SHA-1 usage in any existing solutions, such as site-to-site VPNs and within application development, go for SHA-256 or SHA-3 hashing instead.

News
Awareness, Education and Threat Intelligence

No comments: