Skip to content
English
  • There are no suggestions because the search field is empty.

Living Security Platform - Technical Details for a Successful Launch

Training Platform Technical Details

A key component of employee engagement relies on your users being able to seamlessly interact with video content, digital puzzles, and scorecard dashboards on the Living Security Platform. In an effort  to support a seamless launch and successful rollout within your organization, please review the following technical details we have put together to maximize employee engagement within our Platform.

Topics covered here:

Browser Compatibility

The Living Security Training Platform is designed to work with most browsers but we currently only support the latest version of Microsoft Edge, Google Chrome. The Platform utilizes libraries which may not support some older versions of browsers or specific features of certain browsers, including Internet Explorer (IE).

If the majority of your company is using any older versions of these browsers - or alternative browsers like IE - please let us know right away as we are happy to work with you on messaging. If your IT department is needed to help facilitate this switch, our goal would be to start this process immediately to avoid any delays in timeline.

Ensuring Access with Edge Tracking Prevention

The “Strict” setting in Edge’s Tracking Prevention can block essential resources, which may cause parts of our platform to break. This can result in:

  • Training modules showing as completed when they are not
  • Dashboard errors or pages failing to load

If you encounter these issues, try one of the following solutions:

  1. Switch Tracking Prevention to Balanced or Basic
  2. Keep Strict enabled, but add our domains to the Exceptions list (use the [*.]domain.com format)

ℹ️  Note: These settings are often managed by your endpoint or desktop administration team through Group Policy or Intune. If you’re unable to change them yourself, please contact your IT administrators.


Email Whitelisting

The Living Security Platform is able to send training invitations, learning nudges, notifications, and other emails directly to monitored identities. To ensure these emails do not get flagged, blocked of filtered as a phishing or spam email, please whitelist our IP addresses:

  • 159.183.37.179/32
  • 159.183.38.165/32

We also recommend ensuring the email sender: app@livingsecurity.ai, and domain of livingsecurity.com is allowed.

URL Whitelisting

All traffic for the following URLs need to be whitelisted before training is rolled out:

  • *.livingsecurity.ai

  • *.livingsecurity.com  (legacy assets - videos/images/etc)

  • assets.ctfassets.net  (legacy assets - VTT files from Contentful)

  • videos.livingsecurity-content-cdn.ai  (AI-generated video CDN)

     

  • api.descope.com   (*US ONLY* auth)

     

  • api.euc1.descope.com  (*EU ONLY* auth)

     

  • app.productfruits.com  (*optional* onboarding)

You can verify successful asset loading with the below links or launching the end user test module available in your platform catalog. We recommend doing this on various end user devices and networks:


Please also whitelist our accessibility widget and our chat widget:

Accessibility Widget (optional)
  • cdn.acsbapp.com
  • *.acsapp.com

VPNs, Corporate Network Policies and Bandwidth

These items in conjunction with each other can cause slow load times for training videos and at times, completely block a training video from opening. There is not one magic setting to prevent this since every company, user and machine has different settings and restrictions. However, you should ask if deep packet inspection and/or bandwidth restrictions are in place that prevent the successful delivery of video content from our CDN: https://cdn.cyberescape.livingsecurity.com.

Note: At this time we do not support adaptive bitrate streaming.

Also, ensure network policies support TLS 1.2 for traffic at https://cdn.cyberescape.livingsecurity.com.  Although we support TLS 1.3 for the root application (your unique URL) our CDN https://cdn.cyberescape.livingsecurity.com does not currently support TLS 1.3

SSO Details

To ensure SSO is completed in a timely manner, you will need to provide us your IDP metadata and signing certificate. Only update for the IDP metadata is the nameid with format emailAddress. You will need our SP metadata and signing certificate. It’s available upon request.

We support all SAML 2.0 identity providers and OIDC identity providers. With Okta, you can choose which you prefer to use. 

SSO Steps to Get Started:

  1. Navigate to Settings → Enterprise Identity in the platform
  2. Click Generate Configuration Link
  3. Forward the generated link to your Identity Provider (IdP) administrator to complete the setup

View detailed steps here


User Provisioning

1. On the integrations catalog page, click into the SCIM integration to:

  • Grab your SCIM Endpoint URL

  • Generate your Bearer Token

2. Configure your IdP

  • Paste those credentials into your IdP's SCIM provisioning settings:

    Field

    Value

    SCIM Base URL

    From LSP (Step 1)

    Auth Type

    Bearer Token

    Bearer Token

    From LSP (Step 1)

    Key attribute mappings to configure:

    • userName → email

    • givenName / familyName → first/last name

    • department, title, manager (recommended for HRI context)

     


3. Enable Provisioning Actions 

  • Turn on Create, Update, and Deactivate users at minimum. Verify with a pilot user before rolling out broadly.