Cloud/AI Governance/Security Posture
Security Posture
The firewall report of your fleet: every request inspected, every DLP redaction and FinOps truncation counted, the compliance coverage of your policies scored, and the blind spots named server by server.
Security Posture answers the question an auditor will ask you: what exactly is inspecting my AI traffic, and how much of the fleet does it cover? Every request that crosses Vinkius passes the firewall, and this screen counts what the firewall did: redactions, truncations, bytes kept away from upstream APIs, and the servers where policies are not yet on. The console's own line: "Know your blind spots before they become incidents. Threat interceptions, policy coverage, and compliance readiness scored and explained."
Security Posture
Know your blind spots before they become incidents. Threat interceptions, policy coverage, and compliance readiness scored and explained.
Firewall Activity
Daily DLP and FinOps enforcement actionsEnforcement by MCP Server
Firewall activity and active policies per server| MCP Server | DLP | Requests | DLP Events | FinOps Events | Bytes Saved |
|---|---|---|---|---|---|
| GitHub | 1,842 | 84 | 31 | 2.1 MB | |
| Slack | 1,204 | 61 | 24 | 1.4 MB | |
| Notion | 986 | 52 | 18 | 1.1 MB | |
| Linear | 842 | 47 | 16 | 0.9 MB | |
| Jira | 764 | 43 | 15 | 0.8 MB | |
| Stripe | 691 | 38 | 0 | 0.7 MB | |
| HubSpot | 578 | 22 | 14 | 0.6 MB | |
| Vercel | 412 | 0 | 0 | 0.4 MB |
The mockup runs on the console's Sample Data. On a paid plan the same screen reports on your live traffic, per organization.
The firewall scoreboard
Four cards, one story:
- Firewall Events with the requests inspected behind it: enforcement actions out of total traffic. The firewall saw everything; this is what it did about it.
- DLP Redactions with their share of firewall events on a progress bar: sensitive data caught and redacted before leaving your perimeter.
- FinOps Truncations with their share: oversized payloads cut down to size before they were paid for.
- Data Protected in bytes, against the total processed volume. That ratio is the firewall working at a glance.
Compliance Coverage: the ring that names your blind spots
The ring scores policy coverage across the fleet with the three levers: DLP, FinOps and Approval, each as active servers out of total. In the sample above, DLP covers 6 of 8 servers, FinOps 5, Approval 3. The gap in the ring is not decoration: it is the list of servers where a policy is off, and the table underneath names them one by one. In the sample, Vercel runs with everything off: a red flag you can see from across the room, before it becomes an incident.
The enforcement strip and the timeline
Three numbers complete the picture: Enforcement Rate (events per request), Requests Inspected (all traffic goes through the firewall, no exceptions) and Payload Volume (the total data inspected). The Firewall Activity chart plots the daily DLP and FinOps actions over the period, so a spike in redactions reads as a story: something started shipping sensitive data through that Connector.
Enforcement by MCP Server
The closing table is the checklist: one row per Connector with a check or cross for DLP and FinOps, the requests it handled, its DLP Events and FinOps Events in amber the moment they exist, and the Bytes Saved the enforcement produced. It is the console's own blind spot list: any cross in the policy columns is a server you forgot to protect, and the row next to it tells you how much traffic it carries. Clicking a row opens that server's detail; the empty state is the console's own: "No security data recorded in this period."
From report to control
Reading about coverage is step one; changing it is the Settings group next door. DLP Protection turns redaction into rules, FinOps Guard turns truncation into policy, Connector Policy and Circuit Breaker decide what a server may do and when it gets shut off. The Reports screen shows the gap; the Settings screens close it.