Skip to content

Conversation

@deansaxe
Copy link
Collaborator

@deansaxe deansaxe commented May 7, 2025

Following our last meeting, I've created the first version of the outline of the cybersec awareness month planning guide.

First version of the outline of the cybersec awareness month planning guide.
Copy link
Contributor

@seanmillerrsa seanmillerrsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great doc!

@deansaxe
Copy link
Collaborator Author

deansaxe commented May 7, 2025

I addressed the initial feedback from @jeankaplansky and @seanmillerrsa in the latest version.

Copy link
Collaborator

@xmlgrrl xmlgrrl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great outline. We can iterate as we get exposure to more feedback in CG meetings and the like. My only feedback for now is that it might be useful to stress what not to do, e.g., don't write down all your passwords in a notebook. (An elderly family member had hers stolen!...)

@jeankaplansky
Copy link

Great outline. We can iterate as we get exposure to more feedback in CG meetings and the like. My only feedback for now is that it might be useful to stress what not to do, e.g., don't write down all your passwords in a notebook. (An elderly family member had hers stolen!...)

Agreed. OTOH, getting a stubborn elder family member to use password management software can be challenging. Many older people will change their passwords if they don't remember them, and they will willingly forget about password management apps. The other issue is getting the same older people to update password management apps if they are cognitively blocked from remembering that the password management app even exists.

Learned experience: Some older people need a human password manager AND an app.

@deansaxe
Copy link
Collaborator Author

deansaxe commented May 8, 2025

Thank you @xmlgrrl and @jeankaplansky. I love what this conversation is exposing.

Personally, I think writing down your passwords is fine behavior for many people who's threat model is not the same as mine. Loss of that book could be devastating, but it is hopefully less frequent than account takeover due to reused passwords.

@jeankaplansky One of my biggest concerns with passkeys is exactly what you're pointing at. Password managers can be challenging. Interfaces are inconsistent. Access to the credentials after the owner has passed away could be impossible if the provider doesn't allow legacy contacts access to the data.

This is giving me a lot to think about for how we frame this guidance, especially regarding how it's framed for someone who is not like me. Someone who is not comfortable with technology and all of the decisions that have to be made will approach this in a very different manner.

@jeankaplansky
Copy link

Thank you @xmlgrrl and @jeankaplansky. I love what this conversation is exposing.

Personally, I think writing down your passwords is fine behavior for many people who's threat model is not the same as mine. Loss of that book could be devastating, but it is hopefully less frequent than account takeover due to reused passwords.

@jeankaplansky One of my biggest concerns with passkeys is exactly what you're pointing at. Password managers can be challenging. Interfaces are inconsistent. Access to the credentials after the owner has passed away could be impossible if the provider doesn't allow legacy contacts access to the data.

This is giving me a lot to think about for how we frame this guidance, especially regarding how it's framed for someone who is not like me. Someone who is not comfortable with technology and all of the decisions that have to be made will approach this in a very different manner.

I use passkeys and biometrics on mobile devices. I never tried to explain either passkeys or biometrics with my dad. He didn't use his phone as wallet (I do), and he had enough problems with passwords and differentiating between bank apps and bank web apps.

We need to be ready for people like my dad.

@rkzack
Copy link

rkzack commented May 9, 2025

Great. But, one thing to consider: I advise caution when collecting and storing account names/logins in an insecure way, as generally speaking, that information is also considered sensitive or protected per most security frameworks.

Why? In practice, the vast majority of people still re-use passwords across accounts, usually having 3-4 primary passwords they re-use. So having a list of their account names increases the risk of greater compromises in the event one of those passwords is compromised.

Ideally, step 1 should be that all this info should be recorded in a secured, encrypted location, accessible only to fiduciaries when the time comes.

@gffletch
Copy link

This feels like we need a risk model for this topic :-) At the end of the day, the mechanism mostly likely to be kept up to date by the human is probably the best option.

@gffletch
Copy link

Do we need to pull in concepts like a revocable living trust? Does that change anything?

@gffletch
Copy link

I am a little surprised that utilities come before financial accounts

@deansaxe
Copy link
Collaborator Author

I am a little surprised that utilities come before financial accounts

Just my first best guess. None of this is fixed in stone, it's a place to start talking.

@deansaxe deansaxe merged commit ec2ed07 into openid:main May 13, 2025
@deansaxe
Copy link
Collaborator Author

Merged, I'll queue this up for the next agenda on Friday's meeting.

- Does the service offer a legacy contact or other mechanism for delegation of control?
- If so, what was the chosen mechanism? Include URLs or other data as needed.
- Does the service explicitly ban taking over access to a personal account?
- How do you want your account managed by your estate?
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a whole forward-looking aspect that can be included here as relates to how someone wants their "personhood" preserved and/or their content used posthumously. To me it's the extension or inverse of the living will.

Thinking - reanimation, use of content to fuel grief bots, etc. The law hasn't really caught up here but the more we can encourage people to try to envision what they protected as relates to their identity and legacy, the better. Elders right now won't have as much to say, but anyone middle age and younger at minimum should be considering this.

- Does the service explicitly ban taking over access to a personal account?
- How do you want your account managed by your estate?
- Need to list options here.
- Who will manage your digital estate?
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To the point I made above about posthumous digital personhood, what does it mean for someone to manage your full digital legacy/personhood? What's the amount of time someone could/would do that? Does it matter if your intentions are forgotten in fifty years when no one you knew is around regardless?

- How will they know your wishes? Have you communicated any recovery mechanisms to them already, e.g. Apple's recovery QR code?
- How will they get access to your passwords, passkeys, OTPs (SMS and TOTP), and other credentials necessary to access your accounts?
- If you store data securely in a safe deposit box, it may not be accessible when needed. Consider how you might be able to store this in a more accessible location, e.g. fireproof safe. (Consult local laws.)
- How will you ensure the manager does not get access to the accounts/data before necessary?
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is such a robust dilemma. Account identities need to be protected at all costs all the time, except for that one time when you are incapacitated or dead. There has to be an easier way to solve this. Biometrics are useful but to another comment, not prevalent for elder people especially. Like having a virtual vault that opens on command to only one person when conditions are met.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the way you're thinking. In the identity world we're starting to discuss this as a concept of "delegated authorization" where the delegation includes some conditionals such as whether a person is deceased. @gffletch and others are actively working on/thinking about these issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants