How to Witness Cisco Cloud Control Agent Actions with Cryptographic Compliance Evidence

1. What Cloud Control Is

Cisco Cloud Control is Cisco's agentic operations platform for infrastructure management. It provides an MCP-native architecture with 50+ pre-built connectors spanning cloud providers, network devices, and security appliances. Agents operating within Cloud Control execute actions across cloud, network, and security domains -- provisioning resources, modifying firewall rules, rotating credentials, and orchestrating multi-step workflows.

Cloud Control provides:

• MCP-native architecture -- agents communicate through the Model Context Protocol, enabling tool discovery and invocation across connectors
• 50+ connectors -- pre-built integrations for AWS, Azure, GCP, Meraki, Firepower, ISE, and other Cisco and third-party platforms
• Multi-agent orchestration -- orchestrator agents delegate tasks to specialist agents scoped to specific domains
• Action logging -- internal records of what agents did, when, and against which resources

The Accountability Gap

Cloud Control logs actions internally, but these logs are produced by the same system that executed the actions. For regulated environments -- federal agencies, financial institutions, organizations subject to the EU AI Act -- an auditor or examiner needs independent, cryptographic proof of what agents did. Internal logs alone do not satisfy the independence requirement.

SWT3 fills this gap by operating as an out-of-band witness layer that produces tamper-evident attestation records verifiable by any third party, without requiring access to the Cisco environment.

2. What SWT3 Witnesses

The following table maps Cloud Control concepts to the SWT3 procedures that independently witness them.

Each witness record produces an immutable SWT3 Witness Anchor with a SHA-256 fingerprint. These anchors are independently verifiable at sovereign.tenova.io/verify by any auditor, Notified Body, or C3PAO -- no Cisco infrastructure access required.

3. MCP Integration Pattern

Because Cloud Control is MCP-native, the SWT3 MCP server integrates directly as an additional MCP server in the architecture. There is no need for SDK wrapping, custom middleware, or code-level changes to your agents. The SWT3 MCP server (@tenova/swt3-mcp) registers its witness tools alongside Cloud Control's existing connectors, making them available to any agent in the environment.

Architecture

The MCP client configuration adds the SWT3 witness server alongside Cloud Control's existing MCP servers:

{
  "mcpServers": {
    "cloud-control-aws": {
      "command": "cloud-control",
      "args": ["--connector", "aws"]
    },
    "cloud-control-meraki": {
      "command": "cloud-control",
      "args": ["--connector", "meraki"]
    },
    "swt3-witness": {
      "command": "npx",
      "args": ["-y", "@tenova/swt3-mcp"],
      "env": {
        "SWT3_API_KEY": "axm_live_...",
        "SWT3_TENANT_ID": "YOUR_TENANT",
        "SWT3_AGENT_ID": "cloud-control-orchestrator",
        "SWT3_SIGNING_KEY": "your-signing-key"
      }
    }
  }
}

Once configured, agents can invoke witness tools directly through MCP tool calls. The SWT3 MCP server exposes 16 tools and 2 resources, including witness_inference, witness_tool_call, witness_chain, witness_access, and verify_anchor.

This pattern preserves Cloud Control's existing connector architecture while adding an independent compliance evidence layer that operates entirely out-of-band.

4. Procedure Cards

5. Quick Reference

6. Quick Start

Step 1: Run the SWT3 MCP Server

No installation required. The MCP server runs via npx:

npx -y @tenova/swt3-mcp

Step 2: Add to MCP Client Configuration

Add the swt3-witness entry to your MCP client configuration file alongside your existing Cloud Control connectors:

{
  "mcpServers": {
    "swt3-witness": {
      "command": "npx",
      "args": ["-y", "@tenova/swt3-mcp"],
      "env": {
        "SWT3_API_KEY": "axm_live_...",
        "SWT3_TENANT_ID": "YOUR_TENANT",
        "SWT3_AGENT_ID": "cloud-control-orchestrator",
        "SWT3_SIGNING_KEY": "your-signing-key"
      }
    }
  }
}

Step 3: Verify Integration

Once the MCP server is running, agents can discover and invoke witness tools through standard MCP tool discovery. Verify with the verify_anchor tool or at sovereign.tenova.io/verify.

Environment Variables

For a free trial account, visit sovereign.tenova.io/signup. An API key is generated immediately upon registration.

7. References

• SWT3 SDK Documentation -- Python, TypeScript, and MCP server reference
• UCT Registry -- Full procedure catalog with framework mappings
• Anchor Verifier -- Verify any SWT3 Witness Anchor by fingerprint
• Bidirectional Crosswalk JSON -- Machine-readable framework mappings
• OWASP MCP Top 10 Mapping -- MCP security risk attestation guide
• NSA MCP Security Mapping -- NSA guidance for MCP server hardening
• SWT3 Protocol Specification -- Full protocol reference