Privileged access policy changed. What breaks if Wexler approves it?

AC-2 v3 removes weak-factor fallback, requires phishing-resistant authentication and expands scope to workload identities. RippleTrace has identified 13 linked records across eight systems, but has not evaluated or changed them.

Current posture85/100

→

Proposed posture?agent assessment required

Known blast radius

The same obligation lives in different operational languages.

ConfluenceSheetsJiraAzure BoardsGitHubEntra IDServiceNowVanta

Recently updatedSource · Type · Status

Assurance readiness

85/100

Control coverage30%79%

Verification20%71%

Evidence freshness25%87%

Exception health15%100%

Review progress10%100%

Agent authority · overview

Registered for this view (24)

get_standardget_requirementget_traceability_graphget_execution_statesearch_confluence_pagesget_confluence_pagesearch_jira_issuesget_jira_issueget_azure_board_itemget_pipeline_runget_identity_recordget_servicenow_exceptionget_vanta_control_statusget_architecture_decisionget_infrastructure_recordget_observability_recordcompare_requirement_versionsanalyze_change_impactdetect_gapscalculate_readinessexplain_trace_linkshow_requirement_historygenerate_traceability_matrixgenerate_audit_packet

Never registered

approve_proposalreject_proposaledit_proposalapprove_exception

These have no tool definition anywhere in the codebase, and the store rejects approved-state writes that originate from a tool handler. The agent proposes; a person decides.

Live agent investigationWaiting for agent

READY

Open your WebMCP agent and ask it to investigate AC2-CHG-2026-017. Every call will appear here.

Review queue

Decision audit

Change AC2-CHG-2026-017 received from p.okafor@wexler.example.

Linked records identified across eight systems. None have been evaluated or changed.

Privileged access policy changed. What breaks if Wexler approves it?

The same obligation lives in different operational languages.

Source activity