Posted: 6th November 2014 by Josh in Uncategorized
Tags: , , , ,

Yesterday Palo Alto Networks released a report on a new OSX & iOS malware, WireLurker.  The best write-up I have seen so far is here: http://www.zdziarski.com/blog/?p=4140

A couple pertinent points:

-Currently only circulated through Chinese warez – seems to be targeting identifying information of users only (possibly to identify key players in the Chinese software-pirating market?)

-The concern is not so much about WireLurker itself, but “…that this technique could be weaponized in the future, and be a viable means of attack on public and private sector machines.”

-If you are interested in detecting if a device has been compromised, see here:  https://github.com/PaloAltoNetworks-BD/WireLurkerDetector – If anybody has IDS sigs yet, please let me know….


Key Takeways:

-Remind users that jailbreaking your phone (whether android or iphone) nets you less security – better yet, enforce policies that disallow jailbreaking devices that have organizational data on it

-“While your own Mac may not be infected with WireLurker, it’s possible others (in your school, college, at work, or public computers) are, so it’s important not to trust any devices other than your own. To help prevent this from accidentally happening, you may wish to pair lock your device using these instructions.”

We need to continue to help foster cultural change that surrounds most of our Mac users – the fallacy that if you have a Mac, you don’t need to worry about security issues… “Only PC users need to worry about that.”

This is part of our blog series of continuous dialogue that you should be having with your Executive Leadership, to make them aware of issues that they should be making organizational decisions on:

“There is ongoing litigation whereby most insurance carriers are pushing back against its clients when it comes to “Cyber” security-related claims under an organization’s general liability insurance. Most recently, the insurance carrier for P.F. Chang is taking legal action against P.F. Chang’s claim that their commercial general liability policy covers defense cost and provides indemnity coverage for their recent credit card breach.

Leadership needs to understand that our general liability coverage will most likely not cover a digital security event, even if the coverage wording is vague (the carrier will most likely still fight against it, to avoid precedent-setting cases). If we want to pursue coverage for digital security issues, we would need to pursue a separate policy/rider specifically for it.”

For more information, continue to the following link.


Organizational leadership needs to understand that no matter the technical & procedural protections that are put in place, prevention eventually fails, especially (but not exclusively) against a targeted attack orchestrated by a motivated adversary. This means that the organization must plan for this eventual “failure”—To be able to detect and respond to these failures.

When this failure occurs, the questions that must be asked from leadership is not “Why did our defenses fail,” rather, “How long did it take for us to detect & respond to this failure?” According to industry sources, the mean time of detection of advanced attackers is around 8 months—This mean that the average organization does not know that they have been severely compromised for 8 months, which is typically more than enough time to achieve the adversary’s goals.

With all that in mind, what is your detection strategy?