Early figures from a report due out in November show that consumers are close to hitting a data usage roadblock that enterprises--which may use even more data--won't encounter.
Every week, I get this question from someone at least once: What's the difference between the "Telecom" in FierceTelecom and the "Communications" in FierceEnterpriseCommunications?
The fact that Congress is considering an abstract concept to specify explicitly "identity" may open the door for private firms to do the same. But how could such a system identify people while maintaining privacy?
Should the public's right to data be defined before the law starts interpreting "public data" as something to which everyone has a right?
An open source team that found itself competing with the very platform it tried to support amends its value proposition with an orchestration engine it hopes will keep up with OpenStack.
Someplace beneath the marketing hype is the reality of what "Internet of Things" technology can actually do and it actually makes more sense than the hype itself.
The distribution sources for potentially malicious documents are actively working to disable their distribution. But a Dropbox security alert seems to indicate that's making customers mad.
Reviving a sales model that goes back to the 1980s, the reseller becomes the customer's point-of-presence for Google's SMB applications.
Think about this for a moment: If your phone has an HTML5 browser, and that browser has WebRTC, then why do you need a phone number?
How can the largest producer of collaboration appliances make collaboration work where appliances typically don't? Cisco engineers are tackling the problem before they're tackled by it.
The problem of securing identity in a network of both mobile devices and clouds is only growing more complex. A solution may require us to transcend what we think we know.
The most eye-opening survey numbers from Ponemon to date imply that no one--absolutely no one--is actually implementing security governance standards as specified.
Last Monday in Spotlight, I pointed you toward an article from the personal blog of security researcher Jonathan Zdziarski, who reported on the existence of several exploitable back doors around security features in Apple's iOS.
It looks like an open source, on-premise implementation of Dropbox. Look closer, though, and you'll see a way to securely open up object stores on an OpenStack platform.
The way to implement higher bandwidth services on the way to 10gig involves the deployment of a quality-of-service management technique that net neutrality regulations might prohibit.
Among the many things Apple is notorious about not telling people is the architecture of its iOS system services. While on the surface you'd think Apple is operating in the best interests of security, what this means is that an active open source movement has germinated with the explicit goal of ferreting out ways to establish rootkits and other exploitative, stealth services on iPhones and iPads.
If a champion of the people was supposed to have emerged from the "public dialog" about how the Open Internet problem was to sort itself out, that champion was difficult to see for all the smoke.
Separated by 4.6 miles of fiber from the customer edge, a select customer exchanged Ethernet traffic with the telco over a 100GigE connection.
The system Ping Identity has been building (and to some extent, acquiring) to let people log onto services with their mobile phones is now ready for public launch.
While some net neutrality advocates have elevated the issue to the level of a human rights debate, one advocate is suggesting it be deflated to that of a business arrangement.