Blog Elements

Half Sized Blog Element (Single Author Style)

Half Sized Blog Element (Multi Author Style)

Black Hat USA 2013 Showcases NAND, Windows 8 Secure Boot Hacking Talks

2013-06-12/0 Comments/in Review/by fdesir

A posting from Dark Reading in there Authentication Section: As July’s Black Hat US in Las Vegas nears, organizers have confirmed another trio of highlighted Briefings from the show, which all focus, in some way or other, on getting under the skin of key systems. Here’s the official rundown: – Technologies don’t get much more ubiquitous […]

Bad SSH Key Management Leaves Databases At Risk

2013-06-12/0 Comments/in Vulnerability/by fdesir

A posting from Dark reading in there Database Security Section: A “gaping hole” in the way enterprises govern the use of one of IT’s least sexy but most used access control and encryption protocols is leaving many sensitive database servers and other network devices at serious risk. Secure Shell (SSH)–a Swiss army knife in the arsenal of […]

Black Hat USA 2013 Showcases NAND, Windows 8 Secure Boot Hacking Talks

2013-06-12/0 Comments/in Review/by fdesir

Bad SSH Key Management Leaves Databases At Risk

2013-06-12/0 Comments/in Vulnerability/by fdesir

Full Sized Blog Element (Big Preview Pic)

Black Hat USA 2013 Showcases NAND, Windows 8 Secure Boot Hacking Talks

2013-06-12/0 Comments/in Review/by fdesir

– Technologies don’t get much more ubiquitous than NAND memory, which is used in just about every gadget going. But ubiquity rarely equals safety, as Josh “m0nk” Thomas will demonstrate in “Hiding @ Depth: Exploring, Subverting, and Breaking NAND Flash Memory.” Thomas will show how NAND hardware can be subverted to hide persisting files, opening the door to everything from basic malwares to full-on device bricking. He’ll release two open-source Android tools to both hide and reveal these hidden files, and explore the security implications of NAND’s striking vulnerabilities. Think there’s an easy fix? Unlikely. Come to the session for the full appraisal.

— Windows 8’s Secure Boot, based on UEFI 2.3.1’s Secure Boot, marks a needed, long-in-coming step toward securing boot sequences against malware. But as ever, the devil is in the minute details, and it turns out that platform vendors are making certain mistakes that can completely undermine Secure Boot’s intended protections. Join Intel’s Yuriy Bulygin for “A Tale of One Software Bypass of Windows 8 Secure Boot,” in which he’ll demo a full software bypass of Windows 8 Secure Boot and explain how these breaches could HAve been avoided had the hardware vendors done things differently.

To read more click here:

Bad SSH Key Management Leaves Databases At Risk

2013-06-12/0 Comments/in Vulnerability/by fdesir

A posting from Dark reading in there Database Security Section:

A “gaping hole” in the way enterprises govern the use of one of IT’s least sexy but most used access control and encryption protocols is leaving many sensitive database servers and other network devices at serious risk.

Secure Shell (SSH)–a Swiss army knife in the arsenal of many an IT department–is best known for aiding in the creation of encrypted tunnels to secure remote access and file transfers, but has gradually gained even more acceptance as a way to secure machine-to-machine connections to help enterprises move large amounts of valuable and sensitive data.

But experts say that enterprises do such a poor job managing the public/private key pairs upon which the protocol depends that they’re putting many of their most sensitive data assets at risk, including database servers that use SSH to connect with applications that tap into them.

According to Charles Kolodgy, analyst for IDC, at most enterprises the internal means by which organizations manage their SSH keys are “often clumsy and decentralized.” What’s more, when organizations do take steps to secure use of keys by central access by only a few privileged administrators, they often don’t monitor those privileged insiders for policy violations, creation of rogue keys or other suspicious behavior that could put the security of SSH communications in jeopardy.

To real more click here: