Centrelink takes in-house security tech to US

Powered by SC Magazine
 

Centrelink is to hold workshops in the United States and Australia in an attempt to have its in-house developed smartcard technology adopted as a world standard.

Two-day workshops are planned in Canberra in late June and Washington in July to introduce authentication technology specialists to Centrelink's PLAID protocol.

PLAID stands for 'Protocol for Lightweight Authentication of ID'.

Put simply, it is a smartcard authentication protocol that "specifies how components of a card-based ID authentication system 'talk' to each other".

Centrelink envisions the protocol may one day enable a user to have a single card for access to both buildings and machines (computers) in the workplace.

Developed in-house at Centrelink, the agency has made the protocol available free to the public in the hope a manufacturer will use it to build an off-the-shelf production system.

Centrelink's 27,000 staff currently use random number generators for access control, but the agency is migrating to a PKI certificate-based smart card system later this year.

In 2010, the agency is hoping it will be able to buy a commercial iteration of the PLAID application should one be developed.

The workshops are being held in conjunction with the US National Institute of Standards and Technology (NIST).

Security techies with experience in the ISO/IEC 14443 and ISO/IEC 7816 smartcard standards are welcome to attend.

The Canberra session will take place on June 23 and 24 in Centrelink's Symonston office.


Centrelink takes in-house security tech to US
 
 
 
Top Stories
IBM, NEC picked for major NSW Transport deals
Final contract negotiations begin.
 
Govt proposes crackdown on ISPs over piracy
Wants new legal powers for copyright industry.
 
Westpac interim CIO resigns
Group CIO yet to be appointed.
 
 
Sign up to receive iTnews email bulletins
   FOLLOW US...
Latest Comments
Polls
What is delaying adoption of public cloud in your organisation?







   |   View results
Lock-in concerns
  30%
 
Application integration concerns
  3%
 
Security and compliance concerns
  27%
 
Unreliable network infrastructure
  9%
 
Data sovereignty concerns
  21%
 
Lack of stakeholder support
  3%
 
Protecting on-premise IT jobs
  4%
 
Difficulty transitioning CapEx budget into OpEx
  3%
TOTAL VOTES: 1016

Vote