An original cinematic control room: a male supervisor and human analysts oversee three AI robots and a panoramic cybersecurity monitoring wall.

TUCANA SHIELD / HUMANS + AI. API SECURITY IN VIEW.

Your APIs.
A clearer view.

Behind every API, there are people.

Skip introduction ↓

INTRODUCTION / 01 OF 05Illustrative scenario

↗ Explore workflow

INSPECT THE BOARD

Interactive API security concept. Fictional requests; no customer gateway connected. Coverage details ↗

CALL · CHAT · VOICE

Three services.
One clear overview.

Read what each prepared connector can show, what stays in the source service and what still needs activation.

PHONE · SIGNAL · CONTEXT

Phone service visibility

VI1 Call

See how your phone service is performing without exposing call content in your security dashboard.

Read-only · activation pending

Explore VI1 Call

CONVERSATION · SCOPE · CONTEXT

Communication activity summaries

VI1 Chat

Bring a bounded view of communication activity into the same organization workspace.

Read-only · activation pending

Explore VI1 Chat

VOICE · USAGE · CONTEXT

Voice usage visibility

VoxVain

Review the voice-service usage recorded for your account alongside your other service summaries.

Read-only · activation pending

Explore VoxVain

View all integrations Follow the workflows

LIVE CONNECTION STATUSREAL SERVICE CHECKS · NO CUSTOMER RECORDS

CONNECTING

Current service health

Loading the latest read-only checks…

Waiting for a timestamped observation

Customer workspace—Check duration unavailable

Pilot inquiry service—Check duration unavailable

Recent service checks

Only actual observations appear here.

Health checks describe these services. Customer API request and blocked-attack counters are not connected.Open Grafana ↗

01 / YOUR APIs IN VIEW

Every API connection.
Part of the same mission.

Step inside the Tucana Shield view. Explore API routes, caller identities, and request decisions as one connected environment.

TUCANA SHIELD / API COMMANDINTERACTIVE CONCEPT

ILLUSTRATIVE CONCEPTYour world. Our field of view.

TUCANA SHIELD / HUMAN JUDGMENT + AUTOMATED VIGILANCE

01API inventory↗02Caller identity↗03Request evidence↗

Human review hours require an agreed service scopeExplore the complete workflow ↗

02 / THE PROTECTION LAYERS

Inspect the layer.
Understand its purpose.

Open the platform

PLATFORM / SELECT A LAYERPROPOSED CAPABILITIES

DISCOVER / API SECURITY

Know every route. See every change.

Organize observed API routes, methods, owners and schema changes into an inventory your team can inspect.

Explore this protection layer ↗

Gateway metadata · OpenAPI contracts · schema comparison

ILLUSTRATIVE CONCEPTAPI inventory / evidence in context

TUCANA SHIELD / HUMAN JUDGMENT + AUTOMATED VIGILANCE

COLLECT → CONTEXT → REVIEWExplore the technology and charts ↗

03 / INSIDE THE ANALYST’S SCREEN

More than a signal.
A story you can inspect.

Select a sample investigation, filter the charts, and open a record. Every number belongs to a clearly labeled fictional example.

API authorization / ANALYSIS WORKSPACEFICTIONAL DATA

EXPLORE THE EXAMPLE

Identity, tenant and operation context

Original Tucana Shield demonstration · synthetic records, not customer or vendor statistics.

Observation timeline

SAMPLE REQUESTS

AllowDenyReview28 fixed example records · no live traffic

Review state

p50 31 msp95 75 msTenants 2

Evidence categories

Evidence records

28 visible records

View the chart data and definitions

Filtered fictional API requests
Sample day / time	Tenant	Route	Decision / HTTP	Latency	Reason
Day 1 09:00:00	tenant_northstar	GET /v1/orders/{id}	Allow / 200	16 ms	Verified caller and permitted operation
Day 1 10:07:13	tenant_harbor	GET /v1/orders/{id}	Allow / 200	25 ms	Verified caller and permitted operation
Day 1 11:14:26	tenant_northstar	POST /v1/orders/{id}	Deny / 403	20 ms	Object belongs to another tenant
Day 2 12:21:39	tenant_northstar	GET /v1/orders/{id}	Allow / 200	45 ms	Verified caller and permitted operation
Day 2 13:28:52	tenant_harbor	GET /v1/reports	Review / 200	33 ms	Ownership exception needs review
Day 2 14:35:05	tenant_northstar	POST /v1/orders/{id}	Allow / 200	20 ms	Verified caller and permitted operation
Day 2 15:42:18	tenant_northstar	GET /v1/orders/{id}	Deny / 403	57 ms	Object belongs to another tenant
Day 2 16:49:31	tenant_harbor	POST /v1/agent/tasks	Allow / 200	25 ms	Verified caller and permitted operation
Day 3 09:56:44	tenant_northstar	GET /v1/orders/{id}	Allow / 200	42 ms	Verified caller and permitted operation
Day 3 10:03:57	tenant_northstar	GET /v1/orders/{id}	Deny / 403	25 ms	Object belongs to another tenant
Day 4 11:10:10	tenant_harbor	POST /v1/orders/{id}	Allow / 200	75 ms	Verified caller and permitted operation
Day 4 12:17:23	tenant_northstar	GET /v1/orders/{id}	Review / 200	22 ms	Ownership exception needs review
Day 4 13:24:36	tenant_northstar	GET /v1/reports	Allow / 200	31 ms	Verified caller and permitted operation
Day 4 14:31:49	tenant_harbor	POST /v1/orders/{id}	Deny / 403	26 ms	Object belongs to another tenant
Day 4 15:38:02	tenant_northstar	GET /v1/orders/{id}	Allow / 200	49 ms	Verified caller and permitted operation
Day 4 16:45:15	tenant_northstar	POST /v1/agent/tasks	Allow / 200	37 ms	Verified caller and permitted operation
Day 5 09:52:28	tenant_harbor	GET /v1/orders/{id}	Deny / 403	26 ms	Object belongs to another tenant
Day 5 10:59:41	tenant_northstar	GET /v1/orders/{id}	Allow / 200	63 ms	Verified caller and permitted operation
Day 5 11:06:54	tenant_northstar	POST /v1/orders/{id}	Review / 200	31 ms	Ownership exception needs review
Day 5 12:13:07	tenant_harbor	GET /v1/orders/{id}	Allow / 200	46 ms	Verified caller and permitted operation
Day 6 13:20:20	tenant_northstar	GET /v1/reports	Deny / 403	31 ms	Object belongs to another tenant
Day 6 14:27:33	tenant_northstar	POST /v1/orders/{id}	Allow / 200	79 ms	Verified caller and permitted operation
Day 6 15:34:46	tenant_harbor	GET /v1/orders/{id}	Allow / 200	26 ms	Verified caller and permitted operation
Day 7 16:41:59	tenant_northstar	POST /v1/agent/tasks	Deny / 403	37 ms	Object belongs to another tenant
Day 7 09:48:12	tenant_northstar	GET /v1/orders/{id}	Allow / 200	32 ms	Verified caller and permitted operation
Day 7 10:55:25	tenant_harbor	GET /v1/orders/{id}	Review / 200	55 ms	Ownership exception needs review
Day 7 11:02:38	tenant_northstar	POST /v1/orders/{id}	Allow / 200	43 ms	Verified caller and permitted operation
Day 7 12:09:51	tenant_northstar	GET /v1/orders/{id}	Deny / 403	30 ms	Object belongs to another tenant

Each row is one synthetic observation. Counts change with the selected period, category, and review state. A recorded observation is not a blocked attack or a protection score.

No live systems connectedOpen the full technology view ↓

This example presents our fictional API records in a Grafana-inspired layout. Your signed-in portal uses real Grafana-rendered views of authorized recorded outcomes; this public preview is not a live Grafana embed.

Open customer dashboard Public service-health dashboard ↗Read the feature guide ↗

Follow a guided investigation How to read our demonstrations ↗

04 / ONE WORKSPACE FOR EACH RESPONSIBILITY

The operation.
Every detail in view.

Explore the private workspace preview. Switch roles and open sample records to see what each area is for.

TUCANA SHIELD / PRIVATE WORKSPACE PREVIEWSYNTHETIC RECORDS

NORTHSTAR / SAMPLE ORGANIZATION

A clearer view of your records.

PREVIEW

Account required for private records

05 / FROM EVIDENCE TO ACTION

Review the facts.
Agree the next step.

The interactive screens use fictional records. Real service summaries appear only after their source is connected and validated. A dashboard does not create permission to act.

OBSERVE → REVIEW → AUTHORIZE → VERIFY

A clear path, with clear limits.

Understand the role of VI1 Call, VI1 Chat and VoxVain. Learn what each read-only connector can show and which actions stay in the source service.

Explore the workflow Read the feature guide

06 / OPEN TECHNOLOGY. THE TUCANA SHIELD VIEW.

Explore the engines.
Stay inside the experience.

What open source means

01 / TECHNOLOGY

Environment-dependent

Cilium

Network context and enforcement

Capabilities, charts & evidence ↗

02 / TECHNOLOGY

Integration target

Redpanda

Asynchronous event transport

Capabilities, charts & evidence ↗

03 / TECHNOLOGY

Integration target

ClickHouse

API evidence analytics

Capabilities, charts & evidence ↗

04 / TECHNOLOGY

Integration / staged

Akto

API discovery and security testing

Capabilities, charts & evidence ↗

05 / TECHNOLOGY

Lab prevention verified / production staged

open-appsec

Inline request inspection

Capabilities, charts & evidence ↗

See the connected architecture

API-focused components with distinct licenses and deployment requirements. Optional and archived components are labeled; architecture is not proof of a live connection.

07 / YOUR NEXT SECURITY DECISION

A briefing for every next step.

Open the intelligence library

01 / ASSESS

Your environment. A clearer picture.

API routes, application owners, gateways and the boundaries between customers.

Open this briefing ↗

02 / AUTHORIZE

Who makes the next move?

Define who receives a finding, approves a response, and owns recovery.

Open this briefing ↗

03 / SCOPE

Know what your coverage includes.

Scope API traffic, environments, evidence retention and authorized response.

Open this briefing ↗

YOUR NEXT MOVETUCANA SHIELD / API PILOT

PUT YOUR API ON THE BOARD

Build a clearer
line of defense.

Define your API surface, your priorities, and who can authorize the next step.

Request an API pilot Scope your API coverage

YOUR APIs. YOUR IDENTITIES. YOUR SCOPE. ↗

Your APIs. A clearer view.

Three services.One clear overview.

VI1 Call

VI1 Chat

VoxVain

Current service health

Every API connection.Part of the same mission.

Inspect the layer.Understand its purpose.

Know every route. See every change.

More than a signal.A story you can inspect.

Identity, tenant and operation context

Observation timeline

Review state

Evidence categories

Evidence records

The operation.Every detail in view.

A clearer view of your records.

Review the facts.Agree the next step.

A clear path, with clear limits.

Explore the engines.Stay inside the experience.

Cilium

Redpanda

ClickHouse

Akto

open-appsec

A briefing for every next step.

Your environment. A clearer picture.

Who makes the next move?

Know what your coverage includes.

Build a clearerline of defense.

Your APIs.
A clearer view.

Three services.
One clear overview.

Every API connection.
Part of the same mission.

Inspect the layer.
Understand its purpose.

More than a signal.
A story you can inspect.

The operation.
Every detail in view.

Review the facts.
Agree the next step.

Explore the engines.
Stay inside the experience.

Build a clearer
line of defense.