Implement managed browser security, individual agents and observability
This commit is contained in:
1 parent
ff482ebe23
commit
ea448de2d4
172 files changed
+5404
-347
No files matched your search
@@ -8,9 +8,9 @@ and overriding a centrally locked setting are not alternate control paths.
|
||||
|
||||
Agent authentication must support cryptographic client identity, narrowly scoped
|
||||
revocable credentials, bounded requests, replay protection and attributable audit.
|
||||
Current loopback capability tokens and Windows DPAPI are a foundation; delegated
|
||||
per-agent identities, request proof of possession and individual revocation remain
|
||||
required work. Full UI automation, history/library, safe screenshots and broader
|
||||
The local transport now uses DPAPI pairing, HMAC proof of possession, replay
|
||||
protection and pinned signed post-quantum encrypted requests/replies. Delegated
|
||||
per-agent identities and individual revocation remain required work. Full UI automation, history/library, safe screenshots and broader
|
||||
application capabilities remain separately tracked from the implemented controls.
|
||||
|
||||
Security analysts need enough detail to reconstruct what happened: navigation,
|
||||
|
||||
Reference in new issue
Block a user