| |
 Onom@Topic+
Federative framework
|
| |
|
o Use case #1: NFC, VHDR and
contactless authentication applied to
e-Admin
An innovative discovery mechanism is put
into practice to make the Service Provider
aware of the card fonctions and capabilities.
The user-friendly benefit of NFC is shown
by facilitating the connection to an e-Admin
web portal. The user authentication is
delegated to an Identity Provider, and
once executed successfully, the user is
given access to reserved dat stored on
a remote e-Admin server. Upon user's request,
a huge amount of data is downloaded on
the user's machine. These data are then
transferred onto a VHDR token as follows:
The VHDR part of the demo demonstrates
the performance of the contactless interface
by the same data transfered at 2 different
transfer data rates:
- 424 kbps : current data rate (e_passport,
NFC),
- 1.7 Mbps/ 3.4 Mbps/ 5.1 Mbps
|
| |
|
o Use case #2: Biometric match-on-card
applied to e-Admin
An innovative discovery mechanism is put
into practice to make the Service Provider
aware of the card fonctions and capabilities.
A secure reader with biometric sensor
is employed to collect the fingerprint
and to validate it against a reference
template hosted on-card. A digital signature
of an e-Administration form is controlled
by the biometric verification. The e-Admin
form is partly filled out automatically
for user's convenience. Prior to deliver
the form to the user, the Service Provider
requires a symmetric end-to-end authentication
of the smart card and delegates this authentication
to an Identity Provider (trusted third
party). The Identity Provider performs
the authentication and writes securely
an acknowledgement token (the artifact)
onto the card. This artifact will be checked
by the Service Provider for service allowance
through a validation based on SAML Request/Response
protocol.
|
| |
EsterelTechnologies
formal validation methodology applied
to ICAO EAC
Current smart cards software design
methodology uses the classical V development
model with adaptations to smart cards.
When the product requires Common Criteria
certification, the software development
process is modified to integrate security
oriented tasks and deliverables. This
approach suffers from weaknesses like
complex maintenance, lack of automation;
leading to costly document updates, manual
test traceability, and lack of an unified
development environment. A dedicated workgroup
in ONOM@topic+ works on a new methodology
and associated tools that aim to solve
most of these weaknesses.
In this presentation we describe this
new methodology and the associated tools.
The methodology associates formal design
specifications (mixing graphics and text)
with advanced simulation and verification
techniques. We illustrate how it will
allow high level CC certifications.
|
