Core Capability
Map
Know what your agents can touch — and flag the combinations that should never exist.
Overview
Once agents are discovered, SinzAI Map builds a complete topology of what data each agent can access. It classifies every data store by sensitivity, regulatory regime, and region — then cross-references agent access against these classifications to surface "toxic combinations" where unverified or low-trust agents can reach sensitive data.
Map operates continuously. As data stores are added, as agent scopes change, and as classifications are updated, the topology is recalculated in near real-time. A toxic combination alert fires the moment a dangerous access pattern emerges — not during the next audit cycle.
Data Store Classification
SinzAI classifies every connected data store across three dimensions:
Sensitivity
- Public
- Internal
- Confidential
- Restricted
- PII
- PHI
- PCI
Regulatory Regime
- GDPR
- CCPA/CPRA
- HIPAA
- SOX
- PCI DSS
- FedRAMP
- None
Region
- US East/West
- EU (Frankfurt/Ireland)
- APAC (Singapore/Tokyo)
- GovCloud
Toxic Combination Alerts
A "toxic combination" occurs when an agent with insufficient trust or verification can reach data that its classification does not permit. SinzAI defines toxic combinations as rule triplets: (agent_trust_level, data_sensitivity, action_type).
| Agent Trust | Data Sensitivity | Action | Result |
|---|---|---|---|
| < 50 | PII / PHI / PCI | Read | 🚫 Block + alert |
| 50–74 | PII / PHI / PCI | Read | ⚠️ HITL gate |
| < 75 | Confidential | Write | 🚫 Block + alert |
| Any | Restricted + GDPR | Write (cross-region) | 🚫 Block + alert |
| Unverified | Any | Any | 🚫 Block + alert |
Continuous Reclassification
Map is not a point-in-time snapshot. When a data store's classification changes, when an agent's trust score moves, or when a new regulation takes effect, the topology recalculates. Toxic combination alerts fire immediately — and if a previously blocked combination becomes safe, access is automatically restored (subject to HITL gates if configured).