The emerging OAuth 2.0 web API authorisation protocol, already deployed by Facebook, Salesforce.com and others, is coming under increased criticism for being too easy to use, and therefore to spoof by malicious hackers.. "The OAuth community has made a big mistake about the future direction of the protocol," wrote Yahoo director of standards development Eran Hammer-Lahav in a blog post last week. Hammer-Lahav's criticism may carry more weight than those from the usual naysayer, because he is actually one of the creators of OAuth. "What makes this more frustrating is that the people behind [OAUTH 2.0] are some of the brightest security minds on the Web. These guys know exactly what they are doing, and it's not like they don't care," Hammer-Lahav wrote. "They just gave up and decided that the best they can do is maintain the status quo. They are also representing a large and powerful coalition of big companies too lazy to work a little harder." The link for this article located at Tech News World is no longer available. . OAuth 2.0 faces scrutiny over security vulnerabilities, raising concerns about potential hacker exploits. Insights from specialists in the industry shed light on this issue.. OAuth Security, API Exploitation, Protocol Risks. . Anthony Pell
Security is something that no application can afford to ignore, and it is a particularly large challenge for web applications. A web application deployed on the Internet is subject to potential attack from anywhere, whereas an application contained on an internal intranet has at least fewer locations from which it is vulnerable to attack (usually). The HTTP protocol, which most web applications rely on, was not intended as a secure or session-oriented protocol at all. . . .. Security is something that no application can afford to ignore, and it is a particularly large challenge for web applications. A web application deployed on the Internet is subject to potential attack from anywhere, whereas an application contained on an internal intranet has at least fewer locations from which it is vulnerable to attack (usually). The HTTP protocol, which most web applications rely on, was not intended as a secure or session-oriented protocol at all. As a result, web applications must make use of a number of techniques to layer security onto this protocol. Those of who are not in the business of wheel-reinventing will immediately look about for a framework, preferably based on existing standards, to provide these services for us. Sometimes, however, no one framework is a perfect fit for the job at hand. We might want some of the features of one framework, but other features that are only available in another. In this article we'll use as a backdrop for our discussion an open source project designed for just such a purpose, the Keel meta-framework. Its security design is a practical example of a security structure that can be applied to many different projects. Authentication The first step in figuring out what someone is allowed to do is to figure out who they are, in a provable manner. Java provides the Java Authentication and Authorization Service (JAAS) API for just this purpose. By selecting and configuring the proper LoginModule (or modules, as more than one can be used) we can easily take advantage of a substantialnumber of different authentication mechanisms, including LDAP, Microsoft's Active Directory (which is close but not quite LDAP-compliant), file-based and even database-based authentication. Open source LoginModule implementations exist for all of these options, as well as for many more. Multiple LoginModules can even be used to request the user authenticate themselves by more than one means - perhaps a passphrase and a biometric signature, for example. Ideally, we will use a existing component to provide the front-end for JAAS's LoginModules (which are UI-independent), enabling us to verify the identity of our users with little or no actual coding required. Many frameworks also provide all of the trimmings needed for a complete authentication solution, including a way for a user to request a new password, verify their email address, and other similar operations. The link for this article located at ebcvg.com is no longer available. . Security is something that no application can afford to ignore, and it is a particularly large chall. security, something, application, afford, ignore, particularly, large, chall. . Anthony Pell
Critical information security weaknesses at the Internal Revenue Service demonstrate the importance of moving past the development of an information security program to actually implement the measures outlined in the plan. . .. Critical information security weaknesses at the Internal Revenue Service demonstrate the importance of moving past the development of an information security program to actually implement the measures outlined in the plan . The General Accounting Office found almost 900 weaknesses across the 11 IRS organizations included in its review, particularly in the areas of access and authorization. All of the weaknesses can be traced to IRS' incomplete implementation of its agencywide security program, according to the report dated May 30. The IRS has made progress toward addressing security, including developing a milestone-based plan to fix vulnerabilities -- a step required by the Office of Management and Budget under the Government Information Security Reform Act of 2000 and continued under the Federal Information Security Management Act of 2002. The link for this article located at FCW is no longer available. . Critical information security weaknesses at the Internal Revenue Service demonstrate the importance . critical, information, security, weaknesses, internal, revenue, service, demonstrate, importance. . Anthony Pell
Two separate initiatives led by Netegrity Inc. and Securant Technologies Inc. are looking to develop an XML standard for moving security information--including authentication, authorization and user profiles--across disparate online trading systems.. . .. Two separate initiatives led by Netegrity Inc. and Securant Technologies Inc. are looking to develop an XML standard for moving security information--including authentication, authorization and user profiles--across disparate online trading systems. The goals of Netegrity's Security Services Markup Language, or S2ML, and Securant's AuthXML initiative are similar: to allow customers to move across multiple online exchanges and other e-business systems using a single sign-on and without having to create multiple profiles. Having a standard security language would enable businesses to more quickly create trading relationships and would improve customer loyalty, speed billing cycles and allow businesses to remain in control of online transactions. The link for this article located at ZDNet is no longer available. . Two separate initiatives led by Netegrity Inc. and Securant Technologies Inc. are looking to develop. separate, initiatives, netegrity, securant, technologies, looking, develop. . Anthony Pell
Get the latest Linux and open source security news straight to your inbox.