London Calling: Did Allwinner outsell Intel, Qualcomm?

See on Scoop.itChinese Cyber Code Conflict

London Calling: Did Allwinner outsell Intel, Qualcomm?

Red-DragonRising‘s insight:

People’s Republic of China’s State Owned Enterprise (SOE) Allwinner Technologies Co. Ltd. (Zhuhai, People’s Republlic of China) has sold more tablet computer processors than all Western commercial manufacturers combined! If you use a tablet in ICS or SCADA environments check your tablets’ processor country of orign ASAP! Then contact me to figure out what to do next to protect your enterprise from Chinese hacking efforts….check out their website:

http://www.arm.com/community/partners/display_company/rw/company/allwinner-technology-co-ltd/

See on www.eetimes.com

US Senate Bill Calls For ‘Watch List’ Of Nations Cyberspying On U.S., Trade Sanctions — Dark Reading

See on Scoop.itChinese Cyber Code Conflict

China faces increasing political pressure from the U.S. to curb its cyberespionage activity, but legislation not certain

Red-DragonRising‘s insight:

"In a week that began with the rare move of the Pentagon calling out the Chinese government and military for attacks on U.S. government networks, some key senators have drafted a bill that would create a watch list of nations conducting cyberespionage against the U.S., and spell out just what technologies and products are being stolen — as well as which foreign firms benefit from the intellectual property stolen from the U.S."

See on www.darkreading.com

Pentagon Report Points to Chinese Cyberspying, Military Buildup – The Epoch Times

See on Scoop.itChinese Cyber Code Conflict

The Obama administration has for the first time publicly identified the Chinese regime as the source of a wide ranging campaign of cyberespionage.

Red-DragonRising‘s insight:

MicroSolved’s own Bill Hagestad is quoted in this Chinese Cyber Espionage piece by the Epoch Times:

 

“The Office of the Secretary of Defense is getting it correct albeit not entirely historically correct from a Chinese view,” says William Hagestad II, author of ’21st Century Chinese Cyberwarfare’ and Chinese cyber security consultant, in an email.  “The People’s Republic of China will go the full measure of preventing foreign commercial and yes, military domination of the Chinese information domain in the 21st Century.” 

 

See on www.theepochtimes.com

Mao’s granddaughter accused over People’s Republic of China rich list – UK Telegraph

See on Scoop.itChinese Cyber Code Conflict

The granddaughter of Chairman Mao has been named on China’s rich list, with a fortune of nearly £530 million.

Red-DragonRising‘s insight:

The irony of Chairman Mao Tse Tung’s granddaughter being on the list of the ‘superrich’ within the People’s Republic of China…perhaps it was the intellectual property theft or prolific Chinese cyber espionage…

See on www.telegraph.co.uk

Red Dragon Rising has arrived @ State of Security

Chinese Red Dragon Character  web

Good day friends –

Red Dragon Rising has now arrived and will begin posting items of interest about the People’s Republic of China (中華人民共和國) and her use of the computer as a weapon system…

Please expect to enjoy the latest and most current news and updates about the Middle Kingdom on the State of Security!

Semper Fidelis;

謝謝您

紅龍

OpUSA:: Feint or Fail?

So, yesterday was the date of the much awaited OpUSA, originally proclaimed to be a decisive attack on the US banking and government infrastructures. Thankfully, there seemed to be little impact on US banking or government, and while some commercial and even government sites did get attacked, the sustained impact seemed to be fairly well contained.

Below are a few thoughts on OpUSA and observations made from the data we saw around the Internet (in no particular order):

  • Anonymous groups seemed to be alluding to some infighting, with some groups mocking others and some fragments calling the entire operation a fake. There does seem to be some form of power struggle or competition going on inside the loose alignment of cells, at least from what conversations could be reviewed on Twitter, other social media and the paste bin releases.
  • Many of our team considered the possibility that OpUSA was a feint, designed to attract media attention and recruit new talent, even as primary groups and forces remained on the side lines. From a strategic point, this might make sense, though the in-fighting argument above seems more likely.
  • There seemed to be a large focus on attacking sites primarily powered by PHP. Certainly there are groups and cells inside the movement where their primary focus is PHP attacks and their exploits and tools are solely geared to PHP compromises. Other platforms are likely to remain in scope and within reach, but the majority of the attacks and compromises released yesterday seemed to revolve around PHP.
  • The 10,000 credit card release was MOSTLY a bust. All of the cards we saw were already expired. HOWEVER, it should be noted that SSNs, security questions and other PII was included in that release, so the impacts are broader than just credit card information.
  • Lots of released account credentials, software licenses and such also came out with associated tag lines during the operation. Additionally, many of the folks posting released data to the paste bins and on Twitter also usually release a good deal of pirated software, media and music from what we could tell. It is likely that some of the actors involved in the movement also participate in software and media piracy.
  • At least 3 credit unions were included in the released target lists. This was interesting, especially given the previous Anonymous stance that citizens should replace banks with credit unions. One has to wonder why these three particular CUs were targeted or if they were merely tokens. 

Other than the usual chatter and jeers, there seemed to be little unique about OpUSA and the efforts identified with the campaign. The media is picking up on some additional items here and there, but largely, the operation was seen as being a smaller or less successful campaign than previous attack sets.

Save the Date for CMHSecLunch – May 13th

It’s almost time for another CMHSecLunch! This month, the event is May 13th, 11:30a – 1pm at Easton Mall food court. As always, it is FREE and open to anyone interested in infosec and IT to attend. You can find out more, track the event and RSVP all one page by clicking here.

We hope to see you there! 

Ask The Security Experts: Public Facing Workstations

This time around, we have a question from a reader named John: “I work in a small financial institution and we have problems with physical access to our computers. Many of our workstations sit in semi-public areas and could easily be attacked with USB devices or physical access when a teller or customer service person leaves the customers alone with the machine at a desk or cubicle. What advice do the experts have to help counter these types of attacks?”

Bill Hagestad started the conversation:

Recommended Points for mitigating this digital & physical vulnerability;

1) Remove workstations from semi-public areas; 2) Deploy & install single – purpose Internet workstations at no more than 2 public locations with VERY limited access to financial institution records only after 3 factor authentication has been authorized by credentialed users only; 3) Set time limites on inactive sessions on all banking terminals to logoff after physical proximity to machine exceeds 15 seconds; 4) Enforce 32 random, alpha-numeric character password changes to all critical financial institutional systems weekly; and, 5) Implement and /or continue aggressive financial institution information assurance education program with goal of 100% employee participation; review/update monthly and, 6) Mandate information security and awareness program participation from financial institution leadership throughout all employees and ranks within the organization.

John Davis expanded: I know how difficult this is for financial institutions. Your customer service representatives need computers in their cubicles in order to provide service to your customers, while at the same time those same computers are a main point of physical vulnerabilitiy. Easy steps can be taken, though, to harden these work stations.

First, workstation users should be allotted local administration rights on their systems only when a business need is present. So, CSR workstations should have their USB and DVD ports disabled. Furthermore, their is no need for them to have the ability to upload or download software. In addition, workstations in publicly accessible areas must be turned off each and every time they are unattended. Perhaps you could implement a system similar to the cut off device used on treadmills or at casinos: CSRs would have to clip a device from their clothing to the workstation before it will work. You could accompany this with biometric access for quick and easy access for the users.

Jim Klun added:

From my experience, and assuming the worst case of Windows systems configured as normal workstations with end-users having admin level access, some immediate things I would do:

1. Disable all removable media access at the hardware ( i.e. BIOS) level. At minimum: disable ability to boot from such sources. or: remove all DVD and CDROM drives and physically disable USB ports. (e.g. glue) 2. Ensure all workstations log activity and ensure that the logs are directed to a central log repository and reviewed. Example: http://www.intersectalliance.com/projects/SnareWindows/ 3. Ensure surveillance cameras cover workstation areas. 4. Aggressive screen-lock settings 5. Removal of admin access for all but limited support staff if at all possible. 6. Consider Usage of security cabinets for workstations: Example: http://www.globalindustrial.com/g/office/computer-furniture/cabinets/orbit-side-car-cabinet 7. Network Access Control to limit what devices are allowed on the local network. That unattended RJ45 jack or poorly secured wireless environment is as much a threat as that USB port or CDROM. Bluetooth setting should also be reviewed. 8. Ensure all sensitive information traveling over the local LAN is encrypted. 9. Use a firmware password ( e.g drivelock or a BIOS power-on password) to limit who can boot the machine. 10. Monthly re-iteration of security policies – including need to lock workstations. In my experience such messages are best tied to real-world examples. It makes the risk real – not just an abstract “security guy” worry. For example, this event could be used to ensure employees are aware that an unlocked workstation could lead to the installation of malware: http://news.techworld.com/security/3256513/sovereign-bank-and-penfed-warn-customers-after-keyloggers-are-found-on-laptops/

I note that both JD and Bill talk about enhanced authentication – including the use of proximity devices. Using such devices ( mostly bluetooth ) to secure these workstations sounds like a great idea to me and may be the easiest and most effective solution. Once the financial institution walks away from the workstation – it’s locked and ideally will not boot. http://btprox.sourceforge.net/ – open source Google “computer proximity lock” for a number of commercial alternatives.

Adam Hostetler closed the conversation with:

Everyone has really good suggestions so far. I am a fan of the simple phsyical solutions. I would put the workstations in locked cages. This would prevent any malicious people from inserting USB devices or CDs, or implanting sniffers between the keyboard and USB ports. Additionally, follow the other advice of disabling them through software, just to be sure.

Another solution may be to move to a thin client solution. It is possible to buy thin clients that have no USB ports or optical drives. This would also ensure that no sensitive information was on the workstation, in the event that it was stolen.