Friday, November 20, 2026

 





Core Architectural Layers & Responsibilities

1. Consumption & Agent Tier (Untrusted Reasoning Zone)

  • NLP / Agentic Clients: Conversational interfaces, Text-to-SQL planners, or multi-step reasoning agents.

  • Zero-Trust Assumption: Agents operate with no direct network path or static credentials to SQL databases or internal MCP endpoints. Every session carries a short-lived user/service identity token (via Equitus ICAM or enterprise IdP) asserting role, clearance/tenancy, purpose of use, and environment classification.










2. Fusion Secure Context Plane (SCP)

The SCP acts as both an MCP Gateway/Proxy and a Semantic & Policy Control Plane:

  • Identity & Context Binding (ICAM Integration):

    • Extracts user/agent attributes (Role, Org Unit, Security Clearance, Region/Data Residency) and binds them to an immutable session_context_id.

    • Prevents "confused deputy" attacks where a low-privilege user prompts a high-privilege agent into querying restricted tables.

  • Semantic Grounding & Context Assembly (Fusion + KGNN):

    • Maps natural-language business/mission terms to canonical entities and approved relationships rather than exposing raw physical table names.

    • Dynamically constructs a least-privilege context window: only schemas, semantic views, and MCP tool definitions permitted for that user's attributes are injected into the model's prompt/tool manifest.

  • Arcxa Governance, Risk & Lineage Engine:

    • Dynamic MCP Tool Filtering: Intercepts MCP tools/list and tools/call requests, stripping unauthorized tools and validating tool arguments against JSON-schema and policy rules.

    • Deterministic SQL Guardrails (AST Inspection & Rewrite): Parses agent-generated SQL into an Abstract Syntax Tree (AST) before execution:

      • Enforces read-only (SELECT) or approved stored-procedure execution.

      • Blocks SELECT *, cross-tenant joins, Cartesian products, and high-cost unindexed scans.

      • Injects mandatory row-level predicates (e.g., WHERE tenant_id = :ctx_tenant AND classification <= :ctx_clearance) and column-masking/redaction rules (PII, PCI, CUI) via Arcxa compliance tags.

    • Provenance & Lineage Ledger: Attaches Arcxa lineage metadata (query_id, policy version, source tables/documents, row counts, redactions applied) to every response payload so downstream answers remain fully auditable.




3. Execution & Data Plane (Enforced Isolation Zone)

  • Guarded MCP Servers: Domain-specific MCP servers (document stores, REST/ERP wrappers, knowledge graph tools) accept requests exclusively from the SCP mTLS service identity, propagating the signed user context header for downstream auditing.

  • SQL Query Firewall & Unified Views: Databases accept connections only from the SCP SQL Proxy using short-lived, scoped credentials. Queries target curated Fusion views or governed tables rather than raw staging schemas.


Stage

Component

Action Performed

Security / Value Outcome

1. Auth & Context

ICAM + SCP Gate

Validates user token and establishes

session attributes (role, clearance, tenant).

Blocks unauthorized sessions and

binds identity to all downstream hops.

2. Discovery

SCP + Arcxa

Filters available MCP tools and semantic

schema subsets for the active session.

Agent cannot see or invoke tools/tables

outside user policy; cuts prompt bloat.

3. Planning

NLP / LLM Agent

Generates candidate MCP calls and/or

SQL using only the scoped semantic schema.

Lower hallucination rate and

tighter schema accuracy.

4. Enforcement

Arcxa Policy Engine

Parses SQL AST, injects row/column

filters, validates MCP arguments,

checks risk score.

Prevents data exfiltration, SQL

injection, and cross-domain leakage.

5. Execution

SQL Proxy / MCP Server

Executes rewritten parameterized SQL

and approved MCP calls;

masks sensitive fields.

Deterministic, bounded performance

and strict least-privilege data access.





Wednesday, November 18, 2026

Equitus.ai Fusion AI -Secure Control Plane (SCP)









Equitus Fusion - Secure Context Plane (SCP)—modern enterprise AI governance architectures—acts as the centralized policy, security, and observability layer that sits between your users/applications, AI models, and enterprise data.




Security is provided by Fusion secure control plane which decides what systems are allowed to do, who has access, and how actions are logged and audited, while the data plane handles raw inference, model execution, and database retrievals.


____________________________________________________________________


Equitus.ai Fusion -Secure Control Plane (SCP) — For modernizing enterprise AI governance architectures— SCP acts as the centralized policy, security, and observability layer that sits between your users/applications, AI models, and enterprise data.


Enterprises Security Benefits from Implementing: SCP


  • Decouples Security from Application Logic: Developers don't have to hardcode safety checks, PII scrubbers, or access controls directly into every agent or application.

  • Prevents "Shadow AI": Centralizes visibility over all LLMs, external APIs, and internal knowledge sources being utilized across teams.

  • Ensures Compliance: Provides the verifiable evidence required by regulatory frameworks and internal risk teams regarding how AI handles sensitive data.










Equitus Fusion (sitting atop Equitus's data unification / knowledge graph layer) as a Security Control Plane (SCP) acting as a core gateway, security is enforced layer-by-layer at runtime rather than bolted on afterward.

Equitus.ai Fusion Secure Control Plane decides what those systems are allowed to do, who has access, and how actions are logged and audited.

While the data plane handles raw inference, model execution, and database retrievals.






Core Mechanics:  AI Security Control Plane (SCP) Centralizes 






Security Control Plane typically operates across five foundational pillars:
 

__________________________________________________________________



1. Identity & Context Binding

  • Identity: Ensures every user, application, or autonomous agent carries a verifiable, authenticated identity (often mapped via enterprise SSO).

  • Purpose: Rather than sharing generic API keys across multiple agents or services, the control plane ensures every action tracks back to a specific owner or process, binding permissions strictly to that context.

2. Runtime Policy Enforcement & Guardrails

  • Real-Time: Intercepts prompts, model responses, and tool calls in real time to enforce security compliance.

  • Identity Tests: It acts as an automated filter that scans for Personally Identifiable Information (PII), blocks data exfiltration attempts, stops indirect prompt injections, and restricts agents from interacting with unauthorized APIs or databases.

3. Least-Privilege Access & Tool Governance

  • Guard Rails: Limits what tools and systems an AI agent or model can invoke (such as Model Context Protocol servers or enterprise endpoints).

  • Strict Permissions: Instead of giving an agent broad, write-enabled access to systems of record, the control plane applies strict scope limitations—such as read-only access for lower-risk tasks or requiring explicit authorization for state-changing operations.

4. Human-in-the-Loop (HITL) Workflows

  • Human Oversight: Introduces safety checkpoints for high-risk or critical actions.

  • Human Approval: If an agent attempts an action with significant consequences (such as a financial transaction, code deployment, or database modification), the control plane pauses execution, routes the request to an authorized human approver, and resumes only upon approval.

5. Comprehensive Observability and Audit Trails

  • Lineage: Maintains a tamper-resistant record of every prompt, model response, tool invocation, and policy decision.

  • Mapping: It logs the entire lineage of an AI workflow so security and compliance teams can query past behavior, trace security incidents, and export telemetry directly into SIEM tools like Datadog or Splunk.


______________________________________________________________________


2. How Enterprises Use This Stack via Equitus Fusion SCP



Secure Context Plane



A. Secure Enterprise RAG and Text-to-SQL Analytics


  • Workflow: SCPs guard LLMs querying raw databases directly (which risks schema corruption, data leakage, or SQL injection), the LLM translates natural-language prompts into governed SQL statements.


  • Fusion + SCP Layer: Secure Prompts are routed through Equitus Fusion, which utilizes MCP servers to translate abstract requests into sanitized, read-only SQL queries targeting the unified knowledge graph or underlying enterprise databases.


  • SCP Enforcement: Security Control Plane inspects the generated SQL before execution. It ensures that user-level permissions (Row-Level Security / Column-Level Security derived from Active Directory) are dynamically appended to the query. SCP instantly blocks any query attempt to access restricted tables.


B. Multi-System Cross-Silo Orchestration


  • Complex Prompts: An enterprise user issues a complex prompt: "Find high-value accounts that haven't engaged in 90 days, check their inventory status in our ERP, and draft personalized re-engagement proposals."


  • Fusion + MCP Layer: Equitus Fusion maps the entities across disparate tools (CRM for engagement history, SQL database for inventory). The LLM orchestrates multiple specialized MCP tools in parallel to fetch data from these diverse sources.



  • SCP Enforcement: The Security Context Plane monitors the multi-step chain. It limits tool execution boundaries, ensures write actions (if any) require human-in-the-loop approvals, and strips out PII (Personally Identifiable Information) before text is fed back into external LLM context windows.


C. Traceable Audit Logging and Compliance


  • Provenance : Regulated enterprises (defense, finance, healthcare) require complete provenance for every AI decision.




  • Fusion + MCP Layer: Because MCP standardizes the communication format between the LLM and enterprise resources, every tool call, data fetch, and SQL payload leaves an explicit transaction footprint.



  • SCP Enforcement: The Security Context Plane logs every interaction into an immutable audit ledger. Enterprises can trace precisely which prompt triggered which SQL query, which resource was accessed, and what output was delivered to the user—satisfying strict data governance frameworks.











  Core Architectural Layers & Responsibilities 1. Consumption & Agent Tier (Untrusted Reasoning Zone) NLP / Agentic Clients: Conver...