The I-Card Cloud Selector CloudCard

 An introduction to Avoco’s fully Cloud based I-Card Selector, CloudCard  A demonstration of the logon process using the Cloud selector and a shared secret  A demonstration of the extended use of Information Cards: ◦ Digital signing in the Cloud using Information Cards ◦ Access control of documents using Information Cards

 A fully Cloud based Information Card selector  A leap forward in Information Card usability  Bypasses the world of Windows desktops  Designed to have similar functionality to Windows CardSpace, e.g. ◦ Personal cards can be created ◦ Cards can be imported ◦ Cards can be backed up ◦ Works with standard and auditing cards – not yet tested with others e.g. Relationship and Signalling cards ◦ Like CardSpace, token encryption is left to IdP for auditing cards

 Usability benefits include: ◦ Universal access to your Information Cards ◦ True zero footprint for end users – no plug-ins, ActiveX, downloads, etc. ◦ Access from normal desktops/laptops as well as phones/mobile devices ◦ Test Implementation Site: - currently password username only into CloudCard portal but can be almost anything

 Extensibility: Modular design permits simple use of alternative login protocols, etc.  Portability: Written in PHP ∴ easy to port to other languages such as Java (if needed)  Security: Incorporates anti-phishing technology through shared-secret log in control  Security: SSL - MITM attacks less feasible  Standards: HTML spec to be submitted as standard

 CloudCard called as a post from RP web page: <a href=" udCardA/CardView.php?ampIssuer= cardspace.com&RequiredClaims=http....  Link specifies entry point to selector, required card issuer, claims, etc., like calling a desktop selector.  Additionally certificate of RP is included.

 Used to provide anti-phishing of the I-Card web service account  User chooses a photo before logging into their account  If correct photo displayed, user can log in knowing the site is genuine  A photo always presented to prevent guessing username Sir Henry No-Tail

1. Generate phishing page 2. Username submitted CS Backend 5. Correct image set in fake password entry page Phishing server (PS) 3. PS submits username to CS backend 4. PS gets image from response

1. Create page and setup session key 2. Username submitted with session key data CS Backend 3. Valid Session key: Image returned

1. Generate phishing page 2. Username submitted CS Backend 5. Cannot set correct image Phishing server (PS) 3. PS submits username to CS backend (invalid session key) 4. No response

 No protection against desktop Trojan / virus (but then entire system is potentially compromised including desktop selector)

 Use your preferred login scheme e.g. OpenID.

 Face recognition and recognition of familiar objects is part of an acquired evolutionary trait that helps us survive  We are good at it  We place trust in our ability to use face recognition and object recognition  We use processes of cheat recognition all the time, everyday, to interact with others  An identity system must mesh real world me with digital me  We must use existing human traits when designing the system

 If you’re interested in the research into cheat recognition and similar:  Cartwright, J Evolution & Human Behaviour. Palgrave  Daly, M & Wilson, MI Human evolutionary psychology and animal behaviour  Cosmides, L and Tooby, University of California at Santa Barbara broadnarrow.pdf

 The Avoco Cloud Selector is modular, so ◦ Can choose to use a myriad of authentication techniques – this presentation shows one  Important not to forget the big picture: ◦ Usability – for a consumer as well as business audience ◦ Represents the real world me in a familiar way  I am me because of these reasons (claims)… ◦ Can be used not just for logging into web sites  Identity is more than just access control

 Authentication: ◦ Digital certificate ◦ OpenID ◦ LiveID  Card authentication specified by RP ◦ e.g. only a card backed by X509 can be selected  Seamless upload of cards from IdP to Selector – transparent management for users

 A system for issuing OpenID’s with an Information Card  Links the two ID system – best of both worlds  OpenID attributes can be set as a Information Card Claim  Information card can be authenticated by that OpenID  OpenID linked to the extended claims system of the Information Card  Best of each to create a symbiotic ID system

 Requires additional HTML / JavaScript ◦ Recommended for web pages to allow user to select a Cloud Selector and Desktop Selector where appropriate / available.  How are multiple Selectors to be addressed? ◦ Preconfigured to a single Selector ◦ Preconfigured dropdown list ◦ Dynamic list populated from discovery service.

Digital Signing in the Cloud

 Digital certificates are user-unfriendly and unpopular  People don’t like to install software, including browser plug-ins  Current solutions for signing on-line forms are open to denial of signing caused by only including form text in signature  Therefore, to encourage digital signing, these issues must be addressed

 Avoco Secure have developed first truly Cloud based digital signing  Can be used on: ◦ On any operating system ◦ Using any browser ◦ From desktops, laptops, mobile devices, phones and so on  Signing does not require user to have X509, but standard PKCS#7 signature produced.  Nothing to install – fully Cloud based.  Non-repudiation addressed.

 Always a problem to identify the signer  Avoco – generate repeatable RSA key pair from ID info e.g. ◦ Information Card claims ◦ OpenID attributes ◦ ATM Card numbers ◦ Passwords ◦ etc., etc. ◦ Exact data specified by host  Key pair -> transient X509 used to sign with  Cert and key pair destroyed after signing

 Image of the completed form incorporated into the digital signature

 Incorporates timestamp (RFC3161)  s signature to user  Signature verifiable by common tools as well as Avoco on-line verifier

Controlling Access and Applying Usage Policies to Documents and s

 Controlling access to documents, s using Identity Information from Information Cards ◦ secure2trust ◦ secure2 ◦ secure2access  Claims used to: ◦ Control document and access ◦ Apply usage policies, post access  Done in a content centric manner  Security is persistent across perimeters

Susan Morrow Head of Product Development Avoco Secure