do it. think it. blog it! ... a twisted world

Saturday Jun 25, 2005

By this coming Monday all major federal agencies are required to submit detailed implementation plans to the White House Office of Management and Budget that describe how they plan to meet the smart-card requirements outlined in Federal Information Processing Standard (FIPS) 201 (download PDF). The 2004 presidential directive requires all federal government agencies to use smart cards to authenticate employees for access to resources.
The requirements stem from Homeland Security Presidential Directive 12, which calls for electronic identity cards to be issued to all federal employees and contractors as part of a bid to better secure access to government facilities and information systems. The cards must support two-factor authentication via digital certificates, a password or personal identification number, and biometric identifiers. They also are expected to be interoperable across all federal agencies.
SmartCards aka Java Cards are effective... very very effective. The Java Card Development Kit, includes a complete environment in which applets written for the Java Card platform can be developed and tested. It enables developers to create applets that utilize the features of the Java Card API. Now : This technology is not something new. We've been at it for ages... Why do folks shudder with reluctance when they are given new technologies to play with? Well, ask us, and we shall show you how ;-) According to this report, Taiwan had distributed Java Cards to it's population (22 million) way back in 2003. So did Taiwan, India, China and others... (I just cannot find those reports, I shall provide you links to those reports as soon as I find them) This article that dates back to 2000 would show you that we truly are the early adopters of this technology. So why is the federal sector still fumbling with their deadline for deployment soon approaching.
Sometimes It's best to let the experts show you the way. Why not ? Haven't you seen the Sun folks walking around with Java Cards for a while now ?
and hey, The DoD nomenclature for Java Cards is CAC (Common Access Card), and who do you think is behind it ?? Well, truthfully, the peices of plastic are from Schlumberger, the card readers for windows are from ActiveCard and THE REST, By US !!! ;-) Java Card technology is one of the best secure authentication technologies for trust, privacy and verification of identity on the network, deployed in way over 500 million smart card and mobile phone environments around the world. Sun is building on this success and applying its expertise to the Windows environment though inclusion of Java Card technology support in its Java Desktop System and Java software systems. This model will not only secure access to the device (mobile handset, desktop or infrastructure), but access to network services, and ultimately access to and distribution of content. This guarantees authentication of the device, of the sender, and of content represented, helping reduce victimization through fraudulent Web sites, and e-mail spam and viruses.
Think about it feds.. You got our number.. (and if you didnt know it, it's +1-800-786-0404)
Andrew Layman is Director of Web Services Interoperability for Microsoft Corporation. He participated in the design and development of XML as an interoperable format and protocol mechanism since its beginnings in 1997. Andrew was co-editor of the Namespaces in XML specification,co-author of the seminal XML Data Schemas specification, participated in the W3C XML Schemas specification, and co-authored the specifications for SOAP and the Web Service Description Language. Currently, Andrew manages a team responsible for making sure that the Web Services specifications provide an integrated protocol framework for platform-neutral, language-independent interoperability across multiple vendors and application domains. Robert Brewin is a Distinguished Engineer and Architect for Sun's Developer Tools and a leading advocate for various tools initiatives with an emphasis in improving the ease of development capabilities in both the tools and platforms. Within these roles he was also the architect for Java™ Studio Creator as well as the Java Studio Enterprise and Sun Studio product lines. He has been involved in a number of Sun initiatives, including the SunOne architecture and various technical and architectural teams within the Sun software organization.
SO : Andrew would be at the JavaONE 2005 conference presenting on :
Java™ and .NET are the predominant platforms for new software development. Many developers need a good understanding of the architectures of both platforms in general and how they interoperate in particular. The standards and profiles based on XML and SOAP are the pillars for on-the-wire interoperability between the platforms. This session features the visionaries and architects of the infrastructure of both platforms. The WS-* Web Services protocols are interoperability protocols supported by the .NET platform. The session starts with a brief walk through the standards for interoperability and touches upon the current support for these in both platforms. The session highlights some practical aspects of interoperability with some case studies and examples based on some existing and relatively newer standards. Finally, the session covers the future roadmap for interoperability between the two platforms. This cutting-edge session is for developers and architects who need a technical overview of the practical aspects of interoperability. Hear straight from the architects designing the platforms for better interoperability. After attending this session, you should have a good understanding of on-the-wire interoperability, the support for it in both the current Java and .NET platforms, and the efforts being made for the future.
This was just an FYI for those that many that may forget this IMPORTANT presentation.