How to Implement
SecuritySide provides TrustFactor as SaaS (Software as a Service), which is a model that enables users to access and utilize applications hosted on the cloud.
Cloud Models
TrustFactor is provided in two main ways:
- Shared Cloud: Through the TrustFactor App which is shared among customers.
- Private Cloud: Through the Customized Applications and choosing one or the other changes the level of access you have to the backoffice.
Throughout this documentation, we will mark the sections available only for "Private Cloud" customers with the "Private Cloud only" tag for clarity and simplicity.
Options | Shared Cloud | Private Cloud |
---|---|---|
Separation of Data | Logical | Physical |
Embedded Solution | ||
App Customization | ||
White Label | ||
Costs | $ | $$ |
Types of Integration
TrustFactor can be integrated with the client application via two ways:
1. Standalone Solution
- Pros
- Cons
Independence and Customization:
- Standalone solutions can be customized to a higher degree without affecting other systems
- Implementing new features without needing external systems
Deployment and maintenance:
- SecuritySide enables faster deliveries and updates by addressing issues in real time
- TrustFactor is typically easier to install, set up, and maintain, as it does not require integration with other systems
- No extra costs
Integration:
- Allows integration with the client's internal applications
- As it functions autonomously, which makes it more adaptable and straightforward to integrate with different platforms
Safety:
- The side app allows for greater security, as in the event of a cyberattack, it would require targeting two separate apps
Simplicity:
- They are usually simpler in design, focusing on a specific function or set of functions without dependencies
- In case something unexpected happens, you can always revert to the OTP
UI (User Interface):
- The same UI for all Clients
UX (User Experience):
- On mobile, for transaction validation, it is necessary to switch between the client application and TrustFactor, which may impact the fluidity of the user experience (minimized for Android, the usage is practically transparent for the user)
- Note for Internet Banking: there will always be two separate applications
2. Embedded
- Pros
- Cons
UI (User Interface):
- UI can be customized for different Clients
Integration and UX (User Experience):
- "Only one App" approach: Embedded solutions are designed to work within a larger system or environment, offering seamless integration and interoperability
- On mobile, as it is embedded in the Client App, the usage is practically transparent for the user
- Note for Internet Banking: there will always be two separate applications
Resource Efficiency:
- It uses resources more efficiently since they are tailored for specific tasks within a larger system
Independence and Customization:
- Embedded solutions can be more challenging to customize because they rely heavily on the host system
Maintenance, Integration and Deployment:
- The embedded solution may offer less flexibility and bug fixing challenges as well as new security issues as they rely on integration and a new version of the client application
- If not properly integrated, embedded solutions may cause compatibility problems or necessitate substantial modifications to the host system
- Higher costs to maintain
Safety:
- If the Client-App system does not have adequate protections, the embedded solution might be more vulnerable to attacks or unauthorized access, which could jeopardize overall safety
Choosing between standalone and embedded solutions depends on your specific needs, including:
- Integration requirements,
- Budget considerations, and
- System complexity
Standalone solutions are best suited for situations where independence, simplicity and low costs are essential. However, they may encounter challenges related to UX.
Embedded solutions, on the other hand, are effective in environments where seamless integration, resource efficiency and customization are priorities, but they might involve greater complexity and offer less flexibility.
TrustFactor SDK/API Integration
- TrustFactor provides a comprehensive SDK/API integration, allowing seamless integration with client applications
- This enables developers to incorporate TrustFactor's authentication capabilities into their existing systems, enhancing security without compromising user experience