Board risk

Tier-1 recovery proof for board escalation

Boards should use documented, isolated, and integrity-validated recovery tests to determine whether every Tier-1 service can be restored within its approved recovery-time objective. Any failure or absence of current testing should trigger operational escalation. External incident totals are not a substitute for the organization's own recovery evidence, and this rule does not establish legal materiality or any organization's present recovery status.

Transaction-Bound Approval for High-Risk Payments

For high-value or changed payments, callbacks and ordinary dual approval are not sufficient authorization controls when communication channels can be impersonated. Payments should be released through the approved treasury or payment platform using phishing-resistant credentials, transaction-bound approval, separate reporting lines, and independent beneficiary verification. Voice and messaging should serve only as corroboration.

Board escalation for sustained KelpDAO redemption failure

Organizations may adopt four consecutive hours of failed withdrawals or redemptions as an internal board-escalation threshold, subject to approval against their liquidity obligations and risk tolerance. Sustained operational harm is a safer trigger than a disputed loss estimate.

Govern AI agents as privileged connector infrastructure

Organizations should treat enterprise AI agents and assistants as privileged connector infrastructure: review and disable unnecessary connectors, limit high-risk actions, require authorization and approval for sensitive grants, refresh tokens where warranted, and retain audit trails that connect users, agents, and downstream tools.

Govern AI agents and SaaS connectors as privileged authority paths

→Organizations should govern AI agents and SaaS connectors as privileged authority paths. They should disable or tightly scope agent creation, require admin approval and audit for new agents and connectors, reduce OAuth scopes, use least-privilege service identities, add egress controls, treat retrieved content as untrusted input, strip hidden comments, and require human approval before write, merge, credential, or outbound actions.

Treat enterprise AI agents and SaaS connectors as systems that can exercise authority, not as ordinary chat features. Limit who can create and connect them, minimize scopes, audit changes, constrain egress, treat retrieved content as untrusted, remove hidden instructions where feasible, and require human approval before sensitive actions. Avoid presenting named incident anecdotes as verified compromises unless primary sources are attached.

Authorize temporary emergency controls for identity, mobile, edge, and AI workflow exposure

→Approve concrete 72-hour authority and downtime tolerance today: force identity controls for finance and admin users, allow security to quarantine non-compliant mobile devices without business-unit delay, and authorize emergency change windows for edge and AI workflow systems, with rollback and business-risk ownership.

Boards or executive teams facing the cited identity, mobile, edge, and AI workflow exposure set should consider a time-boxed emergency-change posture: authorize stronger controls for privileged and finance identities, permit quarantine of non-compliant managed mobile devices, and approve emergency windows for exposed edge or AI workflow systems instead of relying only on monitoring uplift.

Attested TLS confidential-computing architecture review

→Review Attested TLS/confidential-computing endpoint identity binding, relay assumptions, and mTLS/service identity controls this week; treat it as medium-priority architecture risk rather than immediate incident response in this packet.

Place the reported Attested TLS/confidential-computing endpoint-trust issue into this week’s architecture review. Verify endpoint identity binding, relay assumptions, and mTLS/service identity controls; do not treat it as an incident queue item absent affected deployment evidence.