Re: [Model-t] Minimization

[[e-mail]]

> Just wanted to send an update that there’s a new version of the
> minimization draft, inspired largely by your comments Martin. I like the
> direction of making smaller number of statements and shorter overall
> text, and focusing of course on established principles. Comments
> appreciated.

A few possible interesting points to include ... I can provide text suggestions if it's useful.

-- Reducing the amount of information shared between devices/subsystems within a larger system not only increases security, it also protects privacy.
-- Reducing the amount of information shared (the depth of the interaction surface) can help to reduce coupling between subsystems, hence increasing system resilience while also increasing security.
-- Reducing the amount of information shared also reduces the attack surface by reducing the amount of control an attacker might gain over any given subsystem through a given interface.
-- Reducing the number of places (physical or logical) in the system where information is shared (the breadth of the interaction surface) can help reduce the attack surface in meaningful ways.
-- For both privacy and security, care should be taken to _destroy_ information in a timely manner ... protocols should be designed, where possible (it's not always possible), to not rely on information being present "forever."
-- Not only should the minimal amount of information be shared, the most abstract, or least specific, information should be shared to "get the job done."

I don't know if all of these are useful or not, just throwing them out there for discussion.

😊 /r