-
_brainstorm_ Not afraid of assembly! Defend: July 2025. Phd ambition?!
First, describe the scope and past occurrences of node hijacks.
From Solarwinds to the [recent 1.3 million Android TVs in a b…
-
While not strictly necessary from a security standpoint its a step towards perimeterless security ("zero trust"). A more homogenous setup might also help with devops (e.g. moving a service between mxr…
mxrth updated
1 month ago
-
### Describe the purpose of the group in no more than 4-5 sentences
The purpose of the Zero Trust Working Group is to support ASWF projects that need to function in a Zero Trust operating environment…
-
Key Points for Summary:
- Cloud-Native Security: Cloud-native applications bring new security challenges like securing microservices, containers, and API communications.
- Zero-Trust Architec…
-
# UI Enhancement Proposal
## Description
I would like to propose some enhancements to the user interface (UI) of the Zero-totp application to improve user experience and overall aesthetics.
#…
-
We should implement the distinction of `trusted` and `untrusted` transactions outlined in ZIP 315, as a way of replacing the single "min confirmations" security level. This would then enable wallets t…
-
(This is used to request new product features, please visit for questions on using Istio)
**Describe the feature request**
As identified in https://github.com/envoyproxy/envoy/security/advisori…
-
I ended up creating a pre-proposal that looks like what I may I originally thought was wanted as part of the spec via SIG discussion, but after seeing the content, it was decided that it made more sen…
xibz updated
3 months ago
-
## Add security principles and posture of canvas reference implementation
For the Canvas reference implementation (and, by implication for the eventual standards) we should document the principles …
-