Reviewed 22 October 2026 · Customer portal email metadata and finding summaries are available. Zero authorized live mailboxes; live ingestion remains pending. The demo uses illustrative data.
THE SAME COMMAND ROOMA new signal to investigate.API + EMAIL / A SHARED SECURITY DIRECTION
FOLLOW ONE MESSAGE
From arrival to a clear finding.
Choose a sample and step through the proposed experience. This is an illustration, using invented messages and chart data.
EMAIL SIGNAL / INTERACTIVE DEMONSTRATIONILLUSTRATIVE DATA
✉↗⌕↗◇↗◎
01 / CONNECTION
Begin with the right mailbox.
The connector checks the account identity before requesting message data. A live connection needs an owner-approved, read-only authorization.
Live authorization pending
Automatic checks → understandable evidence → human decisionMONITOR & REVIEW PILOT
WHAT WE ARE BUILDING
Useful signals. Visible limits.
Detection should explain what it found—and what it could not inspect.
✉
MESSAGE ANALYSIS
Inspect the content.
Locally qualified Rspamd checks produce test message findings. Production scanners are not installed; online reputation and sender-authentication validation still need connected configuration.
Local engine checks qualified⌕
ATTACHMENT ANALYSIS
Look inside the file.
Local ClamAV tests scan decoded attachment content. Encrypted, unsupported, or over-limit content is marked incomplete so it cannot appear fully inspected.
Harmless test fixtures verified◎
REVIEW & CONTROL
Make the finding clear.
The customer portal includes read-only email metadata, recorded connection checkpoints and finding summaries. A recorded checkpoint does not establish current connectivity. Live case routing and mailbox response remain pending.
Portal summaries available
MAILBOX CONNECTIONS
Start with the services your team already uses.
API-based access, granted to the right account. Each provider has its own permissions and coverage limits.
G
Gmail / Google Workspace
Read-only connector and history processing tested with simulated provider responses. Live authorization, token lifecycle and operational validation are still required.
Activation pending
Z
Zoho Mail
Read-only, region-aware connector tested locally. Account permissions, mailbox observation coverage and continuous operation need live validation.
Activation pending
CURRENT READINESS
Know what is ready.
Last reviewed 22 October 2026. Portal availability and local test results do not establish live mailbox protection or measured detection accuracy.
Email pilot coverage and remaining work
Capability
Status
Meaning for your team
Message and attachment scanning
Tested locally
Harmless fixtures exercised the actual engines. Production scanners and mailbox workers are not installed.
Gmail and Zoho read-only clients
Tested locally
Identity binding and error handling checked with simulated responses.
Live mailbox ingestion
Zero authorized mailboxes
No live ingestion. Provider authorization, production workers and end-to-end validation remain pending.
Customer portal email summaries
Portal summaries available
Read-only metadata, recorded checkpoints and finding summaries are available. Current provider connectivity and live findings remain unverified.
Automatic email quarantine
Off
No mailbox changes are performed by this pilot.
A FEW CLEAR ANSWERS
Before you connect.
Does this replace API protection?
No. API security remains the core focus. Email detection extends that direction through scoped mailbox APIs, with a shared approach to identity, findings and review.
Does “no escalation” mean a message is safe?
No. It means the checks performed did not raise that finding. Detection has limits; an incomplete scan remains incomplete even when no alert is produced.
Are you monitoring my mailbox already?
No. This public experience uses illustrative data. A mailbox is connected only after its specific authorization and deployment are verified.
Can Tucana Shield remove suspicious email automatically?
The current email pilot does not modify mailboxes. Quarantine would require a separate authorized integration, tested recovery and a clearly defined response policy.
API FIRST. MORE SIGNALS IN VIEW.
Bring your email into the conversation.
Define the mailboxes, review responsibilities and evidence you need for a focused pilot.
The demo uses synthetic messages and charts. Your customer portal shows recorded email metadata. Current provider connectivity requires validation. Discuss a focused pilot.