Has anyone had any experience with security (vulnerability) testing of the exported content from Storyline or is there any documentation available on security (vulnerability) testing of the exported content from Storyline? e.g are there any calls from the generated output JavaScript or other scripts to external servers (at Articulate or elsewhere), what type of info, if any, is transmitted either about the actual content, the learner or the content creator?
Is this the only type of communication between the published output and Articulate's systems? Is there communication with any other 3rd party systems? Is this communication applicable to both HTML5/JavaScript and SCORM based published content?
Sure thing. Yes, this is the only communication with Articulate. There isn't any communication with other 3rd party systems. And this applies to both web and LMS output.
I'll rely on community members to share their experiences with output security as well!
3 Replies
Hi there, Roger. Check out this information about what analytics we use and how.
Thanks, Crystal.
Is this the only type of communication between the published output and Articulate's systems? Is there communication with any other 3rd party systems? Is this communication applicable to both HTML5/JavaScript and SCORM based published content?
Sure thing. Yes, this is the only communication with Articulate. There isn't any communication with other 3rd party systems. And this applies to both web and LMS output.
I'll rely on community members to share their experiences with output security as well!
This discussion is closed. You can start a new discussion or contact Articulate Support.