Skip to main content

It is not too late to start taking BYOD security seriously

A number of studies have shown that the benefits that come along with a Bring Your Own Device (BYOD) policy are multiple when it comes to improving efficiency of employees. On the basis of these studies, many organizations across the globe proceeded to implement this policy but not all of them managed to carefully consider the impact such a policy would have on the cybersecurity of the organization itself. 

With BYOD, you basically allow employees to bring their own devices (such as laptops) to work and connect to the company’s internal network so they can access organizational resources. It also tends to allow said employees to take the devices home and in some cases, get remote access tools installed on the personal devices to allow them to connect to the same internal organizational resources while they are not on site. As you can imagine, the benefits are quite numerous, but as cybersecurity experts, what we naturally tend to look for are weak spots in such policies and how hackers can leverage these flaws to gain access to your internal network and resources.

A few years ago while I was teaching a class on Penetration Testing and Vulnerability Assessment in India, a Nigerian student of mine asked me a question that has become a staple with close to all the other classes I have taught since then. She asked me “why do we learn how to attack computer systems rather than just learn how to defend them only?” This was a very valid question and I simply quoted to her Sun Tzu’s famous phrase from the Art of War, that if you know your enemy and know yourself, you need not to fear the result of a hundred battles. So as cybersecurity experts, they would need to learn how to check if their own systems are flawed and also try to simulate what malicious hackers may do to gain access to their systems. The major difference between them as ethical hackers and malicious hackers is the purpose for which they would be engaging in the hacking activities. 

Getting back on point with BYOD security, if your organization allows employees to access organizational resources using personal devices, it is imperative that you have a BYOD policy in place. The reason why I feel that this argument is very relevant today is because of the WannaCry ransomware that is running rampant in over a hundred countries across the globe. The method it uses to spread itself is in the form of a malware known as a Worm. This basically means that it propagates itself across the whole network and infects any computer that does not have the patch for this particular exploit. 

The patch in question, MS17-010, was released back in March by Microsoft and it has also been released for Windows versions that are no longer supported such as Windows XP. 
Now, considering this scenario, say an employee has been infected by the WannaCry ransomware or he/she has been attacked using the EternalBlue exploit (which is the exploit that is used to implement WannaCry). If they connect to the internal network, it is most likely that all your organizational computers will be infected if they are not patched already.  

This scenario also highlights the point that within your BYOD policy, it is imperative that you state all personal devices are to be registered with the ICT department and accommodated in the patch management framework of your organization. If not, measures should be made to make sure the network segments accessible to the BYOD devices are not the same as the ones where your system-critical resources also reside. 

As a way of preparation, it’s advisable to undergo penetration testing exercises on your systems, whether it is done as an in-house activity or by an external party. In such cases, it is also in your best interests to include the BYOD policy and related devices within the scope of the pen test. These exercises tend to highlight the flaws in your policies and systems and will also come with recommendations as to measures to help mitigate discovered threats.

To round things up, gone are the days when the cases of malware attacks used to be a foreign thing that would never affect Zimbabwe. Case in point, a few years ago, one of our Harare Institute of Technology B.Tech Information Security and Assurance graduates actually developed a crypto-ransomware penetration testing tool that tested for and exploited particular vulnerabilities in Windows systems and then popped up a warning message instead of the ransom message. It would then automatically trigger the download of patches for the vulnerabilities and also the update of the installed antivirus software. Also, the malware researcher who discovered a way to mitigate the WannaCry ransomware is only 22 years old. The fact of the matter is, technology is available to us all wherever we go, and so are the resources needed to attack and protect computer systems. 

The best we can do to stay ahead of the curve is implement best practices in cybersecurity and ensure that we are ready to counter or respond to any imminent attack. It is not a case of “if” you will be attacked, but “when” you will experience a cyber-attack

Comments

Popular posts from this blog

Password Cracking: RainbowCrack table generation, sorting and usage

I had to do this demo after one of my students asked for my assistance regarding how to use this tool. Usually, I just assign different tools to them individually depending on the aspect of penetration testing we are covering (session hijacking, vulnerability scanning, etc) and then tell them to submit a report and a video demo of how the tool is used. Anyway, after a brief one-to-one discussion I realized the student had actually done the research on how rainbow tables operate (above and beyond the material in the lecture slides) so I figured that if he was here asking for assistance, he genuinely needed it. The tool is available at the RainbowCrack site.  A detailed description of this nifty tool can also be found here . So, firstly I had to generate the rainbow tables. The command line syntax is: rtgen hash_algorithm charset plaintext_len_min plaintext_len_max table_index chain_len chain_num part_index where: hash_algorithm  Rainbow table is hash algorithm specific. R

Malware Analysis: A Python Malware on campus 1

So a few weeks back after a class I'd taken with them,  a number of my students told me of a particular malware that was affecting students' computers, in particular, computers running Windows OS. According to them, if you tried to open a folder that was residing on the USB stick with the malware, the malware would delete some of your files and convert folders into executable files. Granted, the likelihood of a random folder miraculously transforming into a single executable file was kinda "out there" but I figured I'd check it out and use that as a teaching moment for those interested in venturing into malware analysis. So I tasked them to bring me a sample of the malware so I could take a look at it and maybe figure it out. I advised one of them to download DumpIt  and then extract the memory dump from an infected computer using a clean flash disk and then bring it to me. How do you do this exactly? here's how: Download DumpIt . It's a portable

How I Recovered my Corrupted 2TB Hard Drive without having to copy everything to another Drive

So, a little back story. I have a 2 Terabyte external hard drive that's split into 3 partitions for backup; one for entertainment, one for work and one for personal projects. A friend of mine had a Lenovo laptop that was having challenges with installing WLAN drivers (you'd install the drivers and they'd keep giving an error that drivers aren't working. If you tried to uninstall them, they'd just reappear...but that's a whole different story). Anyway, my friend decided to roll-back from Windows 10 to Windows 8 and wanted to copy one of the test builds from my 2TB HDD so I lent it to him. Little did I know that that Lenovo laptop had other plans for me. Upon connecting the external hard drive to the Lenovo laptop, it immediately read it as a FAT32 formatted drive (it was actually NTFS formatted) and had 1.82 TB free space of the "actual" size 1.82 TB. Where panic would have ensued for many, I managed to keep in the growing irritation at such a thing