User verified
Identity from your organisation’s directory, with optional multi-factor authentication.
ZAFEPASS · ZAFEMESSENGER
Every system, its own island.
ZafePass opens a path to one system, for one user, only while it is needed, then closes it again. Nothing else on the network is visible. Source ↗
Kastro is an independent Icelandic technology company and your first local point of contact. ZafePass and ZafeMessenger are developed by Zafehouze Solutions ApS, Denmark.
ILLUSTRATION · ACCESS MODELONE SERVICE OPEN
01 USERSCADA service providerIdentity verified
02 DEVICEApproved supplier computerApproved
Internal applicationsNOT VISIBLE
Industrial controlsPATH OPEN
Shared filesNOT VISIBLE
The supplier reaches one industrial control system, at an agreed time. Nothing else on the network is visible. Illustration, not a screenshot of the software.
01 — THE PROBLEM
A VPN lets people onto the network. Usually they only need one system.
A supplier with VPN access is on your network. ZafePass instead opens a path to the one service they are entitled to, only while the application is open.
VPN
The user is inside the network. Everything there can be seen and approached.
ZAFEPASS
One service is reachable. The rest is invisible, according to the manufacturer.
A simplified illustration. The scope of VPN access depends on its configuration.
Device approved
Unknown devices are queued. The device’s environment forms part of the policy.
Access limited
A path to one service, open while the application is in use. Then it closes.
02 — TWO PRODUCTS
Access and communication are different jobs. Start with the one that matters to you.
ZafePass
Access to one system at a time, only while it is needed.
Service-level access, hidden services, separate gateways for each site, and applications that arrive and leave as needed.
Explore ZafePassZafeMessenger
Conversations and files on your servers. You decide who sees what and how long it is kept.
Retention per channel from nothing to indefinitely, invisible private channels, and guests who only see what they are invited into.
Explore ZafeMessenger03 — SCENARIOS
Start with the work.
A · ZAFEPASS
Suppliers and contractors
The supplier reaches one system, at an agreed time, from an approved computer, and every connection is logged.
B · ZAFEPASSIndustrial controls and remote sites
Pumping stations, substations, and processing plants around the country, each one its own island.
C · ZAFEPASSRemote work and travel
The laptop holds nothing. Applications arrive when needed and disappear afterwards.
D · MESSENGERConfidential leadership conversations
A channel no one else can see, and a conversation that is not retained unless you choose.
E · MESSENGERClient conversations
The client talks to their adviser, and sees nothing else.
Scenarios based on manufacturer descriptions, not customer stories. ZafePass ↗ · ZafeMessenger ↗
04 — DEPLOYMENT
Your environment. Your keys.
- WHERE
- Software only, in your own environment or a cloud you control. No dedicated appliance.
- KEYS
- The manufacturer states that each installation generates its own keys, without PKI or X.509, and Zafehouze has no access. Source ↗
- LOGGING
- Each connection can be logged and sent to your SIEM. Who accessed what, and when.
No solution is unbreakable, and we won’t claim otherwise.
We explain how this one works, link to the manufacturer’s sources, and help you assess it in your own context.
WHO’S SPEAKING
Kastro is an independent Icelandic technology company. ZafePass and ZafeMessenger are developed and owned by Zafehouze Solutions ApS, Denmark. Capability descriptions are based on manufacturer information, with sources linked.
How we get started →Let’s find out together whether this fits.
A short conversation with Kastro · nothing is sent automatically