6 posts tagged with "Integrations"

XFA can be used as a factor through the BYO MFA functionality in OneLogin. This allows XFA to be seamlessly added to any application from within the OneLogin admin dashboard, given that it uses OneLogin as the identity provider.

When a user authenticates with OneLogin, as an additional factor after supplying a username & password, the user is redirected to XFA to verify that the device is compliant with the device security policy before authenticating the user. This assures that only devices that comply with the security policy are allowed access.

XFA can be used as a factor through the External Authentication Methods functionality in Microsoft EntraID. This allows XFA to be seamlessly added to any application from within the Microsoft EntraID admin dashboard, given that it uses EntraID as the identity provider.

When a user authenticates with EntraID, as an additional factor after supplying a username & password, the user is redirected to XFA to verify that the device is compliant with the device security policy before authenticating the user. This assures that only devices that comply with the security policy are allowed access.

XFA is now a Vanta Partner!

You can use XFA to provide device security proof automatically for your compliance needs, pushing updates regularly to Vanta.

Get started in the Vanta Dashboard under Integrations.

XFA now supports the OAuth 2.0 PKCE authentication method to integrate applications with XFA.

The integration works by replacing the redirectURL after authentication so users can verify their device security with XFA.

Available now through the XFA Dashboard!

XFA Enforcement can be used as a possession factor through the idp-factor functionality in Okta. This allows XFA to be seamlessly added to any application from within the Okta admin dashboard, given that it uses Okta as the identity provider.

When a user authenticates with Okta, as an additional factor after supplying a username & password, the user is redirected to XFA to verify that the device is compliant with the device security policy before authenticating the user. This assures that only devices that comply with the security policy are allowed access.

We're excited to announce that XFA Enforcement now supports SAMLv2, or Security Assertion Markup Language 2.0, in an ongoing effort to support as many authentication standard and protocols as possible, with the mission to make it possible to secure any application and making sure that only secure devices have access.

What is XFA Enforcement?​

XFA Enforcement is the specialized tier of the XFA product designed to assess the security posture of devices as part of the authentication with your organization's applications.

This feature empowers you to discover all devices used in your organization and ensure that the devices interacting with your systems meet your organization's stringent security standards, whether the devices were previously known or not.

What's New: SAMLv2 Integration​

In response to the need to secure many SaaS services commonly used in an organization, XFA Enforcement now extends its capabilities to seamlessly and transparently support the SAMLv2, or Security Assertion Markup Language 2.0, authentication protocol for both the requesting application and the identity provider without making any change to the specific authentication request or content.

SAMLv2, or Security Assertion Markup Language 2.0, is one of the most common used standards for providing identity from an identity provider such as Google, Microsoft, Okta, for services such as GitHub, Slack, Jira, Notion, Salesforce, ... and so many more.

How to get started?​

For detailed insights into integrating with these specific applications, please refer to our comprehensive integration guides.

Should you have any queries or require assistance, our dedicated support team stands ready to assist you.

We look forward to bringing you many more updates in the future!