Files
notes/meetings/3.21.25 Meeting with Jonathan.md

21 lines
1.1 KiB
Markdown
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Agenda
- Discuss Table-top scenario format: Ive never done a table-top discussion. Id like to go over the format.
- Discuss specific scenarios: If you have some specific scenarios youve been thinking about, Id like to go over them. This will give Brooks and I some time to think about solutions and bring them for a deeper discussion next week.
The
- identify attack surface
Nist 800-63b
specific scenarios
- dispersion attack
- nKode observations (from shoulder surfing to screen recording)
- key replay attack
- nKode only authentication; what happens nKode is used email?; how do you recover from a lost nkode?
- can create icons that look the same if they've been compress? Can you mess with advisories ability to record a screen, compress it and send it over the wire
- Can we design non space filling shape? what if the shapes float around in the key? what if they're animated
Make a powerpoint with the gate analogy
how will we engage them to think about architectural design?
can we relax MFA requirements? (nkode make credential stuffing impossible)