Migrate Markdown-Notes: projects, meetings, reference, personal
This commit is contained in:
20
meetings/3.21.25 Meeting with Jonathan.md
Normal file
20
meetings/3.21.25 Meeting with Jonathan.md
Normal file
@@ -0,0 +1,20 @@
|
||||
Agenda
|
||||
- Discuss Table-top scenario format: I’ve never done a table-top discussion. I’d like to go over the format.
|
||||
- Discuss specific scenarios: If you have some specific scenarios you’ve been thinking about, I’d 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)
|
||||
Reference in New Issue
Block a user