Requests inspected in 24 hours
YOUR AI SECURITY AT A GLANCE
Protection overview
Understand what CyberPass protected, what needs attention and whether every control is working.
Blocked or redacted 0%
Security events awaiting review
Approved identities using Gateway
What CyberPass did
Waiting for security activity.
What needs attention
Checking open security work.
Latest protection decisions
No events recorded yet.
Finish protection setup
AI ACTIVITY
How AI is being used
See volume, protection actions and routes without exposing prompt or response content.
Inspected by CyberPass
0% of activity
Sensitive values removed
Gateway policy latency
Protection activity
Waiting for security activity.
Protected channels
No channel activity yet.
Recent policy triggers
No policy triggers yet.
Recent AI activity
Waiting for Gateway traffic.
INCIDENTS & EVENTS
Understand and resolve security activity
The attention queue highlights blocked, redacted, high-risk and actively investigated events. Routine allowed traffic remains in All activity.
All recorded decisions
Risk score 60 or above
Open security work
Closed investigations
No matching events.
ENTERPRISE CONNECTIONS
Identity, trust & SIEM
Configure reusable protocol adapters once per organization. Customer URLs, certificates, credentials and role mappings stay in tenant-scoped records.
Identity providers
No enterprise identity provider configured.
Trust bundles
System trust store only.
Secret storage
Checking encryption configuration.
SIEM destinations
No SIEM destination configured.
CONTROLLED TOOL EXECUTION
MCP Firewall
Register Streamable HTTP servers once, expose only approved tools and require analyst approval for sensitive actions.
Server registry
No MCP servers configured.
Policies
No tool policies configured.
Pending approvals
No pending approvals.
Recent tool calls
No MCP traffic recorded.
Arguments and tool outputs are inspected in transit but are not stored. Audit records keep names, decisions and SHA-256 argument fingerprints.
MODELS & ROUTES
Control where AI requests go
Applications use stable CyberPass model names. Policies decide whether each request stays private, reaches an approved public provider or is stopped.
Application asksUses a stable model alias
CyberPass decidesChecks data, risk and policy
Approved model answersChecking configured routes…
Inference endpoints
No providers configured.
Stable model aliases
No model aliases configured.
SECURITY POLICIES
Decide what CyberPass should do
One active policy controls sensitive data, suspicious AI instructions, file inspection, approved models and usage limits.
ACTIVE PROTECTION
Checking policy…
Loading the rules currently applied to live traffic.
Allow, remove protected values or stop the request.
Observe risk signals or block at a chosen threshold.
Limit formats and size, then inspect contents in memory.
Policy versions
No policy versions configured.
SENSITIVE DATA (DLP)
Know what information is protected
CyberPass finds defined sensitive values before they leave an approved application. It can remove them, block the request or record the decision according to policy.
National identifiers, bank accounts and contact data.
API keys and cloud credentials.
Organization dictionaries and safe patterns.
Inspection rules
Loading detectors.
PROTECTED DEVICES
See where endpoint protection is working
Each Windows device reports the Connector, tray application and managed browser extension separately, so missing coverage is easy to spot.
Known endpoints
Connector, tray and extension online
Missing or stale component
Managed connectors
No endpoint devices enrolled.
Connector listens on 127.0.0.1 only. Browser protection inspects text and supported files before submission; direct egress controls remain a customer firewall/MDM responsibility.
Pending installations
No enrollment tokens created.
IDENTITY FOUNDATION
Users & application access
Human access is role-based. Applications authenticate with scoped, revocable keys.
Organization members
Sign in to load members.
Service accounts
Sign in to load service accounts.
AI THREAT GUARD
Understand suspicious instructions
CyberPass combines explainable signals into a risk score. The active policy decides whether to observe the request or stop it.
Signals for instruction override, hidden context requests and role confusion.
Signals for secret disclosure, system-prompt extraction and credential requests.
Signals that attempt to force commands or unsafe tool behavior through text.
DECISION MODEL
Signal → score → action
Guard does not promise perfect detection. Every matched signal is recorded with the request metadata so an analyst can understand why CyberPass observed or blocked a request.
SAFE VALIDATION
Test lab
Validate text, file and policy behavior with synthetic data. Tests do not call an upstream model.
DLP inspection
Check built-in and organization detectors, see matched rules and preview redaction.
File inspection
Extract and inspect a supported synthetic document with the active file policy. Contents are processed in memory and are not stored.
Policy simulation
Test a specific immutable policy version and model alias before activation.
Use synthetic data only.Do not paste real customer, payment or production secrets into the lab.
SYSTEM HEALTH
Is CyberPass ready to protect traffic?
Runtime components show what is online. Readiness checks show what must be configured before the full protection path is usable.
Components
Control APIConnecting
—GatewayRuntime available
READYPublic providerNo external route
OFFEvent storeMetadata only
READYPilot readiness
Checking pilot readiness.
ORGANIZATION SETTINGS
Security data
Control the retention period for minimized security-event metadata.
Event retention
Prompt and response content is not stored in the current metadata-only mode.