Privacy & cryptographic systems
Which assumptions are holding the boundary in place?
What I am examining
I investigate the identities, keys, storage, and protocols that a private system depends on. My attention is on their connections: what happens when a key is lost, a credential changes, or an algorithm has to be replaced while the system remains in use.
Why it matters
Privacy depends on decisions distributed across a system. Making those dependencies visible can help people maintain control as software, credentials, and cryptographic requirements change.
What the evidence must establish
I examine interoperability, key handling, downgrade behavior, recovery, and resource costs in authorized test environments. Any security conclusion must identify the threat model, the conditions tested, and what remains outside the claim.
The comparison
Reviewed cryptographic standards are the foundation. My work here concerns how systems apply them, where their assumptions meet operational reality, and how that use can be inspected and changed.