SwivelSecure AuthControl Sentry

How does PINsafe^® work?

Each user is issued a PIN number – however, this exact PIN is never typed in.

When a user needs to securely authenticate, they’re sent a 10-digit security string – a random sequence of characters or numbers. The security string can be displayed as a graphic (TURing, PINpad® or PICpad) or sent via email or through SMS verification.

By using the PIN as a positional indicator, a one-time code for authentication can be extracted.

Can you show me an example?

The example above shows your PIN is 1370. On this occasion the security string is 5721694380, so your login code is 5240.

The security string can be integrated with many devices and applications, in a variety of ways for complete flexibility. Including:

- Logging into Windows
- Remote access with F5, Citrix Netscaler and Cisco VPN
- Web access with OWA, Apache, and Microsoft ILS

Authentication factors

Swivel Secure provides an extensive range of authentication factors to ensure each deployment provides maximum adoption across your whole organisation.

Whether you choose to authenticate by utilising the OTC on the mobile app, a traditional hardware token or even using your fingerprint, Swivel Secure’s AuthControl Sentry® provides ultimate security and configurability to suit your business’ security needs.

Simpler usability

Single sign-on (SSO) is designed to increase efficiency by allowing users to access all of their applications with a single successful authentication, through the risk-based policy engine. Whether users are accessing applications through a VPN, on-premise, or cloud, they will automatically be directed to authenticate using the single sign-on functionality within the Unified Portal.

Continuous security

Swivel Secure provides a unified portal to deliver frictionless access for your users. By using this single point of access, users’ privileges can be managed and behaviour can be tracked for auditing purposes, enhancing security and providing accountability.

Cost effective

Significant savings can be achieved by utilising SSO, as the necessity for password-related calls to IT support desks are eradicated. Productivity increases, where users are logging into one point to access all of their applications – saving time.

The cost of training is also minimised with a single process to authenticate, whether the user is accessing applications on-premise, through a VPN, or with cloud architecture.

Effortless management

As your business grows and additional applications are required to integrate into the business, they can easily be accessible to users with access authenticated through a single portal.

Privileges can be effortlessly managed and risk-based authentication enabled to ensure policy settings are configured to apply the appropriate level of authentication, per user, per application.

Risk-based authentication

Risk-based authentication (RBA) is a dynamic feature of AuthControl Sentry®, designed to automatically request the appropriate level of authentication to access applications, whether the user is connecting through a VPN, cloud, or on-premise. Based on parameters set in the policy engine, RBA will request the appropriate level of authentication to access applications based on the user, their device and the application.

Ultimate flexibility & control

RBA enables you to set the appropriate risk required for an individual or group to access particular applications. Using a predefined set of parameters, it works for you and decides what level of authentication is required, based on criteria including but not limited to:

- What applications they are trying to access
- What group membership they do have
- Where they are accessing the applications from
- What device they are using

The policy engine

Based on a points system, the adaptive authentication policy engine enables administrators to set parameters per user, per application.

Parameters include:

- Group membership
- Application being accessed
- IP address
- Last authentication
- X509 Cert
- Device
- Physical location (GeoIP)
- Time / date / day

The Policy engine allows you to create new rules and combine existing rules, as well as provide a mechanism to support a range of scenarios with increasing complexity.

Effortless management

Everyone is different and with a range of authentication factors to authenticate access to applications, administrators can select the factors that are suitable for their organisation.

Authentication factors include:

- Mobile app
- SMS
- Fingerprint
- Image authenticators: TURing & PINpad
- Hardware token

Risk-based authentication: Example 1

The Purchasing Assistant has flown to South East Asia to visit a supplier with the Purchasing Manager. She has just finished a meal in a restaurant and realises she forgot to check the stock of some components for a meeting the following day. While waiting for the taxi, she thought she’d quickly log in to the ERP system, using her company-issued mobile device.

Result - unsuccessful

Although she is trying to use a company-issued device to access the ERP, the IP range sets her back -100 points because of her location. She will not be granted access to the ERP this time, independently of her willingness to use multi-factor authentication.

Risk-based authentication: Example 2

The Sales Manager is working in the office today and wants to access the CRM to create an opportunity following a meeting. He is using his company-issued laptop and is accessing the application which is located on-premise.

Result – successful

The Sales Manager clearly exceeds to points he needs to access the CRM. Once he is authenticated, he can use single sign-on (SSO) to access other applications. He receives a call from the Purchasing Assistant and is able to access the ERP system, and provides the quantity with the part number he is given.