Calls for standardized cybersecurity breach reporting 0 232

cybersecurity breach reporting

Internet security company ESET East Africa has added its voice to the call for legislation to compel organizations to share or release information to a supervisory authority, affected individuals or organizations in case of cybersecurity breaches.

According to Teddy Njoroge, ESET Country Manager in charge of Kenya, Uganda, Tanzania and Rwanda, this would help responsible branches of government, businesses as well as Cybersecurity services vendors to keep ahead of cyber-criminals.

“Due to the siloed and secretive manner in which breaches are reported in Kenya, another attack similar to ‘WannaCryptor’ ransomware could be devastating if directed to critical institutions such as health, government, and especially the financial services sector”, He said.

On Tuesday, May 17, Joe Mucheru, Cabinet Secretary in the Ministry of Information and Communication Technology (MoICT) challenged the financial services sector in Kenya to improve information sharing and reporting on Cyber-security breaches.

“Breach notification eliminates the clandestine attempts by hackers to attack systems and enables synergized efforts towards the prevention of the criminal activity as well as their prosecution”, he said.

Speaking at the Cyber-Security & Banking Forum organized by Citibank and the ICT Authority, the CS said standardized reporting would also help in quantifying the exposure and resilience of organizations both in public and private sector to cyber security incidents.

”A shared reporting system would be a welcome move in developing a unified preventive and counteractive measure to hamper the growth of malware such as ‘WannaCryptor’ and other forms of cybercrime in the country.”

The encrypting – type malware is also known as ‘WannaCry‘  or ‘Wcrypt’ that hit the world on Friday, May 14, 2017, spread rapidly around the globe by exploiting a vulnerability in computers running unpatched versions of Microsoft’s Windows Operating System.

Njoroge added that a standardized and shared reporting system would be a welcome move in developing a unified preventive or counteractive measure to hamper the growth of malware and other forms of cybercrime in the country.

“In the aftermath of ‘Wannacryptor’ ransomware attack we can see from statistics a trend that indicates potential under-reporting of both successful and unsuccessful attacks especially noting that over eighty percent of personal computers and servers in Kenya run on the Windows Operating System”, he explained.

ESET recorded eight ‘Wannacryptor attack attempts in Kenya during the period May 14th to 16th 2017. In Africa, worst hit was Egypt which recorded 1,592 attempts followed by South Africa at 386 and Nigeria at 42 attempts out of the 15 countries that registered attack attempts.

Around the globe, ESET recorded the highest number of attacks in Russia with 30,189 cases, followed by Ukraine – 7,955, Taiwan – 7736 and The Philippines at 1,973 cases and which was followed by Egypt.

“In this period 14,383 ESET clients reported 66,566 attack attempts which were all detected and stopped. 60,187 attacks were detected through file or memory detection while another 6,379 attack attempts were stopped through ESET’s Attack Network Protection module”, said Njoroge.

Previous ArticleNext Article

Coming to terms with cyber security nightmare 0 196

Teddy Njoroge

Last year internet security companies made forecasts about possible cyber-threats to really worry about this year. This we followed with measures that companies and individuals needed to take to ensure a cyber-safe 2018. Paramount among these was the need for proactive use of protective software tools as well as sensitisation and training of users about these threats.

True to predictions, 2018 started with a scenario hardly anyone could have foreseen. Two serious design vulnerabilities in Computer Central Processing Units (CPUs) were exposed that could enable cyber-criminals to steal sensitive or private information such as passwords, documents and photos among other data from unsecured devices.

The “Meltdown and Spectre” CPU vulnerabilities point to a much larger underlying issue. Software bugs and hardware bugs are more common than not, but these once identified can be fixed fairly easily with either a software patch or firmware update for hardware issues.

However, as it turns out this is not possible with these two vulnerabilities as they are caused by a design flaw in the hardware architecture, only fixable by replacing the actual hardware. And that is where the problems begin.

CPUs of affected manufacturers such as AMD, ARM, Intel, among others appear in a lot of Internet of Things (IoT) devices and which are scattered all over the globe.

According to ARM, they are already “securing” a trillion (1,000,000,000,000) devices. Granted, not all ARM CPUs are affected, but if even 0.1 per cent of them are, it still means a billion (1,000,000,000) affected devices.

Due to the huge costs involved, it is not feasible to replace all these faulty CPUs. In reality people will keep their existing devices until end of their life cycles, for years even.

Deployed for countless and diverse applications in the households or offices, once operational many owners have most likely forgotten that they have them and which inherently leaves a giant gap for cybercriminals to exploit.

Any Wi-Fi-controlled device such as refrigerator, digital picture frames, Smart TVs, DVRs and PVRs etc., potentially provides opportunity for sensitive data to be lost. For example, a compromised Wi-Fi password for any of these can make it possible for anyone to hack your home or office network thus giving automatic access to any other connected platform such as emails, social media pages and even shared cloud or archive platforms.

Even though to get access to your IoT device, a would be attacker needs to have compromised the internet network already, or even the applications running on the device, we know that cyber-criminals just like a pack of wolves will not relent after smelling blood.

As a warning, when you are buying a new IoT device, ensure to check which CPU it is running on, and if that CPU is affected by these vulnerabilities.

 

Meltdown and Spectre 0 300

 Microsoft released Security Advisory 18002 on Wednesday, January 3, 2018 to mitigate a major vulnerability to Windows in modern CPU architectures. ESET released Antivirus and Antispyware module 1533.3 the same day to all customers to ensure that use of our products would not affect compatibility with Microsoft’s patch.

The first few days of 2018 have been filled with anxious discussions concerning a widespread and wide-ranging vulnerability in the architecture of processors based on Intel’s Core architecture used in PCs for many years, as well as processors from AMD, and even affecting ARM processors commonly used in tablets and smartphones.

The good news is that ESET can help protect against the types of malware that could take advantage of these vulnerabilities.

And, ESET was one of the very first security vendors to allow the Microsoft patch against the flaw to be enabled.

While ESET protects against potential malware infection, you should also take these steps to secure your computers and data:

  • Make sure your browser is up to date. For Chrome or Firefox users:
    • Mozilla has released information describing their response, including how Firefox 57 will address these security flaws.
    • Google has stated, “Chrome 64, due to be released January 23, will contain mitigations to protect against exploitation.” In the meantime, you can enable “Site Isolation” found in current stable versions of Chrome to provide better protection.
  • Make sure you update your ESET software, then update your Windows OS to protect against this exploit. To update ESET:
  • Customers should review ESET’s Knowledgebase article for important updates.
  • See this great collection of tips, articles and recommendations from the Google Project Zero team.
  • If you have a cloud-based server or have a website hosted by hosting provider, check to see what mitigations they have implemented already to prevent Meltdown.