Value & Security for the Connected Customer

We've all seen the requirements. Your password must contain upper and lower case, be between 6 and 23 characters long, and must contain at least one Beatle. And you need to pick a new one on a regular schedule, even if you don't use the site that often. Everybody hates it, and it turns out that these rules do not make it harder for attackers. 

How did we get into this mess? We'll take a look at the history of passwords, the attacks we thought we were protecting against, the attacks we actually need to protect against, how people made everything worse, and how we can make it better.

Key Takeaways:

- Passwords aren't being used for what they're good for, and we need to change that

- Password rules as seen today make for bad passwords, and we can do better

- People will find ways around your arcane policies

One of the challenges with electronic signatures is: How does the user identify themselves? There is also buzz around Qualified Electronic Signatures (as defined in eIDAS), and that this is the only way of replacing the handwritten signatures.
This presentation will take a look at the properties of electronic signatures and different ways the user can identify when signing.

Key takeaways:

* Better understanding of electronic signatures
* The role of eID in electronic signatures
* Electronic signatures and eIDAS