SYNEDAT® · Swissbit
Swissbit – Hardware-backed authentication
SYNEDAT plans Swissbit iShield Key for sign-in using physical security keys. We check services, devices and user groups and connect deployment with issuance, replacement and revocation.
Which product family fits your needs?
Swissbit iShield Key 2
Select USB and NFC variants for devices and services. SYNEDAT checks supported sign-in methods and actual workplace use.
Swissbit iShield Key Manager
Fit administration and key state handling into support. We plan roles, secure handover and documented replacement procedures.
License scope, availability, term and support are reviewed for your project and specified in the quote.
Where the solution adds value
Strengthen administrative account access
SYNEDAT tests key administration services with a pilot group. Registration, daily sign-in and recovery are verified with account owners.
Organize key issuance
We define assignment, onboarding and spare keys. A traceable workflow supports revocation of lost keys and assistance for new users.
What matters when choosing
- Identities and privileges
- Employees, administrators, service accounts and partners have different access needs. We define roles and approvals for the relevant systems.
- Protocols and devices
- FIDO2, certificates, SAML or RADIUS must fit the application. For security keys, USB connectors, NFC and supported platforms also matter.
- Lifecycle and recovery
- We plan issuance, enrollment, loss, revocation and emergency access. This simplifies rollout and avoids unresolved exceptions during operations.
From selection to deployment
Define requirements and objectives
We review systems, users, security requirements and budget. The result is a reasoned selection with a defined scope.
Validate suitability in a pilot
For an agreed pilot, we define tests, acceptance criteria and responsibilities. You receive a documented basis for the investment decision.
Plan rollout and operations
We plan migration, configuration, handover and support together. Scope and responsibilities are agreed before rollout.
Downloads and manufacturer information
Explore your options with the linked service overviews and manufacturer documents. The language shown refers to each document.
-
Swissbit iShield Key 2 – Brochure (PDF)
English
Open PDF: Swissbit iShield Key 2 – Brochure (PDF) (English) ↗
Questions to help you decide
Does a security key work with every application?
Applications must support and enable a compatible method. SYNEDAT checks service, browser, operating system and key variant together.
What happens if a key is lost?
The lost key is revoked in affected services. A preconfigured spare or recovery procedure enables controlled access restoration.
How do MFA and privileged access management differ?
MFA strengthens sign-in with additional factors. PAM controls privileged permissions, credentials and, where supported, sessions. They can complement each other and are planned around your applications.
How do we start using security keys?
We first check applications and identity providers. A pilot group tests sign-in, spare keys and recovery. Issuance, enrollment and support can then be standardized for more users.
Can I request a demo or pilot first?
Yes. Tell us your intended use case. We will discuss available evaluation options, prerequisites, effort and acceptance criteria. A pilot is agreed separately before it starts.
What does SYNEDAT need for a quote?
Useful details include product family, deployment location, current systems, user or device count and target date. We clarify open points together and distinguish the product, implementation and ongoing services in the quote.
Can SYNEDAT help with rollout and ongoing operations?
We agree the services you need, such as architecture, integration, migration, documentation or operational support. Vendor support, response times and ongoing assistance are explicitly defined in the agreed scope.