Category Archives: cybersecurity
Cybersecurity Awareness Month – Cybersecurity Tip #7
Cybersecurity Awareness Month – Cybersecurity Tip #6
Top Secret Colonials October Update
I hope all is well with everyone as we continue to move deeper into the semester. Here are just a few updates with the club.
Everyone please remember to drop off jars of peanut butter and jelly in order to help the us give back. Drop-off boxes are located near the admissions office, in Romo’s, and right outside of Dr. Paullet’s office.
In addition, the Top Secret Colonials are going to be hosting a 12-Hour Gaming Charity Marathon sometime in October. The details on when and where are still being worked out, so be aware of updates happening soon. If you are interested, please email jtwst256@mail.rmu.edu.
Also, please be aware of the cyber security awareness tips being posted throughout the month. Continue to email ideas as you think of them.
Last, if you missed any of the meetings regarding the D.C. National Security Seminar Trip and you’re interested in going, please schedule a meeting with Dr. Paullet.
Thanks, and enjoy the rest of Cyber Security Awareness Month!
Cybersecurity Awareness Month – Cybersecurity Tip #5
Cybersecurity Awareness Month – Cybersecurity Tip #4
Cybersecurity Awareness Month – Cybersecurity Tip #3
Cybersecurity Awareness Month – Cybersecurity Tip #2
Apple App Store Suffers First Malware Infiltration
I would like to start today’s post with a question to my fellow iPhone-owning students, faculty and staff. How many apps do you have installed on your device? For comparison’s sake, I’ll limit this example to just iPhones. At the time of this post I counted 47 installed on my own device. Now that you have that number for your own device, stop and ask yourself, how many of these apps do I know were written and published using trusted code sets and verified publishers? Would I have installed these apps if I knew that they were not trusted and potentially malicious?
In order to thwart the publication of malicious apps Apple, Inc. has developed stringent policies and review processes around application development for their OS X and iOS platforms. To complement these processes, developers are required to use a specific software development package called Xcode.
Earlier this week Apple News announced that it had found that an unprecedented number of apps had made it past the review process and were published to the App Store, subsequently downloaded. To put this in perspective, “Prior to this attack, a total of just 5 malicious apps had ever been found in the App Store, according to cyber security firm Palo Alto Networks, Inc.”, says Jim Finkle from Reuters. To be more precise, 344 apps have been discovered by Chinese security firm Qihoo360 Technology Co. to be potentially affected by this attack.
This begs the question, how could this have happened? How could an organization with such strict requirements on app development inadvertently release apps infected with malicious code? The answer to this question lies with the software that we discussed earlier. Essentially a malicious copy of Xcode was created, also known as XcodeGhost. This framework almost identically mimics Xcode, with the exception that it can be modified to contain malicious code. While this may appear to be a rather simple concept the underlying logic of XcodeGhost is far more complex, a discussion which deserves its own white paper.
The fundamental issue with XcodeGhost is that it could potentially be used by legitimate app developers without their knowledge. Therefore we can assume that legitimate applications that leverage this malicious framework could be susceptible to SQL injection, XSS, or other client-based security flaws that could result in data leakage from a mobile device. Considering the types of apps that are available for banking, location tracking and social media, the problem of data leakage poses a very large and very real problem.
With that in mind, I think back to the 47 apps I have installed on my iPhone and wonder which apps I have installed that could potentially be vulnerable. Should there be a more strict verification process for app development that evaluates even the underlying development software that is being used? While we could leverage peer review methods or even the use of trusted certificates to avoid these situations we may continue to see these types of threats at a high frequency in the very near future. What do you think? Any discussion is welcome in the comments on how an organization might be able to avoid these situations.

