CBubbleSurface Demo
Step 2 of 2 · INC-1001

Define the live security scenario
we are going to prove

The systems are already connected. Now we define the affected identity, human reviewer, external agent, and the capability transition BubbleSurface must enforce.

Elastic / SIEM connected
Auth0 connected

Affected user

Asha Mehta

  • Identity: IDN-ASHA
  • Suspicious session: SES-ASHA-SUSPICIOUS
  • finance-admin privilege active

Human reviewer

Kavya

  • Security analyst: analyst-kavya
  • Can review, approve, reject, or modify
  • Human decision required before sensitive execution

External agent

WebMCP Agent

  • Discovers tools from the live page
  • Invokes only currently exposed capabilities
  • Reacts as the capability surface changes
  • Cannot bypass approval
  • Cannot make a stale capability valid

Test condition

  • ✓Unfamiliar high-risk login from Frankfurt
  • ✓Three failed MFA challenges
  • ✓finance-admin granted outside the change window
  • ✓Unfamiliar session reached a critical finance resource
Goal: contain the identity risk without exposing a broader action surface than necessary.

BubbleSurface should expose investigation capabilities first, keep sensitive execution hidden until exact human approval, and move to verification after execution.

Capability transition we are testing

  1. 1inspect_incident
  2. 2check_privilege_changes
  3. 3prepare_containment
  4. 4Exact human approval
  5. 5remove_approved_privilege
  6. 6verify_identity_state
Before approval:

remove_approved_privilege hidden

After exact human approval:

remove_approved_privilege available

After execution:

remove_approved_privilege removed
verify_identity_state available

The golden path highlights identity-state verification. The live backend requires both verification kinds to pass before final recovery.

What this proves

Shared live state

Human and agent act against the same current security workflow.

Human-gated authority

Sensitive capability appears only when policy, state and approval permit it.

Dynamic WebMCP surface

Capabilities appear and disappear as the workflow progresses.